|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: verio arrogance
Say hypothetically it costs approximately $0.10 per route (in routing cpu/ram cost) per router. (average router cost $12,000 and 120,000 routes in the table). Lets also say hypothetically the average bgp speaking user has 3 bgp speaking routers. And lets say there are 25,000 AS's in use. By announcing as 4 blocks, instead of 1 aggregate, you are costing the bgp speaking community a total of $30,000. You are saving yourself money, at everyone else's expense. I know my math is not exactly correct, but it's an example to show why people get pissy about this sort of thing.. You aren't the biggest offender, but how should anyone draw an arbitrary line for "you are polluting too much" and "you are polluting, but to a reasonable extent". At this point, I have my whole network in NYC, so there isn't really any need for deaggregation. If/When my network expands to other cities, I will be planning things out to avoid deaggregating -- most likely with the deaggregate+no-export method. You could do a deaggregate+no-export method as well, even with your two different transit providers. You would just need to run ebgp-multihop to each of them from the opposite network, and announce your more-specifics there. Not a perfectly clean method, but at least it keeps your pollution local. --Phil -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ralph Doncaster Sent: Friday, July 26, 2002 10:49 PM To: Stephen Griffin Cc: [email protected] Subject: Re: verio arrogance > > I'm a little disappointed you're wasting list bandwidth after this > > has been well discussed, and not a single post has offered a better > > technical alternative to de-aggregating my ARIN /20 (given my > > network topology). > > > > -Ralph > > Announce your largest aggregate, and announce more-specifics tagged > no-export to those peers who agree to accept them? Which is worse than announcing just the more specifics to 2 different transit providers in 2 different cities. > Upgrade the connectivity between your sites? Technically sound, economically stupid. You offering to pony up the $5K/mth for an OC3 so I can have a redundant link between Ottawa and Toronto? Besides the technical aspects of my network, I didn't see any proof that relaxed prefix filtering (and no I'm not saying accept /32's - the more specifics I got Verio to accept were /23's) would cause significant (i.e. >30%) routing table bloat when that was recently discussed. -Ralph
|