North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: The Cidr Report

  • From: Stephen J. Wilcox
  • Date: Fri Feb 11 17:59:20 2005

On Fri, 11 Feb 2005, Mike Leber wrote:
> On Fri, 11 Feb 2005, Stephen J. Wilcox wrote:
> > On Fri, 11 Feb 2005, Frotzler, Florian wrote:
> > 
> > > 
> > > > Recent Table History
> > > >         Date      Prefixes    CIDR Agg
> > > >         04-02-05    151613      103143
> > > >         05-02-05    152142      103736
> > > >         06-02-05    152231      103721
> > > >         07-02-05    152353      103830
> > > >         08-02-05    152514      103966
> > > >         09-02-05    153855      104090
> > > >         10-02-05    154283      104246
> > > >         11-02-05    154341      104240
> > > <...>
> > > 
> > > ~ +3000 routes in one week? Anyone else frightened by this?
> > > 
> > > Florian
> > 
> > any thoughts on how to fix it? my peers keep sending these to me and i'll
> > even admit my customers do too. telling people its bad doesnt appear to have
> > an effect, at the small end networks seem to collect /24s and announce them
> > freely, at the large end i'm still without an explanation as to why large
> > networks require so many prefixes - none of them seem to comment?
> > 
> > if people arent self policing it seems the only other way is for the larger
> > transit providers to stop accepting prefixes and telling their customers to
> > fix their s**t. and i dont see them doing this.
> 
> It seems to me they get paid to carry prefixes by their customers.

the payment would be the same if it was a /19 or 32x/24 announced at source

> And their peers listen to the prefixes because they make money by using
> those prefixes.
> 
> So, to the extent you make money listening to them, use the routes.

so the problem is noone wants to be the first to jump as it costs money? so 
whats the suggestion for how to not be first? ie is it possible for a small 
group of large operators to agree a consensus? 

you dont even have to actively filter to start this, if a script were run to 
advise customers daily when they were announcing routes incompliant to the 
transits 'routing policy' it would have some effect. one thing i've found from 
some of my customers is they're actually ignorant to the problems they cause, 
they think its cool to announce 10 prefixes and can be educated otherwise.

Steve



> 
> And if they start to cause you problems you will have to take corrective
> action to stablize your network, as was done a long time ago (internet
> time):
> 
> http://www.merit.edu/mailinglist/mailarchives/old_archive/1995-09/msg00047.html
> 
> (link grabbed at random from the archives, I'm sure there are better posts
> that actually list the full old school sprint filters.)
> 
> However, if you are the one filtering and all your competitors figure out
> how to handle 154,000 routes then you will be at a competitive
> disadvantage.
> 
> Coincidentally, the largest networks also spend the most with their
> vendors and get to tell the vendors what they want in the next generation
> of boxes they buy.
> 
> Mike.
> 
> +----------------- H U R R I C A N E - E L E C T R I C -----------------+
> | Mike Leber           Direct Internet Connections   Voice 510 580 4100 |
> | Hurricane Electric     Web Hosting  Colocation       Fax 510 580 4151 |
> | [email protected]                                       http://www.he.net |
> +-----------------------------------------------------------------------+
> 
>