Pro-actively publishing IRR data
I'm still working on trying to get my primary provider to BGP peer with us, but in the meantime, I'd like to pro-actively publish our objects and route policy to the IRR. My primary provider is currently advertising our IPv4 routes for us from their AS. Are there any potential dangers of publishing our information before we use it that I may be overlooking? Steve
On Mon, Mar 16, 2009 at 12:14:08PM -0400, Steve Bertrand wrote: [snip]
Are there any potential dangers of publishing our information before we use it that I may be overlooking?
In case you are worried about folks who filter, recall that the IRR uniqueeness is based upon the Prefix/length, originAS, and sourceDB tuple. There is nothing wrong with registering the origin as it is parallel to the origin-as-it-will be. If *you* do it, instead of your provider, you will not have to co-ordinate with anyone to yank the old one. Purposeful overlapping for the purposes of transition is one of the features. Cheers, Joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
Joe Provo wrote:
On Mon, Mar 16, 2009 at 12:14:08PM -0400, Steve Bertrand wrote: [snip]
Are there any potential dangers of publishing our information before we use it that I may be overlooking?
In case you are worried about folks who filter, recall that the IRR uniqueeness is based upon the Prefix/length, originAS, and sourceDB tuple. There is nothing wrong with registering the origin as it is parallel to the origin-as-it-will be. If *you* do it, instead of your provider, you will not have to co-ordinate with anyone to yank the old one. Purposeful overlapping for the purposes of transition is one of the features.
Thanks Joe, This is exactly what I was looking to find out. Cheers, Steve
participants (2)
-
Joe Provo -
Steve Bertrand