[13252] in North American Network Operators' Group
Re: Problems with specific routing policies for each exchange point
daemon@ATHENA.MIT.EDU (Jake Khuon)
Fri Oct 31 14:03:23 1997
From: "Jake Khuon" <khuon@Merit.Net>
To: "Kevin Oberman" <oberman@es.net>
cc: mark@exodus.net (Mark Tripod), nanog@Merit.Net
In-reply-to: "Kevin Oberman"'s message of Fri, 31 Oct 1997 08:10:58 -0800.
<9710311610.AA10122@ptavv.es.net>
Reply-To: khuon@Merit.Net (Jake Khuon)
Date: Fri, 31 Oct 1997 13:55:39 -0500
### On Fri, 31 Oct 97 08:10:58 -0800, "Kevin Oberman" <oberman@es.net> wrote
### to khuon@Merit.Net (Jake Khuon) concerning "Re: Problems with specific
### routing policies for each exchange point ":
KO> I must admit that I do not see the reason for using AS macros in rs-in
KO> and rs-out statements. As far as I know these statements merely
KO> control which AS peers will receive your routes from the route server
KO> and vice-versa. Since these are direct peers with the route server, I
KO> can't see the need to put anything other than specific AS numbers into
KO> the rs-in and rs-out lines.
KO>
KO> Am I missing something obvious?
One particular instance where an as-macro could be useful within rs-in/out
is in the case where one wants to support an MLPA.
--
/*===================[ Jake Khuon <khuon@Merit.Net> ]======================+
| Systems Research Programmer, IE Group /| /|[~|)|~|~ N E T W O R K |
| VOX: (313) 763-4907 FAX: (313) 747-3185 / |/ |[_|\| | Incorporated |
+==[ Suite C2122, Bldg. 1 4251 Plymouth Rd. Ann Arbor, MI 48105-2785 ]==*/
