About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE NCC Mail Archives
     
Mailing Lists:
RIPE NCC Navigation Ends
Link to NCC Lists Archive NCC Lists Archive
Link to RIPE Lists Archive RIPE Lists Archive
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Hierarchical AS-path acl generation?

  • To: Pekka Savola < >
  • From: Mark Prior < >
  • Date: Mon, 28 Oct 2002 22:36:06 +1030

At 1:55 PM +0200 28/10/02, Pekka Savola wrote:
Problem appears to be that as I'd apply these to _inbound_ lists, and
pretty much nobody has structured their policy like ASy:AS-CUSTOMERS:xxx,
this can't really be done. :-( (It would also get very complex with
customers' customers but that's a fringe case probably).

It appears the only way to do this would be to bug the peers to build
their policy using those Customer sets.. somehow I dont' see them jumping
right into this :-/

Well in my case I was using my own registry (and just registering a copy at RADB for info) so I could create all the sets I wanted :-) You could use a different naming scheme if you wanted to host the objects at RADB (just prepend every name with your AS number) and didn't want to badger your customers/peers into doing "the right thing"[tm].

For our peers (rather than customer who I had control over :-) I used a script to check what routes were received versus accepted from a peer and then nag me when they got too far out of sync.

Mark.



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

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | © RIPE NCC. All rights reserved.
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages