[34573] in North American Network Operators' Group
Re: BGP Question - how do work around pigheaded ISPs
daemon@ATHENA.MIT.EDU (Joe Provo)
Mon Feb 12 17:38:38 2001
Date: Mon, 12 Feb 2001 17:36:20 -0500
From: Joe Provo <joe.provo@rcn.com>
To: nanog@merit.edu
Message-ID: <20010212173620.B99785@ultra.net>
Reply-To: joe.provo@rcn.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010209213312.A16372@pentics.com>; from chuegen@pentics.com on Fri, Feb 09, 2001 at 09:33:12PM -0800
Errors-To: owner-nanog-outgoing@merit.edu
On Fri, Feb 09, 2001 at 09:33:12PM -0800, Craig A. Huegen wrote:
> This is a frequent problem for those who have had address space from some
> of the older blocks and are trying to go back and better handle.
[snip]
One point you missed: without good/accurate registry data, there is no
difference between "broken announcments" and "hijacked network". That
is a strong operational reason to strictly follow the registry
allocations, rather than the weak concern about people selling off
chunks of legacy address space.
I have been aware of several times when squatted, stolen, or
misconfigured-into-others'-space has been caught by registry-minded
filters. Specifically regarding slices of classical B-space and
not yet allocated A-space.
Cheers,
Joe
--
Joe Provo Voice 508.486.7471
Director, Internet Planning & Design Fax 508.229.2375
Network Deployment & Management, RCN <joe.provo@rcn.com>
