On Mon, Nov 23, 2009 at 7:25 PM, Randy Bush <randy@psg.com> wrote:
In all seriousness though, how does this get fixed? and... who has to renumber? :)
luckily, it's not a renumber in the ip address sense. but some router jock[ette]s are gonna be even more overworked than usual.
hope for their sake it's just 1 router :) and 2 transits ... if they have internal bgp setup (more than one router in their peering/transit edge) it's going to cause them some pain :( (at least with only 1 router and 2 bgp peers you could hope to static route around the maintenance event)
how to detect if there are more instances?
o Should some form of 'scrape routeviews before assignment' happen at the RIR? (if you don't like o RV, pick another 2-3 sources of data) o How do you make sure each RIR does this act? o Should the customer check public data sources before acceptance? o Is there a 30 day revoke/return dance for Number Resources?
how to prevent new instances, both asn and ip?
See above ... It seems sensible to check existing data sources, if that can be automated easily enough? -chris