[34645] in North American Network Operators' Group
Re: Using unallocated address space
daemon@ATHENA.MIT.EDU (michael thomas guldan)
Thu Feb 15 14:03:30 2001
Date: Thu, 15 Feb 2001 14:58:05 -0500
From: michael thomas guldan <michael@core.ele-mental.org>
To: nanog@merit.edu
Message-ID: <20010215145805.S14953@ele-mental.org>
Mail-Followup-To: nanog@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4.3.2.7.2.20010215191720.00ad7850@max.ibm.net.il>
Errors-To: owner-nanog-outgoing@merit.edu
On Thu, Feb 15, 2001 at 07:31:52PM +0200, Hank Nussbacher wrote:
>
> 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
could someone please explain the benefit of turning the registries into
internet police forces? i really don't understand how this could
*realistically* solve this problem, and i can imagine plenty of ways that
this could become a bigger problem in itself
> 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.
>
and the offending party will announce 32 /23s.. what will this solve?
regards,
michael
--
e: michael@ele-mental.org c: +1.614.260.6716 u: www.ele-mental.org
Wir fahr'n fahr'n fahr'n auf der Autobahn
