Hi Mauricio, thanks for the reply.
I believe there are quite a few folks who automate their peering up keep
with the help of the data contained within the IRRs. With the IRRs
providing a mechanism for validating routing information and RPSL providing
a common language for describing routing policy - automating the creation
of prefix and AS-Path filters for peering sessions becomes attractive.
Check out http://www.irr.net/docs/faq.html for additional reasons for using
IRR data to generate routing policy.
IRRToolSet is a tool that can create router configurations based on IRR
data. The portion I'm trying to figure out is the 'pushing' of these
configurations. From what I gather, it seems that this is usually
something thats homegrown. Anyone willing to share their homegrown tools?