- Test - lists.nanog.org

Congestion control train-wreck workshop at Stanford: Call for Demos
by nanditad＠stanford.edu 06 Sep '07

06 Sep '07

Congestion control train-wreck workshop at Stanford: Call for Demos We would like to invite you to a two-day congestion control workshop, titled "Train-wrecks and congestion control: What happens if we do nothing?", which we are hosting at Stanford on 31 March - 1 April, 2008. Spurred on by a widespread belief that TCP is showing its age and needs replacing - and a deeper understanding of the dynamics of congestion control - the research community has brought forward many new congestion control algorithms. There has been lots of debate about the relative merits and demerits of the new schemes; and a standardization effort is under way in the IETF. But before the next congestion control mechanism is deployed, it will need to be deployed widely in operating systems and - in some cases - in switches and routers too. This will be a long road, requiring the buy-in of many people: Researchers, product developers and business leaders too. Our own experience of proposing new congestion control algorithms has been met with the challenge: "Show me the compelling need for a new congestion control mechanisms?", and "What will really happen to the Internet (and my business) if we keep TCP just the way it is?" As a community, we need examples that are simple to understand, and demonstrate a compelling need for change. We call them the "Train wreck scenarios". Examples might show that distribution of video over wireless in the home will come to a halt without new algorithms. Or that P2P traffic will bring the whole network crashing down. Or that huge, high-performance data-centers need new algorithms. Whatever your favorite example, we believe that if we are collectively armed with a handful of mutually agreed examples, it will be much easier to make a business case for change. Or put another way, if we can't articulate compelling examples to industry leaders, then is the cost and risk of change worth it? The goal of the workshop is to identify a handful of really compelling demonstrations of the impending train-wreck. The outcome will be a set of canonical examples that we will use to persuade industry of the need for change. We are deliberately inviting you many months ahead of time - to give you time to create your compelling train-wreck demonstration. You can choose the way you present your demonstration: You could bring equipment and show a live-demo; you could show simulations or animations; or you could produce a video showing a real or synthetic demo. Whatever method you choose, the goal is to create a case that will persuade a mildly-technical but influential business leader of the need for change. We will invite a panel of judges to give prizes for the most compelling examples in two categories: (1) The Overall Most Compelling Example, which will be judged on a combination of the technical merits and the presentation of the scenario, and (2) The Most Technically Compelling Example, which will be judged on its technical merit alone, without consideration of the way it is presented. The whole purpose of the workshop it to focus on the {\em problem}, not the solutions. We are most definitely {\em not} interested in your favorite scheme, or ours. So we need some ground-rules. \begin{center} {\em No-one is allowed to mention a specific mechanism, algorithm or proposal at any time during the workshop: Not in their talk, not in a panel, and not in questions to the speakers. The only mechanisms that will be allowed mention are: TCP (in its standard and deployed flavors), and idealized alternatives for purposes of demonstration. For example, comparing TCP with an oracle that provides instantaneous optimal rates to each flow.} \end{center} Attendance to the workshop will be by invitation only - to keep the discussion focused and lively. We will video the entire workshop and all the demonstrations, and make it publicly available on the Internet. We will make any proceedings and talks available too. The goal is to open up the demonstrations for public scrutiny and feedback after the event. The event is hosted by the Stanford Clean Slate Program - http://cleanslate.stanford.edu - and local arrangements will be made by Nick McKeown and Nandita Dukkipati. The workshop has received offers of support and funding from Cisco Systems and Microsoft. We hope to make a limited number of travel grants available. We have a small Program Committee (listed below) to select the final demonstrations. We are soliciting a 1-page description of your demo. Please note the following dates. Important Dates: =============== Workshop: 31 March - 1 April, 2008 1-page demo description submission deadline: 1 Dec, 2007 Notification of acceptance: 15 Dec, 2007 Final demo submissions: 17 March, 2008 Last date for demo withdrawals: 25 March, 2008 Please email your initial 1-page submissions to: Nandita Dukkipati <nanditad(a)stanford.edu> and Nick McKeown <nickm(a)stanford.edu> Best wishes, and we hope to see you in Stanford! Nandita Dukkipati Nick McKeown Program Committee: ================== 1. Albert Greenberg, Microsoft Research 2. Peter Key, Microsoft Research 3. Flavio Bonomi, Cisco 4. Bruce Davie, Cisco 5. Steven Low, Caltech 6. Frank Kelly, Cambridge 7. Lars Eggert, Nokia Research/IETF 8. Nick McKeown, Stanford 9. Guru Parulkar, Stanford 10. Nandita Dukkipati, Stanford/Cisco/Princeton

14 22

TeliaSonera routing issue / microsoft.com
by Pekka Savola 06 Sep '07

06 Sep '07

Hi - TeliaSonera has reported routing problem due to prefix filtering leaks / max-prefix triggering, starting around 0616 UTC. I guess some others are seeing this as well. I wonder what was the more exact reason, and why the problem still persists after about 6 hours. In particular, our customers have noticed this with various sites related to Microsoft, including e.g., VoIP systems failing because contacting some active-x site failed. Is there a looking glass, traceroute server, or sensible contact info for someone at AS 8075 to check what the routing looks like from that perspective? (Traceroute works from our upstream, but not from here, which suggests a potential return path issue for e.g., 193.166.0.0/15, pingable address 193.166.255.241). ;; ANSWER SECTION: www.microsoft.com. 1088 IN CNAME toggle.www.ms.akadns.net. toggle.www.ms.akadns.net. 57 IN CNAME g.www.ms.akadns.net. g.www.ms.akadns.net. 57 IN CNAME lb1.www.ms.akadns.net. lb1.www.ms.akadns.net. 57 IN A 207.46.192.254 lb1.www.ms.akadns.net. 57 IN A 207.46.193.254 lb1.www.ms.akadns.net. 57 IN A 207.46.19.190 lb1.www.ms.akadns.net. 57 IN A 207.46.19.254 1 s-b4-link.telia.net (213.248.97.93) 0.620 ms 0.498 ms 0.409 ms 2 s-bb2-link.telia.net (213.248.66.13) 0.762 ms 0.597 ms 0.721 ms 3 kbn-bb2-pos0-0-0.telia.net (213.248.65.29) 10.231 ms 10.276 ms 10.215 ms 4 nyk-bb2-link.telia.net (213.248.82.101) 94.660 ms 94.670 ms 94.640 ms 5 sjo-bb1-link.telia.net (80.91.254.177) 161.549 ms 161.542 ms 161.530 ms .. stops here. If it works (from upstream) it continues as follows: 6 microsoft-110312-sjo-bb (213.248.86.70) 161.421 ms 161.818 ms 157.519 ms 7 ge-6-3-0-44.sjc-64cb-1a.ntwk.msn.net (207.46.44.98) 161.814 ms 155.456 ms 157.559 ms 8 ge-1-0-0-0.bay-64c-1a.ntwk.msn.net (207.46.37.158) 156.229 ms 158.292 ms 156.223 ms -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

3 2

PKI operators anyone?
by Joe Maimon 06 Sep '07

06 Sep '07

MS-PRESS recommended design guidelines for multi-tier PKI systems for validity periods are along the lines of 8 years for the root 4 years for the "policy" 2 years for the "issuing" 1 year for the issued certificate This is ostensibly due to fears of brute force cracking of the private keys over the root key's validity period. Accompanied with this recommendation is one for key lengths of 4096 for the root 2048 for the policy 1024 for the issuing and for the issued. I have found the downside to this: Constant renewals every single year of either minor or major impact. While MS-AD pki client implementations seem to handle most of the (except for the root) resigning just fine, external implementation struggle with some details, such as "chaining up to the root" trusting (thereby only requiring them to trust the root cert) and such as trusting two different certs (for an issuing CA that gets resigned) but that have the same common name, hence loads of fun every 11 months or so. I am about to recommend a re implementation along these lines 80 years for the root, 4096bit key 35 years for the policy, 4096bit key 15 years for the issuing, ?bit key <=5 years for the issued certificates. Good idea? Bad Idea? Comments? Are all pki client implementation in the wild 4096bit compatible? Thanks in advance, Joe

10 17

RE: PKI operators anyone?
by Paul Ferguson 06 Sep '07

06 Sep '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The only way a successful PKI will be deployed is if the U.S. Government takes a "hands-off" approach. Good luck with all that. $.02, - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.3 (Build 3017) wj8DBQFG33D9q1pz9mNUZTMRAg92AKC8oqVYWytmwC6Nzl44MKVucKKlvgCfX78t M5Wh+nBltJCqNYa6fiY+thE= =FGmF -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

1 0

Draft agenda for NANOG 41
by Steve Feldman 04 Sep '07

04 Sep '07

The NANOG Program Committee is please to announce the draft angenda for the NANOG 41 conference, to be held October 14-16 in Albuquerque, NM: SUNDAY, October 14 - Joint NANOG/ARIN IPv6 Workshop: 8:30am - 4:30pm - Tutorials 1:30pm - 3:00pm BGP Multihoming Techniques (part 1) - Philip Smith, Cisco Systems Layer 3 VPN for v4 & v6 in IP Core - Madhusudan Nanjanagud, Cisco Systems 3:30pm - 5:00pm BGP Multihoming Techniques (part 2) - Philip Smith, Cisco Systems - Newcomers meeting and reception: 3:30pm - 5:00pm - Community meeting - 5:30pm MONDAY, October 15 - General session: 9:00 - 12:30 9:00- 9:30 Opening Remarks 9:30-10:00 Perfect Storms, Internet Economics, and the Future of the Internet - David Meyer, Cisco/Univ. of Oregon 10:00-10:30 Resilient L2 VPNs - Ian Cowburn, Alcatel-Lucent 10:30-11:00 BREAK 11:00-11:30 From NetFlow to IPFIX: the evolution of IP flow information export - Brian Trammell, CERT/NetSA; Elisa Boschi, Hitachi Europe 11:30-12:30 Optical Panel - Moderator: Ted Seely, Sprint - General session: 2:00pm - 3:30pm 2:00- 2:30 LISP: A Level of Indirection for Routing Dino Farinacci, Cisco 2:30- 3:30 LISP-CONS: A Content distribution Overlay Network Service for LISP - David Meyer, Cisco/Univ. of Oregon 3:30- 4:00 Protection and Fault Recovery at Internet Peering Points using 802.1ag CFM - Rahul Vir, Foundry Networks - BOFs: 4:00pm - 5:30pm Peering BOF XVI - Bill Norton, Equinix - Beer 'n Gear - 5:30 - 7:30 TUESDAY, October 16 - General session - 9:00 - 12:00 9:00-10:00 KEYNOTE: Stephen Ryan, General Counsel, American Registry of Internet Numbers (ARIN) and Partner, McDermott, Will and Emery in Washington D.C. 10:00-10:30 BREAK 10:30-11:00 Have We Reached 1000 Prefixes Yet?: A snapshot of the global IPv6 routing table - Gert D�ring, SpaceNet AG, presented by CJ Aronson 11:00-12:00 EOTWAWKI: The end of the world, as we know it - Cathy Aronson, Daydream Imaging & Leo Bicknell, ISC - General session - 1:30 - 5:00 1:30- 2:00 IPv6 Transition & Operational Reality - Randy Bush, IIJ 2:00- 3:00 Lightning Talks! 3:00- 3:30 BREAK 3:30- 4:00 Integrating Networks - Nina Bargisen and Michael Lyngb�l, TDC 4:00- 4:15 Research Forum: BGP Protection Without Global Cooperation - Josh Karlin, University of New Mexico and Stephanie Forrest, University of New Mexico and Jennifer Rexford, Princeton University 4;15- 4:45 TBA 4:45- 5:00 Closing Remarks and Election Results This is a draft agenda, and will be subject to change until the meeting ends. For current information, see http://www.nanog.org. On Sunday, October 14, there will also be a special one-day workshop on IPv6 implementation, jointly sponsored by NANOG and ARIN. The week continues with the ARIN XX meeting on October 17-19. Finally, a few announcements from Merit: Meeting registration (https://www.nanog.org/registration/) is open and the lower registration rate is in effect through September 24. The group room rate at the hotel (http://www.nanog.org/mtg-0710/hotel.html) expires September 24. Note: make your reservation early as NANOG is meeting on the tail end of the International Balloon Fiesta. Hotel rooms will be in high demand, especially on Saturday night, Oct. 13. For additional meeting information, please see http://www.nanog.org/. See you in Albuquerque! Steve Feldman PC Chair

1 0

Re: Congestion control train-wreck workshop at Stanford: Call forDemos
by Christian Kuhtz 04 Sep '07

04 Sep '07

Lmao. Thanks, Sean, I just snorted my cup of freshly brewed coffee. Ouch. :-) ------Original Message------ From: Sean Donelan Sender: owner-nanog(a)merit.edu To: Stephen Stuart Cc: nanog Sent: Sep 4, 2007 10:30 AM Subject: Re: Congestion control train-wreck workshop at Stanford: Call forDemos On Tue, 4 Sep 2007, Stephen Stuart wrote: >>> Operators are probably more interested in the "fairness" part of >>> "congestion" than the "efficiency" part of "congestion." >> >> TCP's idea of fairness is a bit weird. Shouldn't it be per-user, not >> per-flow? > > How would you define "user" in that context? Operators always define the "user" as the person paying the bill. One bill, one user. Its fun to watch network engineers' heads explode. -- Sent from my BlackBerry.

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 31 Aug '07

31 Aug '07

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 bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 01 Sep, 2007 Report Website: http://thyme.apnic.net This report: http://thyme.apnic.net/ap-data/2007/09/01/0400 Analysis Summary ---------------- BGP routing table entries examined: 229742 Prefixes after maximum aggregation: 119898 Deaggregation factor: 1.92 Unique aggregates announced to Internet: 110820 Total ASes present in the Internet Routing Table: 26109 Prefixes per ASN: 8.80 Origin-only ASes present in the Internet Routing Table: 22732 Origin ASes announcing only one prefix: 11081 Transit ASes present in the Internet Routing Table: 3377 Transit-only ASes present in the Internet Routing Table: 77 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 20 Max AS path prepend of ASN (35389) 16 Prefixes from unregistered ASNs in the Routing Table: 10 Unregistered ASNs in the Routing Table: 6 Prefixes from 32-bit ASNs in the Routing Table: 6 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 11 Number of addresses announced to Internet: 1756836704 Equivalent to 104 /8s, 183 /16s and 51 /24s Percentage of available address space announced: 47.4 Percentage of allocated address space announced: 62.1 Percentage of available address space allocated: 76.4 Total number of prefixes smaller than registry allocations: 121719 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 53719 Total APNIC prefixes after maximum aggregation: 20575 APNIC Deaggregation factor: 2.61 Prefixes being announced from the APNIC address blocks: 50635 Unique aggregates announced from the APNIC address blocks: 21459 APNIC Region origin ASes present in the Internet Routing Table: 3046 APNIC Prefixes per ASN: 16.62 APNIC Region origin ASes announcing only one prefix: 809 APNIC Region transit ASes present in the Internet Routing Table: 467 Average APNIC Region AS path length visible: 3.6 Max APNIC Region AS path length visible: 15 Number of APNIC addresses announced to Internet: 313653792 Equivalent to 18 /8s, 177 /16s and 250 /24s Percentage of available APNIC address space announced: 77.7 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 116/6, 120/6, 124/7, 126/8, 202/7 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 108857 Total ARIN prefixes after maximum aggregation: 62963 ARIN Deaggregation factor: 1.73 Prefixes being announced from the ARIN address blocks: 80198 Unique aggregates announced from the ARIN address blocks: 31899 ARIN Region origin ASes present in the Internet Routing Table: 11791 ARIN Prefixes per ASN: 6.80 ARIN Region origin ASes announcing only one prefix: 4522 ARIN Region transit ASes present in the Internet Routing Table: 1091 Average ARIN Region AS path length visible: 3.4 Max ARIN Region AS path length visible: 14 Number of ARIN addresses announced to Internet: 343064576 Equivalent to 20 /8s, 114 /16s and 192 /24s Percentage of available ARIN address space announced: 75.7 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959 ARIN Address Blocks 24/8, 63/8, 64/5, 72/6, 76/8, 96/6, 199/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 48026 Total RIPE prefixes after maximum aggregation: 30905 RIPE Deaggregation factor: 1.55 Prefixes being announced from the RIPE address blocks: 44417 Unique aggregates announced from the RIPE address blocks: 29477 RIPE Region origin ASes present in the Internet Routing Table: 10130 RIPE Prefixes per ASN: 4.38 RIPE Region origin ASes announcing only one prefix: 5399 RIPE Region transit ASes present in the Internet Routing Table: 1605 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 20 Number of RIPE addresses announced to Internet: 325697152 Equivalent to 19 /8s, 105 /16s and 190 /24s Percentage of available RIPE address space announced: 74.7 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-44031 RIPE Address Blocks 62/8, 77/8, 78/7, 80/4, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 16441 Total LACNIC prefixes after maximum aggregation: 4422 LACNIC Deaggregation factor: 3.72 Prefixes being announced from the LACNIC address blocks: 14536 Unique aggregates announced from the LACNIC address blocks: 7794 LACNIC Region origin ASes present in the Internet Routing Table: 858 LACNIC Prefixes per ASN: 16.94 LACNIC Region origin ASes announcing only one prefix: 282 LACNIC Region transit ASes present in the Internet Routing Table: 144 Average LACNIC Region AS path length visible: 3.9 Max LACNIC Region AS path length visible: 19 Number of LACNIC addresses announced to Internet: 42168064 Equivalent to 2 /8s, 131 /16s and 111 /24s Percentage of available LACNIC address space announced: 62.8 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 189/8, 190/8, 200/7 AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 2683 Total AfriNIC prefixes after maximum aggregation: 1021 AfriNIC Deaggregation factor: 2.63 Prefixes being announced from the AfriNIC address blocks: 2261 Unique aggregates announced from the AfriNIC address blocks: 1335 AfriNIC Region origin ASes present in the Internet Routing Table: 206 AfriNIC Prefixes per ASN: 10.98 AfriNIC Region origin ASes announcing only one prefix: 69 AfriNIC Region transit ASes present in the Internet Routing Table: 36 Average AfriNIC Region AS path length visible: 3.9 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 7426304 Equivalent to 0 /8s, 113 /16s and 81 /24s Percentage of available AfriNIC address space announced: 22.1 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4755 1345 383 74 Videsh Sanchar Nigam Ltd. Aut 9583 1134 100 106 Sify Limited 4134 1071 11178 289 CHINANET-BACKBONE 9498 997 532 66 BHARTI BT INTERNET LTD. 4766 803 5441 319 Korea Telecom (KIX) 17488 796 52 55 Hathway IP Over Cable Interne 23577 786 34 682 Korea Telecom (ATM-MPLS) 7545 729 159 121 TPG Internet Pty Ltd 18101 595 119 50 Reliance Infocom Ltd Internet 4812 547 968 96 China Telecom (Shanghai) 1221 542 1951 424 Telstra Pty Ltd 4668 516 68 10 LG-EDS Systems Inc. 17676 503 10919 64 Softbank BB Corp. 4808 483 779 114 CNCGROUP IP network: China169 9443 464 122 77 Primus Telecommunications 4802 432 116 158 Wantree Development 7474 378 216 267 SingTel Optus Pty Ltd 17974 373 130 13 PT TELEKOMUNIKASI INDONESIA 4837 366 5104 167 chinanet IDC center beijing n 9829 363 258 14 BSNL National Internet Backbo ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1475 6074 993 AT&T WorldNet Services 4323 1324 992 373 Time Warner Telecom 2386 1214 618 748 AT&T Data Communications Serv 11492 1137 110 11 Cable One 6478 1132 324 169 AT&T Worldnet Services 6197 1028 718 511 BellSouth Network Solutions, 18566 1022 288 9 Covad Communications 174 975 6780 863 Cogent Communications 701 938 6577 716 UUNET Technologies, Inc. 7011 919 278 549 Citizens Utilities 20115 817 751 436 Charter Communications 1239 802 2718 563 Sprint 19262 775 2745 184 Verizon Global Networks 22773 762 2149 50 Cox Communications, Inc. 209 739 3836 584 Qwest 5668 657 176 23 CenturyTel Internet Holdings, 6517 590 165 37 Yipes Communications, Inc. 3356 587 10811 344 Level 3 Communications, LLC 852 576 1095 361 Telus Advanced Communications 15270 574 160 38 PaeTec.net -a division of Pae RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 702 492 1923 394 UUNET - Commercial IP service 24863 367 57 40 LINKdotNET AS number 9116 346 168 26 Goldenlines main autonomous s 3301 314 1456 294 TeliaNet Sweden 3320 314 6035 261 Deutsche Telekom AG 6746 287 130 263 Dynamic Network Technologies, 680 269 2045 257 DFN-IP service G-WiN 8708 262 420 241 Romania Data Systems S.A. 8220 260 445 243 COLT Telecommunications 3215 258 2424 98 France Telecom Transpac 8551 248 244 28 Bezeq International 3352 227 1868 38 Ibernet, Internet Access Netw 5089 222 1658 54 NTL Group Limited 3269 221 2775 73 TELECOM ITALIA 9121 214 1441 24 TTnet Autonomous System 3292 195 1379 175 TDC Tele Danmark 1257 192 1195 170 SWIPnet Swedish IP Network 3300 192 172 92 AUCS Communications Services 12479 192 578 6 Uni2 Autonomous System 3246 187 253 177 Song Networks LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 904 1974 205 UniNet S.A. de C.V. 11830 517 299 9 Instituto Costarricense de El 16814 426 26 9 NSS, S.A. 11172 371 114 57 Servicios Alestra S.A de C.V 7303 339 177 45 Telecom Argentina Stet-France 14522 333 28 7 SatNet S.A. 6471 322 75 33 ENTEL CHILE S.A. 22047 318 246 13 VTR PUNTO NET S.A. 14117 281 19 15 Telefonica del Sur S.A. 10481 278 104 9 Prima S.A. 11556 235 128 3 Cable-Wireless Panama 6147 227 178 24 Telefonica Del Peru 10620 223 62 23 TVCABLE BOGOTA 6503 201 170 82 AVANTEL, S.A. 23216 196 16 44 RAMtelecom Telecomunicaciones 20299 180 25 31 NEWCOM AMERICAS 8163 177 11 6 METROTEL REDES S.A. 7738 169 506 23 Telecomunicacoes da Bahia S.A 21826 168 30 59 INTERCABLE 19169 165 12 17 Telconet AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 283 868 224 The Internet Solution 8452 222 188 7 TEDATA 2018 148 301 115 Tertiary Education Network 6713 142 135 11 Itissalat Al-MAGHRIB 33783 126 8 11 EEPAD TISP TELECOM & INTERNET 5536 124 8 10 Internet Egypt Network 33776 100 6 3 Starcomms Nigeria Limited 24835 87 48 6 RAYA Telecom - Egypt 15475 75 84 4 Nile Online 2905 74 174 71 The Internetworking Company o 23889 69 24 15 MAURITIUS TELECOM 2561 62 6 2 Egyptian Universities Network 33774 47 29 25 AS Number for Telecom Algeria 5713 46 294 36 Telkom SA Ltd 16637 46 21 29 Johnnic e-Ventures 8524 31 2 10 AUCEGYPT Autonomous System 12455 29 6 3 Jambonet Autonomous system 21280 29 4 4 Swift Global Kenya Ltd.Is an 10798 27 16 1 Standard Bank of South Africa 21491 24 17 2 UTL On-line is RF broadband I Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4755 1345 1271 Videsh Sanchar Nigam Ltd. Aut 11492 1137 1126 Cable One 9583 1134 1028 Sify Limited 18566 1022 1013 Covad Communications 6478 1132 963 AT&T Worldnet Services 4323 1324 951 Time Warner Telecom 9498 997 931 BHARTI BT INTERNET LTD. 4134 1071 782 CHINANET-BACKBONE 17488 796 741 Hathway IP Over Cable Interne 22773 762 712 Cox Communications, Inc. 8151 904 699 UniNet S.A. de C.V. 5668 657 634 CenturyTel Internet Holdings, 7545 729 608 TPG Internet Pty Ltd 19262 775 591 Verizon Global Networks 6517 590 553 Yipes Communications, Inc. 18101 595 545 Reliance Infocom Ltd Internet 15270 574 536 PaeTec.net -a division of Pae 6197 1028 517 BellSouth Network Solutions, 19916 568 517 OLM LLC 11830 517 508 Instituto Costarricense de El List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 64250 RESERVED 122.171.0.0/24 9498 BHARTI BT INTERNET L 64250 RESERVED 122.171.1.0/24 9498 BHARTI BT INTERNET L 64586 PRIVATE 192.170.73.0/24 4845 Chung Hsiao East Roa 64501 RESERVED 195.189.160.0/24 35041 Crystone Autonomous 64586 PRIVATE 202.165.137.0/24 4845 Chung Hsiao East Roa 64586 PRIVATE 202.165.140.0/24 4845 Chung Hsiao East Roa 64586 PRIVATE 202.165.141.0/24 4845 Chung Hsiao East Roa 64586 PRIVATE 202.165.142.0/24 4845 Chung Hsiao East Roa 64586 PRIVATE 202.165.143.0/24 4845 Chung Hsiao East Roa 24410 UNALLOCATED 203.119.28.0/24 4134 CHINANET-BACKBONE Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 7.1.1.0/24 1239 Sprint 132.0.0.0/10 721 DLA Systems Automation Center 137.0.0.0/13 721 DLA Systems Automation Center 158.0.0.0/13 721 DLA Systems Automation Center 172.33.1.0/24 7018 AT&T WorldNet Services 192.0.10.0/24 9498 BHARTI BT INTERNET LTD. 192.44.0.0/24 5501 Fraunhofer Gesellschaft 192.44.0.0/19 702 UUNET - Commercial IP service 192.70.164.0/24 25689 National Research Council of 192.153.136.0/21 721 DLA Systems Automation Center 192.172.0.0/19 721 DLA Systems Automation Center Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:18 /9:9 /10:15 /11:38 /12:134 /13:260 /14:471 /15:919 /16:9620 /17:4069 /18:6596 /19:13963 /20:16197 /21:14868 /22:19127 /23:20067 /24:120967 /25:772 /26:1030 /27:505 /28:84 /29:5 /30:0 /31:0 /32:8 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6478 1131 1132 AT&T Worldnet Services 11492 1129 1137 Cable One 18566 1004 1022 Covad Communications 9583 968 1134 Sify Limited 2386 907 1214 AT&T Data Communications Serv 7018 816 1475 AT&T WorldNet Services 7011 813 919 Citizens Utilities 6197 781 1028 BellSouth Network Solutions, 23577 777 786 Korea Telecom (ATM-MPLS) 4755 727 1345 Videsh Sanchar Nigam Ltd. Aut 9498 669 997 BHARTI BT INTERNET LTD. 17488 619 796 Hathway IP Over Cable Interne 4766 601 803 Korea Telecom (KIX) 19916 563 568 OLM LLC 4323 557 1324 Time Warner Telecom 6517 556 590 Yipes Communications, Inc. 15270 538 574 PaeTec.net -a division of Pae 5668 522 657 CenturyTel Internet Holdings, 4668 506 516 LG-EDS Systems Inc. 18101 500 595 Reliance Infocom Ltd Internet Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:8 7:1 8:86 12:1810 13:1 15:19 16:3 17:3 18:13 20:36 24:967 25:1 32:56 33:3 38:349 40:60 41:321 44:2 47:4 52:4 55:3 56:3 57:25 58:471 59:386 60:367 61:1016 62:927 63:2002 64:3189 65:2369 66:3402 67:804 68:658 69:1969 70:448 71:105 72:1396 73:2 74:642 75:262 76:128 77:330 78:48 80:826 81:826 82:576 83:357 84:607 85:805 86:340 87:488 88:279 89:973 90:25 91:522 97:5 116:315 117:154 118:9 121:270 122:595 123:170 124:644 125:988 128:274 129:216 130:139 131:363 132:55 133:9 134:197 135:34 136:189 137:81 138:153 139:72 140:499 141:173 142:379 143:255 144:299 145:46 146:329 147:123 148:412 149:148 150:110 151:159 152:87 153:119 154:3 155:260 156:160 157:214 158:158 159:171 160:113 161:96 162:175 163:180 164:476 165:394 166:275 167:297 168:515 169:123 170:387 171:22 172:2 189:71 190:1005 192:5742 193:3972 194:3191 195:2296 196:974 198:3823 199:3283 200:5094 201:1184 202:7371 203:7710 204:3928 205:1972 206:2418 207:2840 208:2815 209:3479 210:2458 211:1087 212:1314 213:1482 214:413 215:41 216:3987 217:1191 218:325 219:382 220:1028 221:415 222:262 End of report

1 0

New version of Multi-Router Looking Glass (MRLG) released *SECURITY FIX*
by John Fraizer 31 Aug '07

31 Aug '07

A new version (v 5.4.1) of the Multi-Router Looking Glass has been released. Version 5.4.1 includes some minor updates I've made over the past year or so and also includes traps to prevent your looking-glass from being used to exploit the recent flaw discussed at http://tinyurl.com/2x8jpx All users of MRLG are strongly encouraged to update to the latest release. The MRLG source code can be found at: http://www.op-sec.us/mrlg/source/ If you have never seen MRLG in action, it is available for use at http://www.op-sec.us/mrlg/

1 0

Network Operations Guide
by Kim Onnel 31 Aug '07

31 Aug '07

Hello, My customer grew from a small enterprise to an SP/Mobile operator network very quickly. I want to guide them on how to operate their network, so I am looking for a document for this. On the top of my head and please add your suggestions: 1) Change Management 2) Network Management 3) Daily Operational tasks/process Let me explain what's on my mind for each point above: 1) I can think of RANCID and TACACS+ in terms of configurations, but they also do hardware changes that affects the network without any strict procedures (example: add a switch and start an STP loop) 2) This I can get, but would also welcome suggestions, NMS, SNMP, netflow…. 3) Ticketing system, escalation procedures, troubleshooting documents, backup procedures, inventory… Your valuable input would be highly appreciated,. Regards, Kim

9 11

[urgent assistance] 198.32.0.0/16 - Disappeared...
by Fergie 31 Aug '07

31 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paging Bill Manning... Unfortunately, we've tried to reach Bill, as well as other folks at EP.NET to no avail, and this is impacting us quite negatively. [snip] Not available in any routing tables I have access to or any of the looking glasses from http://www.nanog.org/lookingglass.html. this is significant because any in-addr blocks that are authoritative @ flag.ep.net and dot.ep.net will now suffer from reverse name resolution issues. - From ATT route server: route-server>sh ip bgp 198.32.4.13 % Network not in table - From CerfNET route server: route-server>sh ip bgp 198.32.4.13 % Network not in table Allstream Toronto: route-server.east>sh ip bgp 198.32.4.13 % Network not in table This has been a problem since yesterday evening. [snip] FYI, some of our address space has been sub-allocated via EP.net and relies on it's reachability: [DOMAIN whois information for EP.NET ] Domain Name: EP.NET Namespace: ICANN Unsponsored Generic TLD - http://www.icann.org TLD Info: See IANA Whois - http://www.iana.org/root-whois/net.htm Registry: VeriSign, Inc. - http://www.verisign-grs.com Registrar: NETWORK SOLUTIONS, LLC. - http://www.networksolutions.com Whois Server: whois.networksolutions.com Name Server[whois+dns with ip] DOT.EP.NET 198.32.2.10 Name Server[from whois+dns, whois ip]: DOT.EP.NET 2001:478:6:0:230:48FF:FE22:6A29 Name Server[whois+dns with ip] FLAG.EP.NET 198.32.4.13 Updated Date: 11-Jan-2007 Creation Date: 09-Dec-1994 Expiration Date: 08-Dec-2012 Status: clientTransferProhibited [whois.networksolutions.com] Welcome to the Network Solutions Registrar WHOIS Server. The IP address from which you have visited the Network Solutions Registrar WHOIS database is contained within a list of IP addresses that may have failed to abide by Network Solutions' WHOIS policy. Failure to abide by this policy can adversely impact our systems and servers, preventing the processing of other WHOIS requests. To see the Network Solutions WHOIS Policy, click on or copy and paste the following URL into your browser: http://www.networksolutions.com/whois/index.jhtml If you feel that you have received this message in error, please contact us at: whoisquery(a)networksolutions.com and include the following information: Whois Query: domain ep.net YOUR IP address is 216.151.198.186 Date and Time of Query: Fri May 11 21:39:55 EDT 2007 Reason Code: CE [whois.networksolutions.com] Please contact me off-list is you have any inisght into this. Thanks, - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.1 (Build 1012) wj8DBQFGRRydq1pz9mNUZTMRAt1RAJ0daUTj2zsy4yw9Yq83mTgQdYBXcQCg+lgC Hs2XTn1hp42IjMLXmTfU4Vs= =D8x5 -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

5 6