[34636] in North American Network Operators' Group
Re: Using unallocated address space
daemon@ATHENA.MIT.EDU (Philip Smith)
Thu Feb 15 07:56:37 2001
Message-Id: <5.0.2.1.2.20010215214906.0558e4d0@lint.cisco.com>
Date: Thu, 15 Feb 2001 21:53:55 +1000
To: nanog@merit.edu
From: Philip Smith <pfs@cisco.com>
In-Reply-To: <20010213065655.23346.cpmta@c004.sfo.cp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Errors-To: owner-nanog-outgoing@merit.edu
At 22:56 12/02/2001 -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.
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...
I've see these:
Network Origin AS Description
39.96.40.224/30 14408 iCAIR
50.198.0.0/16 2548 Digital Express Group, Inc.
91.16.23.0/24 11770 Net56
103.22.7.0/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...
philip
--
