[99183] in North American Network Operators' Group

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

Re: Route table growth and hardware limits...talk to the filter

daemon@ATHENA.MIT.EDU (Russ White)
Sat Sep 8 18:14:46 2007

Date: Sat, 08 Sep 2007 18:13:30 -0400
From: Russ White <riw@cisco.com>
To: Forrest <forrest@almighty.c64.org>
CC: nanog@nanog.org
In-Reply-To: <Pine.LNX.4.44.0709081644360.14686-100000@almightyc64-mail2.dyndns.org>
Errors-To: owner-nanog@merit.edu


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Maybe this is a dumb question, but why isn't there a BGP option to just
> filter more specific routes that have the same AS path as the larger
> aggregate?  This would allow the networks that announce more specifics for
> traffic engineering to still accomplish that, while throwing away the
> garbage from someone else that decides to announce their /19 as 33 routes
> for no apparent reason.  Sure, this would fail if a network decided to 
> only announce /24's for example without a larger aggregate, but how many 
> networks are really doing that?

http://www3.ietf.org/proceedings/03nov/I-D/draft-grow-bounded-longest-match-00.txt

As a matter of fact.

:-)

Russ

- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG4x6KER27sUhU9OQRAs/ZAJ9LARtnoo7YUshwBCuGyj/fVO7MJACg/2AI
Qe6P+ImcLKnan97HlwmYVjQ=
=zgmF
-----END PGP SIGNATURE-----

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