About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Modification of RIPE-181's as-in/as-out attributes

  • To: Cengiz Alaettinoglu < >
  • From: Curtis Villamizar < >
  • Date: Tue, 31 Oct 1995 21:49:30 -0500
  • Cc: "Steven J. Richardson" < >
  • Reply-to:

In message <199510311942.AA07667@localhost, 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




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community