BGP Update Report
BGP Update Report Interval: 12-Nov-07 -to- 13-Dec-07 (32 days) Observation Point: BGP Peering with AS2.0 TOP 20 Unstable Origin AS Rank ASNUpds % Upds/PfxAS-Name 1 - AS8452 339964 5.0%1152.4 -- TEDATA TEDATA 2 - AS9116 190504 2.8% 536.6 -- GOLDENLINES-ASN Golden Lines Main Autonomous System 3 - AS16637 177437 2.6%2534.8 -- MTNNS-AS 4 - AS8866 137868 2.0% 480.4 -- BTC-AS Bulgarian Telecommunication Company Plc. 5 - AS475562271 0.9% 40.8 -- VSNL-AS Videsh Sanchar Nigam Ltd. Autonomous System 6 - AS33783 53695 0.8% 409.9 -- EEPAD 7 - AS14390 52883 0.8% 839.4 -- 8 - AS949848850 0.7% 43.8 -- BBIL-AP BHARTI BT INTERNET LTD. 9 - AS958346699 0.7% 40.5 -- SIFY-AS-IN Sify Limited 10 - AS982946349 0.7% 40.6 -- BSNL-NIB National Internet Backbone 11 - AS912142681 0.6% 198.5 -- TTNET TTnet Autonomous System 12 - AS815141953 0.6% 33.2 -- Uninet S.A. de C.V. 13 - AS26407 41941 0.6%1553.4 -- 14 - AS24731 41385 0.6% 844.6 -- ASN-NESMA National Engineering Services and Marketing Company Ltd. (NESMA) 15 - AS26829 41230 0.6% 41230.0 -- 16 - AS702 40111 0.6% 39.9 -- AS702 Verizon Business EMEA - Commercial IP service provider in Europe 17 - AS462135561 0.5% 230.9 -- UNSPECIFIED UNINET-TH 18 - AS17974 35217 0.5% 79.5 -- TELKOMNET-AS2-AP PT Telekomunikasi Indonesia 19 - AS33588 32539 0.5% 68.9 -- 20 - AS11456 31622 0.5% 20.2 -- TOP 20 Unstable Origin AS (Updates per announced prefix) Rank ASNUpds % Upds/PfxAS-Name 1 - AS26829 41230 0.6% 41230.0 -- 2 - AS17540 26107 0.4% 26107.0 -- MTL-AP Modern Terminals Limited 3 - AS22072 25664 0.4% 25664.0 -- 4 - AS33447 14021 0.2% 14021.0 -- 5 - AS40474 10516 0.2% 10516.0 -- 6 - AS617417671 0.3%8835.5 -- 7 - AS193348461 0.1%8461.0 -- 8 - AS326506144 0.1%6144.0 -- 9 - AS309295442 0.1%5442.0 -- HUTCB Hidrotechnical Faculty - Technical University 10 - AS14453 14298 0.2%3574.5 -- 11 - AS40256 12118 0.2%3029.5 -- 12 - AS261142746 0.0%2746.0 -- 13 - AS16637 177437 2.6%2534.8 -- MTNNS-AS 14 - AS126877497 0.1%2499.0 -- URAN URAN Autonomous system 15 - AS139564516 0.1%2258.0 -- 16 - AS391074169 0.1%2084.5 -- INTERLAN-AS Asociatia Interlan 17 - AS436561728 0.0%1728.0 -- INTERTELECOM-TV Teleradiocompany Intertelecom, Sumy, UA 18 - AS974714490 0.2%1610.0 -- EZINTERNET-AS-AP EZInternet Pty Ltd 19 - AS26407 41941 0.6%1553.4 -- 20 - AS427041474 0.0%1474.0 -- ELITENETWORK-AS SC Elite Network Communications SRL TOP 20 Unstable Prefixes Rank Prefix Upds % Origin AS -- AS Name 1 - 192.96.14.0/2482392 1.1% AS16637 -- MTNNS-AS 2 - 192.96.13.0/2482387 1.1% AS16637 -- MTNNS-AS 3 - 209.163.125.0/24 51721 0.7% AS14390 -- 4 - 12.108.254.0/24 41230 0.6% AS26829 -- 5 - 83.228.59.0/2439369 0.6% AS8866 -- BTC-AS Bulgarian Telecommunication Company Plc. 6 - 83.228.61.0/2438971 0.5% AS8866 -- BTC-AS Bulgarian Telecommunication Company Plc. 7 - 83.228.103.0/24 37256 0.5% AS8866 -- BTC-AS Bulgarian Telecommunication Company Plc. 8 - 203.83.127.0/24 26107 0.4% AS17540 -- MTL-AP Modern Terminals Limited 9 - 12.106.30.0/2425664 0.4% AS22072 -- 10 - 125.23.208.0/20 22400 0.3% AS9498 -- BBIL-AP BHARTI BT INTERNET LTD. 11 - 64.79.128.0/1921033 0.3% AS23005 -- 12 - 81.10.26.0/24 20951 0.3% AS8452 -- TEDATA TEDATA 13 - 81.10.1.0/24 20779 0.3% AS8452 -- TEDATA TEDATA 14 - 81.10.2.0/24 20730 0.3% AS8452 -- TEDATA TEDATA 15 - 81.10.27.0/24 20700 0.3% AS8452 -- TEDATA TEDATA 16 - 196.219.249.0/24 20500 0.3% AS8452 -- TEDATA TEDATA 17 - 196.219.245.0/24 20495 0.3% AS8452 -- TEDATA TEDATA 18 - 196.219.244.0/24 20494 0.3% AS8452 -- TEDATA TEDATA 19 - 196.219.248.0/24 20494 0.3% AS8452 -- TEDATA TEDATA 20 - 196.219.236.0/24 20492 0.3% AS8452 -- TEDATA TEDATA Details at http://bgpupdates.potaroo.net Copies of this report are mailed to: nanog@merit.edu [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
The Cidr Report
This report has been generated at Fri Dec 14 21:14:06 2007 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org for a current version of this report.
Recent Table History
Date PrefixesCIDR Agg
07-12-07245371 156245
08-12-07245586 156720
09-12-07245616 157178
10-12-07245707 157536
11-12-07245869 157959
12-12-07245898 158252
13-12-07246138 156202
14-12-07244644 156696
AS Summary
26973 Number of ASes in routing system
11377 Number of ASes announcing only one prefix
1510 Largest number of prefixes announced by an AS
AS7018 : ATT-INTERNET4 - ATT WorldNet Services
89093632 Largest address span announced by an AS (/32s)
AS721 : DISA-ASNBLK - DoD Network Information Center
Aggregation Summary
The algorithm used in this report proposes aggregation only
when there is a precise match using the AS path, so as
to preserve traffic transit policies. Aggregation is also
proposed across non-advertised address space ('holes').
--- 14Dec07 ---
ASnumNetsNow NetsAggr NetGain % Gain Description
Table 244770 1566968807436.0% All ASes
AS4755 1495 492 100367.1% VSNL-AS Videsh Sanchar Nigam
Ltd. Autonomous System
AS18566 1034 33 100196.8% COVAD - Covad Communications
Co.
AS9498 1059 69 99093.5% BBIL-AP BHARTI BT INTERNET
LTD.
AS4323 1381 393 98871.5% TWTC - Time Warner Telecom,
Inc.
AS22773 830 76 75490.8% CCINET-2 - Cox Communications
Inc.
AS11492 1166 434 73262.8% CABLEONE - CABLE ONE
AS8151 1155 428 72762.9% Uninet S.A. de C.V.
AS6478 1084 409 67562.3% ATT-INTERNET3 - ATT WorldNet
Services
AS19262 857 215 64274.9% VZGNI-TRANSIT - Verizon
Internet Services Inc.
AS17488 917 279 63869.6% HATHWAY-NET-AP Hathway IP Over
Cable Internet
AS4134 978 360 61863.2% CHINANET-BACKBONE
No.31,Jin-rong Street
AS15270 589 42 54792.9% AS-PAETEC-NET - PaeTec
Communications, Inc.
AS18101 610 96 51484.3% RIL-IDC Reliance Infocom Ltd
Internet Data Centre,
AS6197 1033 520 51349.7% BATI-ATL - BellSouth Network
Solutions, Inc
AS2386 1319 810 50938.6% INS-AS - ATT Data
Communications Services
AS19916 569 76 49386.6% ASTRUM-0001 - OLM LLC
AS7018 1510 1028 48231.9% ATT-INTERNET4 - ATT WorldNet
Services
AS7545 669 199 47070.3% TPG-INTERNET-AP TPG Internet
Pty Ltd
AS4812 539 93 44682.7% CHINANET-SH-AP China Telecom
(Group)
AS4766 818 374 44454.3% KIXS-AS-KR Korea Telecom
AS6517 610 182 42870.2% YIPESCOM - Yipes
Communications, Inc.
AS17676 504 90 41482.1% GIGAINFRA BB TECHNOLOGY Corp.
AS7011 994 581 41341.5% FRONTIER-AND-CITIZENS -
Frontier Communications of
America, Inc.
AS4808 515 122 39376.3% CHINA169-BJ CNCGROUP IP
network China169 Beijing
Province Network
AS3356 835 451 38446.0% LEVEL3 Level 3 Communications
AS9443 450 76 37483.1% INTERNETPRIMUS-AS-AP Primus
Telecommunications
AS4668 519 169 35067.4% LGNET-AS-KR LG CNS
AS16814 427 93 33478.2% NSS S.A.
AS3602 396 75 32181.1% AS3602-RTI - Rogers Telecom
Inc.
AS16852 395 75 32081.0% LVLT-16852 - Level 3
Re: IEEE 40GE 100GE
I have three practical uses for 40G at present... First and most obvious is router to router. In this case, if the routers are in the same cage, there's little reason to want to be able to push more than 100 feet. (The same applies to aggregation switches and similar.) The second use is links around a campus. Now we're pushing distances. ESPECIALLY when you consider budgets due to patch losses and so on. In this case, 3-4km is probably still adequate for me in most cases. (Equinix's DC area will probably work with 3km as long as they don't take it through 8 patch panels before they get to you. DC3 is the only one to be concerned about because of the added inter-building distance.) The third use for this is across a metro area. (Lets face it, it's hard to find a good amount of space in any one location.) In this case, in most areas, I have a need to use DWDM. I would still need to do this on dark fiber since some locations can quite easily push more than 40 gigs back to the core. So I either double my fiber costs and buy two pair to each location or I use DWDM. So now the concern is when my DWDM vendor will be able to mux these together. That, above and beyond how far can you push this? If I've got a long run and no place to put an amplifier in the middle, even 10km may mean I'm SOL. So from my POV, I have a vested insterest in all three options and the relevant orders of magnitude between each one. For the sake of instroducing the technology, should it not persue the same path that 10GE did? That is, focus on the first condition with an eye to the second and add the third once you've got the problems with the first two worked out? On Wed, Dec 12, 2007 at 06:27:55AM -0500, Robert E. Seastrom wrote: A practical question here: does anyone know offhand if 4km reach is adequate for interbuilding access (i.e., DC[124] to DC3) access at Equinix Ashburn, including worst-case interior wiring and cross connects? I'm thinking that's cutting it close. The enterprise people are substantially less likely to find themselves with a lot of interconnections in a GCE (Ginormous Campus Environment) than we are, and I suspect that skews the 90% number a bit. Folks who are more familiar with the layout of other facilities may wish to chime in here. ---Rob Bora Akyol [EMAIL PROTECTED] writes: IEEE is seeking feedback from network operators etc on the reach requirements for 40GE 100GE. If you have direct feedback to give, please contact Chris Cole directly (email address below). This is very important as it will directly impact how much you pay for those soon to be cherished 40 100 GE hardware in the future. I believe information on how many patch panel connections you expect the links to go through is also highly valued. Regards Bora From: Chris Cole [EMAIL PROTECTED] Subject: Re: [HSSG] Reach Ad Hoc To: [EMAIL PROTECTED] Date: Tue, 11 Dec 2007 16:21:31 -0800 Reply-To: Chris Cole [EMAIL PROTECTED] During the November HSSG meeting, optics vendors made a presentation proposing changing the 10km reach objective to 3km or 4km. One of my motivations for working on the proposal was informal input from a number of 100GE end users that 90% of their data center and short interconnect needs would be met by a reach objective less then 4km (versus 10km.) With such a reach distribution, a 4km or less optimized reach objective would result in overall cost savings. As part of the HSSG effort to review this proposal, numerous requests, both informal as well as from the HSSG chair and Reach Ad Hoc chair, have been made for contributions to quantify the 10km and under reach distribution. While the optics vendors as suppliers can accurately represent the relative costs of optics alternatives, they can not represent end user requirements. To date, we have seen no end user presentation or data supporting changing the 10km reach objective to 4km or less. Unless such contributions are forthcoming, it is likely that there will be no motivation to make the change. This sentiment can be seen in the 12/7 Reach Ad Hoc conference call minutes. I would encourage any HSSG participant that views their volume 100GE SMF needs as better met by a 4km or shorter reach objective to make a contribution containing reach distribution data in support of this position. Otherwise we will move forward with the existing approved objectives. Chris From: Andy Moorwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 6:03 AM To: [EMAIL PROTECTED] Subject: [HSSG] Reach Ad Hoc Colleagues, the meeting notes from our call last week are now posted on the IEEE website http://www.ieee802.org/3/hssg/public/reach/MeetingNotes_r1_1207.pdf Thank you for your contributions Andy -- --- Wayne Bouchard [EMAIL PROTECTED] Network Dude
Somewhat bizarre scenario... (Fiber distance)
Given this 40G/100G topic, I figured I'd bring this up given the topics. I've got a link that is testing out at 29.5db loss @ 1550. Its 107km. I seem to remember a few good solutions for 1Gb/s or 2.5Gb/s that can handle a link like this, but its been a while and I can't seem to remember. I can put a regen in there if I have to, but that or an EDFA both seem like ugly solutions since I just need 1 wave. Shoot me a few suggestions? Thanks in advance, Deepak
Re: Somewhat bizarre scenario... (Fiber distance)
Deepak Jain wrote: Given this 40G/100G topic, I figured I'd bring this up given the topics. I've got a link that is testing out at 29.5db loss @ 1550. Its 107km. I seem to remember a few good solutions for 1Gb/s or 2.5Gb/s that can handle a link like this, but its been a while and I can't seem to remember. I can put a regen in there if I have to, but that or an EDFA both seem like ugly solutions since I just need 1 wave. Responding to myself. I've tentatively had it lit with an MRV LR2 type optic which is xmitting at 0 db (min rated is -2db) which *should* just make it... but I was hoping for a solution that wasn't as... tight. I'd hate to have someone have to test through a few spares to find a replacement optic that was hot enough. Thanks. DJ
Re: Somewhat bizarre scenario... (Fiber distance)
On Fri, 14 Dec 2007, Deepak Jain wrote: Given this 40G/100G topic, I figured I'd bring this up given the topics. I've got a link that is testing out at 29.5db loss @ 1550. Its 107km. I seem to remember a few good solutions for 1Gb/s or 2.5Gb/s that can handle a link like this, but its been a while and I can't seem to remember. I can put a regen in there if I have to, but that or an EDFA both seem like ugly solutions since I just need 1 wave. Shoot me a few suggestions? http://www.finisar.com/product-113-1_Gigabit_CWDM_GBIC_with_APD_Receiver_(FTR-1619-xx) 30dB. Will do more, we've done ~180km (~36dB) with one of those. -- Mikael Abrahamssonemail: [EMAIL PROTECTED]
RE: IEEE 40GE 100GE
The 100G 40km reach (the 40G in your email I am assuming is a type) will be a black/white code, and it will not support DWDM. Chris -Original Message- From: Wayne E. Bouchard [mailto:[EMAIL PROTECTED] Sent: Friday, December 14, 2007 11:42 AM To: Robert E. Seastrom Cc: Bora Akyol; nanog@merit.edu; Chris Cole Subject: Re: IEEE 40GE 100GE I have three practical uses for 40G at present... First and most obvious is router to router. In this case, if the routers are in the same cage, there's little reason to want to be able to push more than 100 feet. (The same applies to aggregation switches and similar.) The second use is links around a campus. Now we're pushing distances. ESPECIALLY when you consider budgets due to patch losses and so on. In this case, 3-4km is probably still adequate for me in most cases. (Equinix's DC area will probably work with 3km as long as they don't take it through 8 patch panels before they get to you. DC3 is the only one to be concerned about because of the added inter-building distance.) The third use for this is across a metro area. (Lets face it, it's hard to find a good amount of space in any one location.) In this case, in most areas, I have a need to use DWDM. I would still need to do this on dark fiber since some locations can quite easily push more than 40 gigs back to the core. So I either double my fiber costs and buy two pair to each location or I use DWDM. So now the concern is when my DWDM vendor will be able to mux these together. That, above and beyond how far can you push this? If I've got a long run and no place to put an amplifier in the middle, even 10km may mean I'm SOL. So from my POV, I have a vested insterest in all three options and the relevant orders of magnitude between each one. For the sake of instroducing the technology, should it not persue the same path that 10GE did? That is, focus on the first condition with an eye to the second and add the third once you've got the problems with the first two worked out? On Wed, Dec 12, 2007 at 06:27:55AM -0500, Robert E. Seastrom wrote: A practical question here: does anyone know offhand if 4km reach is adequate for interbuilding access (i.e., DC[124] to DC3) access at Equinix Ashburn, including worst-case interior wiring and cross connects? I'm thinking that's cutting it close. The enterprise people are substantially less likely to find themselves with a lot of interconnections in a GCE (Ginormous Campus Environment) than we are, and I suspect that skews the 90% number a bit. Folks who are more familiar with the layout of other facilities may wish to chime in here. ---Rob Bora Akyol [EMAIL PROTECTED] writes: IEEE is seeking feedback from network operators etc on the reach requirements for 40GE 100GE. If you have direct feedback to give, please contact Chris Cole directly (email address below). This is very important as it will directly impact how much you pay for those soon to be cherished 40 100 GE hardware in the future. I believe information on how many patch panel connections you expect the links to go through is also highly valued. Regards Bora From: Chris Cole [EMAIL PROTECTED] Subject: Re: [HSSG] Reach Ad Hoc To: [EMAIL PROTECTED] Date: Tue, 11 Dec 2007 16:21:31 -0800 Reply-To: Chris Cole [EMAIL PROTECTED] During the November HSSG meeting, optics vendors made a presentation proposing changing the 10km reach objective to 3km or 4km. One of my motivations for working on the proposal was informal input from a number of 100GE end users that 90% of their data center and short interconnect needs would be met by a reach objective less then 4km (versus 10km.) With such a reach distribution, a 4km or less optimized reach objective would result in overall cost savings. As part of the HSSG effort to review this proposal, numerous requests, both informal as well as from the HSSG chair and Reach Ad Hoc chair, have been made for contributions to quantify the 10km and under reach distribution. While the optics vendors as suppliers can accurately represent the relative costs of optics alternatives, they can not represent end user requirements. To date, we have seen no end user presentation or data supporting changing the 10km reach objective to 4km or less. Unless such contributions are forthcoming, it is likely that there will be no motivation to make the change. This sentiment can be seen in the 12/7 Reach Ad Hoc conference call minutes. I would encourage any HSSG participant that views their volume 100GE SMF needs as better met by a 4km or shorter reach objective to make a contribution containing reach distribution data in support of this position. Otherwise we will move forward with the existing approved objectives. Chris From: Andy Moorwood [mailto:[EMAIL PROTECTED] Sent: Tuesday,
