Good start, RPSL is actually a step forward from RIPE-181.  I think RIPE
has the best documentation and surely most widely used RPSL databases. 
The IRR as the collection of databases isn't quite perfectly mirrored
nor is the data nearly up to date.  

As for the question about the application.  It sounds like your being
asked to filter routes the other networks(probably just customers and
peers) are advertising into your network.  The nice idea being chased is
probably to verify authority to advertise a given route to prevent
mistakes and some malicious activity.

Various Places to look:
http://www.ripe.net/ripencc/pub-services/db/irrtoolset/index.html nee
http://www.isi.edu/ra/RAToolSet/
http://www.ripe.net/
http://www.ripe.net/ripencc/pub-services/
http://www.ripe.net/ripe/docs/databaseref-manual.html
RPSL in RFC 2622
RFC 2725
Using RPSL RFC 2650

Peter van Oene wrote:
> 
> AS-Macro's are an object in an RPSL based Internet Routing Registry (IRR)
> that is used to simplify routing policy registration by grouping AS's.  See
> Ripe-181 (rfc 1786).
> 
> If you happen to build routing policies using RPSL, I expect you can write
> policies around AS-Macros, though I've no experience doing so.  Try posting
> on the ISP lists, ISP-Routing or ISP-BGP or another similar ISP oriented
> list or doing some additional reading.
> 
> At 06:23 AM 12/27/2001 -0500, you wrote:
> >Recently I was asked to do BGP filtering for a peer thru AS-Macros. I've
> >looked around but can't find any examples of it. I'm at a loss: is BGP
> >filtering thru AS-Macros another fancy name for AS-PATH filtering, or is
it
> >something entirely different? If it is different, can anybody point mt to
> >some examples/sources of information on this?
> >
> >Many thanks,
> >Hugo Taxa




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=30290&t=30172
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to