[102844] in North American Network Operators' Group

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

Re: Prefix filtering for Cisco SUP2

daemon@ATHENA.MIT.EDU (Andy Dills)
Fri Feb 29 14:14:23 2008

Date: Fri, 29 Feb 2008 13:56:08 -0500 (EST)
From: Andy Dills <andy@xecu.net>
To: Henry Futzenburger <henryfutz@gmail.com>
cc: nanog@merit.edu
In-Reply-To: <da60725e0802291015n14a4c19fh9621b8c3277eb362@mail.gmail.com>
Errors-To: owner-nanog@merit.edu


On Fri, 29 Feb 2008, Henry Futzenburger wrote:

> 2. Accept only default and RIR minimum routes from upstream.
>     a. Filter based on RIR minimums, rely on default for unaggregated
> routes.
>     b. Assume a reduction of about 50,000-100,000 total routes.
> 
> Does anyone have any opinions as to whether one option is better than the
> other?  Are there options that would be better than either of these?  Are
> there serious risks to either option?
> 
> My sense is that either of these would be a fairly benign change, only
> having a marginal impact on routing efficiency in either case.  It seems
> like the better option is the one that retains the greater number of routes
> within some margin of safety.  What do you think?

I chose number 2. 

It works so well I'm starting to wonder why any network with less than, 
say, three or four transit providers would want to do anything else, even 
without system limits. 

My philosophy is rapidly becoming "Let the settlement-free club worry 
about all the deaggregated prefixes."

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---

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