On Wed, 10 Jul 2002 10:01:34 +0300, Hank Nussbacher <hank@att.net.il> wrote:
At 10:08 PM 09-07-02 +0000, Christopher Sharp wrote:
The LIR that allocated the ASN should be able to handle its removal. I have started creating mntner objects for new ASNs with duplicate auth tags ( with different MD5-PW passwords). I give one to the requesting organization and one I keep for myself. In the event the company goes bankrupt and I can't find anyone to talk to in the company, then I at least have the ability to remove their entry without them being around.
This is excellent for future registrations but doesn't help with historical allocations that were not done like this. Especially where the allocating LIR has had no contact with the registrant for an extended period of time. I suspect we need to look back, as well as forward, when implementing a solution.
I don't think we have to resort to the courts for this and I doubt they would help. But the problem is not only with ASNs but also with IP blocks being advertised by organizations that don't own them. Those that get routing-wg@ripe.net see the list every week of unallocated ASNs and IP blocks being used freely on the Internet. I'd like to make a suggestion. Since these ASNs and IP blocks are the property of the RIRs, and since organizations are cybersquatting on these resources why shouldn't these RIRs advertise these IP blocks and ASNs themselves and blackhole them to their routers?
You'd get the attention of these cybersquatting organizations *real* fast.
To succeed in grabbing the attention of all such offenders you probably need the support of all RIRs and IANA to carry out a unilateral crackdown. Otherwise the skilled offenders will just migrate to other unallocated address space. An informal approach such as the wider distribution of this list may well help. I'm sure a lot of people would start listing many of these ASNs and IP blocks in their filters. C.