North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Using unallocated address space
- From: Hank Nussbacher
- Date: Thu Feb 15 12:57:12 2001
At 21:53 15/02/01 +1000, Philip Smith wrote:
At 22:56 12/02/2001 -0800, Sean Donelan wrote:
And announcing both unallocated address space and unallocated AS space
will mean an entry in my little summary which I send out every week to
RIPE NCC, ARIN and APNIC mailing lists...
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
I've see these:
Network Origin AS Description
126.96.36.199/30 14408 iCAIR
188.8.131.52/16 2548 Digital Express Group, Inc.
184.108.40.206/24 11770 Net56
220.127.116.11/24 9768 PubNet (Korea Telecom)
And the large amount of private and unallocated ASes has already been
mentioned on the list this week...
Someone is watching, it's another issue what to do about it, if anything
can be done at all...
Has RIPE/ARIN/APNIC responded yet? I can hound RIPE as well if you want.