This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Modification of RIPE-181's as-in/as-out attributes
- Next message (by thread): too many hits?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Curtis Villamizar
curtis at ans.net
Wed Nov 1 03:49:30 CET 1995
In message <199510311942.AA07667 at cat.isi.edu>, Cengiz Alaettinoglu writes: > > I like this idea. There is only one problem that I see with it. The > as numbers in as-in and as-out lines are often used (by tools like > prpath and prtraceroute) to deduce the topology of the Internet. If an > AS only specifies a policy like: > > aut-num: AS2 > as-in: from (NOT AS1) 5 accept ANY > > then prpath has no way of deducing the neighbors of AS2. Doesn't that deduction belong in the inet-rtr ifaddr and peer lines? > aut-num: AS2 > neighbor-list: AS3, AS4, AS5, AS1 # pehaps with router addresses? This is reasonable for AS that don't provide inet-rtr records for their routers (I suspect most). Curtis
- Next message (by thread): too many hits?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]