[43103] in North American Network Operators' Group

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

Re: The Gorgon's Knot. Was: Re: Verio Peering Question

daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Fri Sep 28 22:16:11 2001

Message-Id: <5.1.0.14.2.20010928220621.03c18318@127.0.0.1>
Date: Fri, 28 Sep 2001 22:09:15 -0400
To: nanog@merit.edu
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <Pine.GSO.4.40.0109282210520.28431-100000@clifden.donelan.c
 om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Errors-To: owner-nanog-outgoing@merit.edu


At 10:12 PM 9/28/2001 -0400, Sean Donelan wrote:
 >
 >> The global routing table is hereby capped at 125K routes.  After that,
 >> if you want a route, you have to pay somebody to give up theirs.
 >
 >Of course, we could adopt geographic allocations.  North American is
 >still working on (+1) in e.164 space.  We could shrink the global
 >route table to a few thousand routes.

There are many prefixes which are demonstrably useless in the global table 
(e.g. most of 7046).  If you are really interested in reducing the size of 
the table, why not go after those?  Instant gratification and all that.

But I thought the problem is not *size* of the table, but *changes* in the 
table.  With zero updates, a BGP table of double the current size would not 
bother any core router on the 'Net today.

So, let's work on things like progressive flap dampening.  I believe you 
suggested this before, Sean?

--
TTFN,
patrick


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