[26082] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Verio Decides what parts of the internet to drop

daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Sat Dec 4 09:46:11 1999

From: bmanning@vacation.karoshi.com
Message-Id: <199912041513.HAA03023@vacation.karoshi.com>
To: jlewis@lewis.org
Date: Sat, 4 Dec 1999 07:13:40 -0800 (PST)
Cc: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.10.9912040214380.7100-100000@redhat1.mmaero.com> from "jlewis@lewis.org" at Dec 04, 1999 02:17:33 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


> > > As for BSDI, is it possible for them to trade their /17 in to ARIN for a
> > > more likely routable one?
> > 
> > 	NO.  Arin can't presume to know what is or is not routable.
> 
> registries have no control over backbone BGP filters, they can't guarantee
> routability.  If there's not a good chance of their allocations being
> routable, then what's the point in allocating space?

	Lets back up a tad and approch from another direction.
	Routable by whom? 

	One of the important (and some would say the most important)
	things a registry can do is keep accurate information on 
	delegations. If a user of space does not care that its packets
	are visable via Sprint (to pick on an ISP at random), then
	why should a registry care, as long as the user of IP space is
	happy. The registry should be willing and able to make such
	a delegation and registry clients ought to be able to ensure
	that the registry has accurate data about them and their delegation.

	IMHO, registries must be blind to ISP routing policy. 

--bill


home help back first fref pref prev next nref lref last post