Re: Weekly Routing Table Report
Wha happen? Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Analysis Summary BGP routing table entries examined: 139674 Prefixes after maximum aggregation: 83474 Unique aggregates announced to Internet: 67116 Total ASes present in the Internet Routing Table: 17729 Origin-only ASes present in the Internet Routing Table: 15381 Origin ASes announcing only one prefix:7282 Transit ASes present in the Internet Routing Table:2348 Transit-only ASes present in the Internet Routing Table:194 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 23 Prefixes from unregistered ASNs in the Routing Table:38 Special use prefixes present in the Routing Table:0 Prefixes being announced from unallocated address space: 13 Number of addresses announced to Internet: 1212269440 Routing Table Report 04:00 +10GMT Sat 02 Apr, 2005 Analysis Summary BGP routing table entries examined: 158858 Prefixes after maximum aggregation: 92606 Unique aggregates announced to Internet: 76314 Total ASes present in the Internet Routing Table: 19277 Origin-only ASes present in the Internet Routing Table: 16774 Origin ASes announcing only one prefix:7827 Transit ASes present in the Internet Routing Table:2503 Transit-only ASes present in the Internet Routing Table: 68 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 23 Prefixes from unregistered ASNs in the Routing Table:31 Special use prefixes present in the Routing Table:0 Prefixes being announced from unallocated address space: 13 Number of addresses announced to Internet: 1394234240 This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. Routing Table Analysis cscora To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], afnog@afnog.org @apnic.net cc: Sent by: Subject: Weekly Routing Table Report owner-nanog 04/08/2005 02:18 PM Please respond to pfs This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] If you have any comments please contact Philip Smith [EMAIL PROTECTED]. Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Analysis
Re: Weekly Routing Table Report
On Fri, 08 Apr 2005 16:48:53 EDT, Joe Loiacono said: Wha happen? Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Total ASes present in the Internet Routing Table: 17729 Routing Table Report 04:00 +10GMT Sat 02 Apr, 2005 Total ASes present in the Internet Routing Table: 19277 This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Just guessing here, but I'd not be surprised if the explanation involved one or more of the phrases BGP Flap, temporary outage, backhoe/shark/chucklehead. 4AM local might very well be inside a maint window too... pgpjB6QopXXH6.pgp Description: PGP signature
RE: Weekly Routing Table Report
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, April 08, 2005 2:00 PM To: Joe Loiacono Cc: [EMAIL PROTECTED] Subject: Re: Weekly Routing Table Report On Fri, 08 Apr 2005 16:48:53 EDT, Joe Loiacono said: Wha happen? Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Total ASes present in the Internet Routing Table: 17729 Routing Table Report 04:00 +10GMT Sat 02 Apr, 2005 Total ASes present in the Internet Routing Table: 19277 Just guessing here, but I'd not be surprised if the explanation involved one or more of the phrases BGP Flap, temporary outage, backhoe/shark/chucklehead. 4AM local might very well be inside a maint window too... I'll take Backhoe Planting for $100..'tis plantin' season y'know... /Alex K.
Re: Weekly Routing Table Report
Hi Folks, Sorry about that, something seems to have broken when the script was run earlier on today. The table in the view I use was 140k prefixes then, and is now back up to the normal 159k again. philip -- Joe Loiacono said the following on 09/04/2005 06:48: Wha happen? Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Analysis Summary BGP routing table entries examined: 139674 snip
Re: Weekly Routing Table Report
The largest growth element I see is deaggregation of 'classical' space which may have perfectly valid purpose within an AS, or in a provider-customer relationship, but not N hops away in the DFZ. The reasons vary from putting the burden of traffic engineering on the rest of the world to handwaving about applying security band-aids by reducing the visibility into the the target space. Joe, If I was visiting your home and I happened to toss a rock through your livingroom window on my way out, would you send me a bill for the repairs? We have no existing business relationship, no contracts in place, so would you send me a bill? Sometimes there are technical solutions to problems but if my actions increase your costs there is also a non-technical solution. One could argue that this whole CIDR reports issue should not even be discussed on this list because it is a non-technical issue. If someone else is causing your network increased costs, send them a bill, talk to your lawyer, whatever. But keep it off NANOG. --Michael Dillon (with only half of my tongue in cheek)
Re: Weekly Routing Table Report
On Fri, Jan 07, 2005 at 03:47:08PM -0500, Jared Mauch wrote: [snip] I think that's a matter that seems to be already decided. People want multihoming, redudnancy and such and are willing to put the burden on the global routing table as a result. The matter was not strictly (not even primarily) multihoming when the last serious look at the data was made, and it doesn't appear to be the matter today. CAIDA's older data matches my current anecdotal day-to-day experience.* (No one has offered more current analysis in the wake of continuing threads here and elsewhere. If you've got more recent data + analysis then then please share.) The largest growth element I see is deaggregation of 'classical' space which may have perfectly valid purpose within an AS, or in a provider-customer relationship, but not N hops away in the DFZ. The reasons vary from putting the burden of traffic engineering on the rest of the world to handwaving about applying security band-aids by reducing the visibility into the the target space. Trivial example pulled off the top: 136.223.0.0/16 sourced as raft of same as-path deaggregates by 7018. Are there IRR entries to indicate a conscious decision rather than error? Surely you jest. Yes, growth happens and the memory addition Jared cites has been going on and continues to go on (multihoming enterprises, other edge customers now get to feel the pain). There are some interesting observations as part of the current 'atom' work** previously discussed in the nigh-weekly related threads here. Joe * specifically, see para 2 in conclusions of Complexity of global routing policies http://www.caida.org/outreach/papers/2001/CGR/ ** section 6 in http://www.caida.org/projects/routing/atoms/proposal/ -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
Re: Weekly Routing Table Report
Routing Table Analysis wrote: This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] If you have any comments please contact Philip Smith [EMAIL PROTECTED]. Routing Table Report 04:00 +10GMT Sat 08 Jan, 2005 Analysis Summary BGP routing table entries examined: 153319 Prefixes after maximum aggregation: 89967 Should it matter that in six months its gone from 140k to 153k? At this rate it might crack 200k in less than two years.
Re: Weekly Routing Table Report
On Fri, Jan 07, 2005 at 03:02:40PM -0500, Joe Maimon wrote: This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] If you have any comments please contact Philip Smith [EMAIL PROTECTED]. Routing Table Report 04:00 +10GMT Sat 08 Jan, 2005 Analysis Summary BGP routing table entries examined: 153319 Prefixes after maximum aggregation: 89967 Should it matter that in six months its gone from 140k to 153k? At this rate it might crack 200k in less than two years. I think that's a matter that seems to be already decided. People want multihoming, redudnancy and such and are willing to put the burden on the global routing table as a result. The result, people are upgrading router memory to the max, lots of people have been asking recently about how much memory for a full routing table, etc.. I think the simple answer is: If you're using anything recent (ie: since 2001) you're going to want to use 256m at minimum and ideally 512m-1g of dram in your system with a reasonable cpu to process updates quickly. This is something that the market has really demanded (multihoming) so the result is a global impact. The statement think globally, act locally comes to mind, but it's a tough problem as everyone depends on their internet connectivity these days, so they want it to be as reliable as possible. - jared -- Jared Mauch | pgp key available via finger from [EMAIL PROTECTED] clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Re: Weekly Routing Table Report
Analysis Summary BGP routing table entries examined: 153319 Prefixes after maximum aggregation: 89967 Should it matter that in six months its gone from 140k to 153k? At this rate it might crack 200k in less than two years. This was about the weekly routing table report, but I'm going to bring in some numbers from the CIDR report. It would be back down to 140k if the dirty 30 top offenders in the CIDR Report would aggregate their routes. Someone's going to have to draw a line in the sand at some point, and someone thinking locally and acting globally is going to be punished by the globe. Don't ask me how this could work, because I don't have an answer. Maybe I'm the Dirty 30 T-Shirts could be made up and handed out. (I wonder if a couple of major routing venders, who profit from routing table growth, would sponsor the creation of the t shirts snicker...) -Jerry
Re: Weekly Routing Table Report
--On Friday, January 07, 2005 18:15 -0600 Jerry Pasker [EMAIL PROTECTED] wrote: This was about the weekly routing table report, but I'm going to bring in some numbers from the CIDR report. It would be back down to 140k if the dirty 30 top offenders in the CIDR Report would aggregate their routes. Someone's going to have to draw a line in the sand at some point, and someone thinking locally and acting globally is going to be punished by the globe. Don't ask me how this could work, because I don't have an answer. Yeah I've been noticing this problem myself too...I'm between 150k and 151k at my various peers. Most of the gear at my edges should be fine well past the 250,000 mark or so, but I know of people who are having problems right now, even if they don't know it. What, really, could be done to curtail these offenders? Maybe I'm the Dirty 30 T-Shirts could be made up and handed out. (I wonder if a couple of major routing venders, who profit from routing table growth, would sponsor the creation of the t shirts snicker...) -Jerry -- GPG/PGP -- 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E
Re: Weekly Routing Table Report
How much has the second number changed? Is this the result of worsening aggregation or simply more address space being advertised? Core routers won't even blink at 200k routes. I wonder how many enterprise 3x00/7x00 routers will fall over due to memory issues. Also, as we have learned previously, past routing table growth (especially for a short period) is an extremely poor predictor of future growth. - Dan On 1/7/05 3:02 PM, Joe Maimon [EMAIL PROTECTED] wrote: Routing Table Analysis wrote: This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] If you have any comments please contact Philip Smith [EMAIL PROTECTED]. Routing Table Report 04:00 +10GMT Sat 08 Jan, 2005 Analysis Summary BGP routing table entries examined: 153319 Prefixes after maximum aggregation: 89967 Should it matter that in six months its gone from 140k to 153k? At this rate it might crack 200k in less than two years.
