[27882] in North American Network Operators' Group
Re: more-specifics in class B space?
daemon@ATHENA.MIT.EDU (Brian Wallingford)
Thu Mar 23 00:58:49 2000
Date: Thu, 23 Mar 2000 00:41:31 -0500 (EST)
From: Brian Wallingford <brian@meganet.net>
To: Joe Provo - Network Architect <joe.provo@rcn.com>
Cc: nanog@merit.edu
In-Reply-To: <20000322221226.A23178@ultra.net>
Message-ID: <Pine.LNX.4.10.10003230032400.10852-100000@cerise>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
: > it appears there are providers out there that are abiding by the "ARIN
: > guidelines" and thereby nuking routes within classical class b space.
: [snip]
:
: It also appears that there are parties who received address delegations
: within classical B space and are parceling chunks out, without any
: delegation or registration. Without that administrativia, and no clear
: customer-vendor relationship in an AS path, how does this behavior look
: any different to address hijacking?
It doesn't. At the very least, an rwhois server should be hosted by the
current authority for the aggregate space, and adverts should be
registered with the appropriate routing registry. IMHO, of course.
-brian
