At 22:56 12/02/01 -0800, Sean Donelan wrote:
On Mon, 12 February 2001, John Fraizer wrote:
Any time a network is caught announcing non-allocated address space, the registry should bill them accordingly. If they refuse to pay, the registry should yank their ASN. That would be strong encouragement to do the right thing.
Other than making it difficult for people to figure out WHOIS using that ASN, "yanking" an ASN's registration has little practical effect. You can use an un-allocated ASN almost as easily as using an un-allocated address block.
The registries, ARIN/RIPE/APNIC should announce the offending block themselves and shunt it to null0. If the offender announces a /18 then they should announce theirs as 2x/19s and thereby override the bogus /18. I don't think the problem is so huge that a few dozen extra prefixes announced by the registries will bloat and kill the routing table size. If the registries don't do this, these cybersquatters will come thru later on and demand to keep the IP address space they have grabbed just as the .sex, and .web and all the other alternate DNSers have done. -Hank