[43262] in North American Network Operators' Group
Re: Gordius has left the building. Was: RE: The Gorgon's Knot.
daemon@ATHENA.MIT.EDU (Alex Bligh)
Wed Oct 3 04:54:31 2001
Date: Wed, 03 Oct 2001 09:53:52 +0100
From: Alex Bligh <alex@alex.org.uk>
Reply-To: Alex Bligh <alex@alex.org.uk>
To: "Bender, Andrew" <abender@taqua.com>, nanog@merit.edu
Cc: Alex Bligh <alex@alex.org.uk>
Message-ID: <171147393.1002102831@[195.224.237.69]>
In-Reply-To: <D730399C6D1CD411B6DC00508BAC05362A316B@apollo.taqua.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Errors-To: owner-nanog-outgoing@merit.edu
--On Tuesday, 02 October, 2001 11:09 PM -0400 "Bender, Andrew"
<abender@taqua.com> wrote:
> We'll have to see another knee in route
> proliferation before this becomes a problem, and space exhaust would
> most certainly prevent this from happening.
Ah, but with what minimum prefix length:
a) Verio-esque
b) /24 - current 'global minimum filter length'
c) /32
d) A mixture between (a) and (b) - current situation
People need to recognize that there is defacto filtering going
on out there is everyone's network (well, nearly everyone's),
in that very few people accept longer routes than a /24. In
a CIDR world that's a different filtering rule to the Verio
one, but it's still arbitrary (in some senses - think non-RIR
assigned class A space - rather more arbitrary).
IE is the assumption space exhaust will precede the problems
you predict on router hardware precisely BECAUSE RIR allocation
rules (the more sensible ones), and the /various/ filtering,
dampening policies and the othr pro-aggregation work, has
determined a minimum useful prefix size? In which case getting
rid of the policies which make your assumption correct would
be a bad thing.
--
Alex Bligh
Personal Capacity.
