[92807] in North American Network Operators' Group
Re: 200K prefixes - Weekly Routing Table Report
daemon@ATHENA.MIT.EDU (Jerry Pasker)
Fri Oct 13 15:54:46 2006
In-Reply-To: <EA7B0567-7450-4458-854F-D179D7E75120@ianai.net>
Date: Fri, 13 Oct 2006 14:35:36 -0500
To: nanog@merit.edu
From: Jerry Pasker <info@n-connect.net>
Errors-To: owner-nanog@merit.edu
>On Oct 13, 2006, at 2:02 PM, Routing Analysis Role Account wrote:
>
>>Routing Table Report 04:00 +10GMT Sat 14 Oct, 2006
>>
>>Analysis Summary
>>----------------
>>
>>BGP routing table entries examined:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
>>200339
>> Prefixes after maximum aggregation:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
>>108814
>
>Shall we all have a moment of silence for 200K prefixes in the global table=
=2E
>
>Maybe reboot all our routers at once or something?
>
>--
>TTFN,
>patrick
Thanks for reminding me to change my neighbor=20
maximum-prefix 250000 80 statements to something=20
more "reasonable" before I started getting=20
warnings to my pager! I'm still a few thousand=20
routes shy of 200K as of today......
I like that second line that you included.=20
Maximum aggregation isn't always possible, but I=20
think there are a lot of operators out there that=20
don't aggregate as much as they could. They cite=20
various reasons for chewing up router memory (=20
"Oh, it's technically impossible....". or my=20
favorite.... "because someone could announce more=20
specifics and steal our traffic, so we have to=20
announce 842 /24s all separately, ALL THE TIME" )=20
while the rest of the net doesn't seem to have=20
those issues, (or they deal with them as they=20
happen... "uh, oh, someone's blackholing our=20
traffic, let's announce our space as /24s until=20
we can get that other operator to correct their=20
stupidity... we'll withdraw the /24s as soon as=20
it's fixed 22 hours later....")
You should have put a difference number there=20
too, just so everyone didn't have to get out=20
their calculators to figure out how many extra=20
routes there are (91525). So since my calculator=20
is out, I did some more numbers. Of those 91,525=20
routes that are extra routes in the table,=20
14,444 of those are the dirty-30.
So of those top 30 ASes that I refer to as the=20
"Dirty Thirty", represent .13% (POINT ONE THREE=20
PERCENT!) of the ASes, but they contribute 15.7%=20
of the amount of route-bloat on the net!!=20
=2E13%,=3D15.7%.
The dirty-thirty is a shameful list. But=20
apparently there isn't enough pressure from=20
within the routing community to not be on it. At=20
least not yet. ;-)
----------------------------------
"I'll reboot mine, if you reboot yours."
