- Test - lists.nanog.org

RE: issues Level3 versus rest of the world?, looks good from Berlin...
by Security Admin (NetSec) 01 Jul '07

01 Jul '07

Looks good from berlin too: Show Level 3 (Berlin, Germany) Traceroute to 64.26.31.117 1 ae-31-55.ebr1.Berlin1.Level3.net (4.68.108.158) 4 msec ae-31-51.ebr1.Berlin1.Level3.net (4.68.108.30) 0 msec ae-31-53.ebr1.Berlin1.Level3.net (4.68.108.94) 0 msec 2 ae-3.ebr2.Dusseldorf1.Level3.net (4.69.133.146) 12 msec 16 msec 20 msec 3 ae-3.ebr2.Dusseldorf1.Level3.net (4.69.133.146) 16 msec 20 msec 16 msec 4 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 16 msec 24 msec 16 msec 5 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 20 msec 16 msec 20 msec 6 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 36 msec 24 msec 32 msec 7 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 36 msec 36 msec 36 msec 8 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 108 msec ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 112 msec ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 116 msec 9 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 112 msec 108 msec 108 msec 10 ae-2.ebr3.Atlanta2.Level3.net (4.69.132.85) 120 msec 124 msec 124 msec 11 ae-2.ebr3.Atlanta2.Level3.net (4.69.132.85) 128 msec 128 msec 124 msec 12 ae-5-5.car1.Tampa1.Level3.net (4.69.133.49) 140 msec 136 msec 164 msec 13 ae-5-5.car1.Tampa1.Level3.net (4.69.133.49) 136 msec 140 msec 136 msec 14 e1-11-level3.co2.tpax.as30217.net (4.71.0.10) 140 msec 140 msec 140 msec 15 e1-11-level3.co2.tpax.as30217.net (4.71.0.10) 136 msec PROGRESS-TE.car3.Tampa1.Level3.net (4.71.0.18) 136 msec e1-11-level3.co2.tpax.as30217.net (4.71.0.10) 136 msec 16 64.26.31.117 [AS30217 {DESYNC}] 140 msec 140 msec 140 msec c/o http://lg.level3.net/traceroute/traceroute.cgi?site=ber1&target=64.26.31.117 -- This mail was scanned by BitDefender For more informations please visit http://www.bitdefender.com

2 1

issues Level3 versus rest of the world?
by Peter Dambier 01 Jul '07

01 Jul '07

I cannot http 64.26.31.117 traceroute to 64.26.31.117 (64.26.31.117), 30 hops max, 40 byte packets 1 krzach.peter-dambier.de (192.168.48.2) 1.022 ms 1.499 ms 1.685 ms 2 * * * 3 217.0.78.58 75.464 ms 83.260 ms 91.327 ms 4 f-ea5.F.DE.net.DTAG.DE (62.154.16.161) 108.374 ms 108.407 ms 116.207 ms 5 Te-4-4.car2.Frankfurt1.Level3.net (4.68.110.253) 134.233 ms * * 6 * * ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126) 160.320 ms 7 ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125) 154.145 ms 171.149 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 171.099 ms 8 ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 148.639 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 148.567 ms ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 166.351 ms 9 ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 184.331 ms 184.365 ms 188.637 ms 10 ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 188.671 ms ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133) 217.410 ms ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137) 217.444 ms 11 ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141) 233.065 ms * * 12 ae-78.ebr2.Atlanta2.Level3.net (4.69.134.53) 233.085 ms * * 13 * * * 14 ae-5-5.car1.Tampa1.Level3.net (4.69.133.49) 180.572 ms 180.581 ms ae-13-13.car3.Tampa1.Level3.net (4.69.133.54) 196.538 ms 15 ae-13-13.car3.Tampa1.Level3.net (4.69.133.54) 196.572 ms e1-11-level3.co2.tpax.as30217.net (4.71.0.10) 205.242 ms 220.799 ms 16 PROGRESS-TE.car3.Tampa1.Level3.net (4.71.0.18) 220.834 ms e1-3.dr2.as30217.net (84.40.24.42) 227.636 ms PROGRESS-TE.car3.Tampa1.Level3.net (4.71.0.18) 235.616 ms 17 e1-3.dr2.as30217.net (84.40.24.42) 174.951 ms 64.26.31.117 183.360 ms 190.007 ms At the same time 205.189.71.34 cannot ftp me although I can ssh him. traceroute to echnaton.serveftp.com (62.227.219.14), 30 hops max, 38 byte packets 1 205.189.71.253 (205.189.71.253) 0.241 ms 0.220 ms 0.227 ms 2 ge-5-2-234.ipcolo1.Amsterdam1.Level3.net (212.72.46.165) 0.735 ms 1.051 ms 0.981 ms 3 ae-0-51.mp1.Amsterdam1.Level3.net (4.68.120.1) 1.233 ms 0.952 ms 1.229 ms 4 as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) 9.234 ms as-0-0.mp2.Hamburg1.Level3.net (4.68.128.30) 9.231 ms as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) 9.117 ms 5 so-10-0.hsa2.Hamburg1.Level3.net (4.68.115.241) 9.182 ms 8.868 ms so-2-0.hsa2.Hamburg1.Level3.net (4.68.115.253) 9.107 ms 6 HH-EB1.HH.DE.net.dtag.de (4.68.127.242) 9.621 ms 9.706 ms 9.476 ms 7 217.5.68.82 (217.5.68.82) 15.605 ms 15.901 ms 15.724 ms 8 217.0.78.57 (217.0.78.57) 18.219 ms 17.031 ms 16.874 ms 9 * * * ... All they have in common is Level3 and we have a blue moon today. It is a couple of people distributed over the globe who complained. Kind regards Peter and Karin Dambier -- Peter and Karin Dambier Cesidian Root - Radice Cesidiana Rimbacher Strasse 16 D-69509 Moerlenbach-Bonsweiher +49(6209)795-816 (Telekom) +49(6252)750-308 (VoIP: sipgate.de) mail: peter(a)peter-dambier.de mail: peter(a)echnaton.arl.pirates http://iason.site.voila.fr/ https://sourceforge.net/projects/iason/ http://www.cesidianroot.com/

2 2

RE: issues Level3 versus rest of the world?
by Security Admin (NetSec) 01 Jul '07

01 Jul '07

<<I cannot http 64.26.31.117>> But I can :) .... 4 9 ms 9 ms 8 ms f1.ba01.b002698-1.lax01.atlas.cogentco.com [38.112.9.189] 5 8 ms 8 ms 9 ms g2-3.core01.lax01.atlas.cogentco.com [66.250.12.129] 6 17 ms 9 ms 8 ms t8-1.mpd01.lax01.atlas.cogentco.com [154.54.1.102] 7 136 ms 206 ms 212 ms t7-1.mpd02.sfo01.atlas.cogentco.com [154.54.6.30] 8 21 ms 19 ms 20 ms v3498.mpd01.sjc03.atlas.cogentco.com [154.54.6.234] 9 21 ms 21 ms 20 ms 64.132.69.17 10 23 ms 21 ms 21 ms core-02-so-1-0-0-0.okld.twtelecom.net [64.129.248.16] 11 81 ms 79 ms 79 ms dist-01-so-0-0-0-0.tamq.twtelecom.net [66.192.243.17] 12 98 ms 232 ms 179 ms 66.192.247.163 13 94 ms 94 ms 93 ms 66.193.50.238 14 94 ms 95 ms 93 ms e1-3.dr2.as30217.net [84.40.24.42] 15 94 ms 93 ms 93 ms 64.26.31.117 Level3 can too, c/o http://lg.level3.net/traceroute/traceroute.cgi?site=sjo1&target=64.26.31.117 Show Level 3 (San Jose, CA) Traceroute to 64.26.31.117 1 vlan52.csw2.SanJose1.Level3.net (4.68.123.62) 12 msec vlan51.csw1.SanJose1.Level3.net (4.68.123.30) 0 msec vlan52.csw2.SanJose1.Level3.net (4.68.123.62) 0 msec 2 ae-63-63.ebr3.SanJose1.Level3.net (4.69.134.225) 4 msec ae-73-73.ebr3.SanJose1.Level3.net (4.69.134.229) 0 msec ae-63-63.ebr3.SanJose1.Level3.net (4.69.134.225) 0 msec 3 ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) 20 msec 16 msec 20 msec 4 ae-78.ebr2.LosAngeles1.Level3.net (4.69.135.13) 16 msec 20 msec 16 msec 5 ae-3.ebr3.Dallas1.Level3.net (4.69.132.78) 40 msec 52 msec 56 msec 6 ae-68.ebr1.Dallas1.Level3.net (4.69.135.1) 40 msec 44 msec 56 msec 7 ae-7-7.car2.Tampa1.Level3.net (4.69.133.41) 64 msec 64 msec 68 msec 8 ae-23-23.car3.Tampa1.Level3.net (4.69.133.62) 64 msec 68 msec 76 msec 9 PROGRESS-TE.car3.Tampa1.Level3.net (4.71.0.18) 64 msec e1-11-level3.co2.tpax.as30217.net (4.71.0.10) 64 msec PROGRESS-TE.car3.Tampa1.Level3.net (4.71.0.18) 64 msec 10 e1-3.dr2.as30217.net (84.40.24.42) [AS30217 {DESYNC}] 64 msec 64 msec 68 msec 11 64.26.31.117 [AS30217 {DESYNC}] 64 msec 64 msec 68 msec ...... Do you multihome? If not, you should. SecAdmin -- This mail was scanned by BitDefender For more informations please visit http://www.bitdefender.com

1 0

Cable-Tying with Waxed Twine
by Dan Mahoney, System Admin 01 Jul '07

01 Jul '07

Hey all, This seems a wee bit off topic, but definitely relates to network operations (somewhere below layer 1) and I can't think of a better place to ask. Upon leaving a router at telx and asking one of their techs to plug in the equipment for me, I came back to find all my cat5 cables neatly tied with some sort of waxed twine, using an interesting looping knot pattern that repeated every six inches or so using a single piece of string. For some reason, I found this trick really cool. I have tried googling for the method, (it's apparently standard, I've seen it in play elsewhere), and for the type of twine, but had little luck. I was wondering if any of the gurus out there would care to share what this knot-pattern is actually called, and/or if there's a (illustrated) howto somewhere? -Dan "Tired of getting scratched up by jagged cable ties" Mahoney -- --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---------------------------

21 20

Re: The Choice: IPv4 Exhaustion or Transition to IPv6
by Brandon Butterworth 30 Jun '07

30 Jun '07

> I'm working on it ... But I think it will be really difficult to capture in > a couple of pages what the document try to explain ! A. v4 runs out, use v6 or similar B. not run out of v4 The detail of A and B may safely be debated by all for some time as nobody knows what will happen, feel free to speculate wildly (with a nod to Deep Thought) brandon

2 1

Thoughts on best practice for naming router infrastructure in DNS
by Olsen, Jason 29 Jun '07

29 Jun '07

I've found myself with a few spare cycles and have decided to put them towards addressing a pet peeve I frequently encounter here: the complete state of chaois that is the naming in DNS for our network infrastructure. There are mismatched forward and reverse entries, no designated subdomain for WAN or LAN gear, there are records that remained after equipment was retired, etc. The single biggest area of offense is in the naming for our routing gear. I attribute this to the fact that routers commonly have a greater number of IP addresses associated with them than, say, your average edge switch. I'm still doing some digging around the 'net as well as the NANOG archives (the document from Rutger's at http://www-td.rutgers.edu/documentation/Reference/RUNet_Network_Device_N aming_Convention/ provided a great example that I'm considering following) but I thought I'd toss it out on the list for a bit of insight into what's being done today as opposed to five years ago. There seems to be two general practices that are used when naming routers in DNS. The first is to describe the location, equipment, interface and interface number on the equipment in the hostname, matching that to a designated subdomain that describes the function (WAN routing, LAN switching, etc). Something like "corp-wan1-gige0-0.wan.example.com" would be used to describe interface Gi0/0 on WAN router #1 at the corporate office and "dpg-mu1.wan.example.com" would describe the Multilink1 interface on the DuPage location's only WAN router. The upside to this methodology is that techs and users alike can see useful information when doing a traceroute, etc. The downside is that if your router has a dozen interfaces you end up with two dozen records (12 forward, 12 reverse) associated with the device that must be maintained. Additionally, the moment you upgrade an interface you have to change the two corresponding records to reflect the new IP or interface type (FastE to GigE, for example). The other style I've seen is to use one generic name, such as "corp-wan1.wan.example.com" for the first WAN router and "corp-core1.lan.example.com" for the first core router, make the FQDN resolve to a loopback or similarly unchanging IP and for every interface that carries an IP address just have the address reverse to that single generic FQDN. This is generally simpler to maintain and is given praise because it's less likely to confuse NMS applications like OpenView Network Node Manager -- on the downside you lose a lot of potentially useful information. Neither one of these seems well-equipped to deal with "virtual" interfaces such as an ethernet interface that is VRRP or HSRP'd between two routers (eg x.x.x.10 is your "virtual" IP for the subnet's gateway, router 1 has physical interface IP of x.x.x.8 and router 2 has x.x.x.9). So, what practices do you folks follow? What are the up and downsides you encounter? -JFO Jason "Feren" Olsen DeVry University

9 9

Weekly Routing Table Report
by Routing Analysis Role Account 29 Jun '07

29 Jun '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 30 Jun, 2007 Report Website: http://thyme.apnic.net This report: http://thyme.apnic.net/ap-data/2007/06/30/0400 Analysis Summary ---------------- BGP routing table entries examined: 224622 Prefixes after maximum aggregation: 118451 Deaggregation factor: 1.90 Unique aggregates announced to Internet: 109225 Total ASes present in the Internet Routing Table: 25577 Prefixes per ASN: 8.78 Origin-only ASes present in the Internet Routing Table: 22272 Origin ASes announcing only one prefix: 10821 Transit ASes present in the Internet Routing Table: 3305 Transit-only ASes present in the Internet Routing Table: 74 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 22 Max AS path prepend of ASN (35389) 16 Prefixes from unregistered ASNs in the Routing Table: 16 Unregistered ASNs in the Routing Table: 20 Prefixes from 32-bit ASNs in the Routing Table: 4 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 11 Number of addresses announced to Internet: 1731452128 Equivalent to 103 /8s, 51 /16s and 220 /24s Percentage of available address space announced: 46.7 Percentage of allocated address space announced: 61.9 Percentage of available address space allocated: 75.5 Total number of prefixes smaller than registry allocations: 117910 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 52657 Total APNIC prefixes after maximum aggregation: 20514 APNIC Deaggregation factor: 2.57 Prefixes being announced from the APNIC address blocks: 49562 Unique aggregates announced from the APNIC address blocks: 21739 APNIC Region origin ASes present in the Internet Routing Table: 2996 APNIC Prefixes per ASN: 16.54 APNIC Region origin ASes announcing only one prefix: 810 APNIC Region transit ASes present in the Internet Routing Table: 456 Average APNIC Region AS path length visible: 3.6 Max APNIC Region AS path length visible: 15 Number of APNIC addresses announced to Internet: 301656224 Equivalent to 17 /8s, 250 /16s and 232 /24s Percentage of available APNIC address space announced: 74.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: 107145 Total ARIN prefixes after maximum aggregation: 62315 ARIN Deaggregation factor: 1.72 Prefixes being announced from the ARIN address blocks: 78811 Unique aggregates announced from the ARIN address blocks: 31164 ARIN Region origin ASes present in the Internet Routing Table: 11665 ARIN Prefixes per ASN: 6.76 ARIN Region origin ASes announcing only one prefix: 4489 ARIN Region transit ASes present in the Internet Routing Table: 1062 Average ARIN Region AS path length visible: 3.4 Max ARIN Region AS path length visible: 17 Number of ARIN addresses announced to Internet: 338181440 Equivalent to 20 /8s, 40 /16s and 61 /24s Percentage of available ARIN address space announced: 74.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: 46947 Total RIPE prefixes after maximum aggregation: 30348 RIPE Deaggregation factor: 1.55 Prefixes being announced from the RIPE address blocks: 43349 Unique aggregates announced from the RIPE address blocks: 28811 RIPE Region origin ASes present in the Internet Routing Table: 9830 RIPE Prefixes per ASN: 4.41 RIPE Region origin ASes announcing only one prefix: 5203 RIPE Region transit ASes present in the Internet Routing Table: 1570 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 22 Number of RIPE addresses announced to Internet: 320961472 Equivalent to 19 /8s, 33 /16s and 123 /24s Percentage of available RIPE address space announced: 79.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/5, 88/6, 92/7, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 15306 Total LACNIC prefixes after maximum aggregation: 4251 LACNIC Deaggregation factor: 3.60 Prefixes being announced from the LACNIC address blocks: 13356 Unique aggregates announced from the LACNIC address blocks: 7547 LACNIC Region origin ASes present in the Internet Routing Table: 817 LACNIC Prefixes per ASN: 16.35 LACNIC Region origin ASes announcing only one prefix: 261 LACNIC Region transit ASes present in the Internet Routing Table: 146 Average LACNIC Region AS path length visible: 4.2 Max LACNIC Region AS path length visible: 19 Number of LACNIC addresses announced to Internet: 40049920 Equivalent to 2 /8s, 99 /16s and 29 /24s Percentage of available LACNIC address space announced: 59.7 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: 2561 Total AfriNIC prefixes after maximum aggregation: 1015 AfriNIC Deaggregation factor: 2.52 Prefixes being announced from the AfriNIC address blocks: 2043 Unique aggregates announced from the AfriNIC address blocks: 1244 AfriNIC Region origin ASes present in the Internet Routing Table: 194 AfriNIC Prefixes per ASN: 10.53 AfriNIC Region origin ASes announcing only one prefix: 58 AfriNIC Region transit ASes present in the Internet Routing Table: 36 Average AfriNIC Region AS path length visible: 3.7 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 6196736 Equivalent to 0 /8s, 94 /16s and 142 /24s Percentage of available AfriNIC address space announced: 18.5 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 4134 1347 10189 282 CHINANET-BACKBONE 4755 1243 382 72 Videsh Sanchar Nigam Ltd. Aut 9583 1107 79 394 Sify Limited 9498 980 469 66 BHARTI BT INTERNET LTD. 4766 789 4927 312 Korea Telecom (KIX) 23577 775 35 703 Korea Telecom (ATM-MPLS) 17488 706 46 49 Hathway IP Over Cable Interne 7545 689 151 110 TPG Internet Pty Ltd 18101 565 117 36 Reliance Infocom Ltd Internet 1221 550 1954 425 Telstra Pty Ltd 4812 517 904 92 China Telecom (Shanghai) 4668 508 68 10 LG-EDS Systems Inc. 17676 504 10935 65 Softbank BB Corp. 9443 467 121 77 Primus Telecommunications 4802 411 105 151 Wantree Development 7474 410 218 270 SingTel Optus Pty Ltd 17974 371 130 13 PT TELEKOMUNIKASI INDONESIA 9829 362 258 14 BSNL National Internet Backbo 2907 361 1700 301 SINET Japan 17557 352 41 170 Pakistan Telecom ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1474 6087 986 AT&T WorldNet Services 4323 1318 1042 368 Time Warner Telecom 2386 1211 615 752 AT&T Data Communications Serv 6478 1124 368 153 AT&T Worldnet Services 11492 1094 107 23 Cable One 6197 1024 717 510 BellSouth Network Solutions, 18566 1011 288 9 Covad Communications 174 954 6778 865 Cogent Communications 701 951 6597 723 UUNET Technologies, Inc. 7011 849 252 538 Citizens Utilities 1239 810 2734 580 Sprint 20115 798 728 424 Charter Communications 19262 779 2724 202 Verizon Global Networks 209 751 3854 579 Qwest 22773 728 1892 44 Cox Communications, Inc. 5668 614 169 21 CenturyTel Internet Holdings, 7029 602 488 80 Alltel Information Services, 852 579 1089 363 Telus Advanced Communications 855 575 254 73 Canadian Research Network 19916 568 49 51 OLM LLC RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 2119 514 1075 136 Telenor Internet Access 702 512 1936 403 UUNET - Commercial IP service 24863 355 56 37 LINKdotNET AS number 3301 310 1455 290 TeliaNet Sweden 3320 305 6034 256 Deutsche Telekom AG 6746 280 129 256 Dynamic Network Technologies, 680 264 2044 255 DFN-IP service G-WiN 3215 254 2376 96 France Telecom Transpac 8220 249 444 241 COLT Telecommunications 8708 248 419 238 Romania Data Systems S.A. 8551 223 213 28 Bezeq International 3269 222 2775 74 TELECOM ITALIA 5089 221 1658 53 NTL Group Limited 3352 219 1864 41 Ibernet, Internet Access Netw 9121 210 1441 24 TTnet Autonomous System 9116 200 136 25 Goldenlines main autonomous s 1257 196 1196 174 SWIPnet Swedish IP Network 3246 195 329 185 Song Networks 12479 191 578 6 Uni2 Autonomous System 3300 186 172 92 AUCS Communications Services LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 854 1917 211 UniNet S.A. de C.V. 11830 483 299 9 Instituto Costarricense de El 11172 371 116 63 Servicios Alestra S.A de C.V 16814 361 22 8 NSS, S.A. 22047 313 238 12 VTR PUNTO NET S.A. 7303 300 145 32 Telecom Argentina Stet-France 14117 279 19 15 Telefonica del Sur S.A. 6471 275 74 33 ENTEL CHILE S.A. 11556 231 128 4 Cable-Wireless Panama 6147 225 172 27 Telefonica Del Peru 6503 211 188 84 AVANTEL, S.A. 10620 207 59 14 TVCABLE BOGOTA 23216 195 16 43 RAMtelecom Telecomunicaciones 10481 181 72 8 Prima S.A. 14522 173 27 8 SatNet S.A. 21826 156 27 59 INTERCABLE 7910 155 11 30 ANDINET ON LINE 19169 153 10 31 Telconet 20299 152 23 12 NEWCOM AMERICAS 7738 146 474 22 Telecomunicacoes da Bahia S.A AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 280 867 221 The Internet Solution 8452 226 188 7 TEDATA 6713 142 135 11 Itissalat Al-MAGHRIB 2018 136 301 111 Tertiary Education Network 33783 126 8 11 EEPAD TISP TELECOM & INTERNET 5536 123 8 15 Internet Egypt Network 24835 85 48 6 RAYA Telecom - Egypt 2905 77 174 73 The Internetworking Company o 15475 75 84 4 Nile Online 2561 62 6 2 Egyptian Universities Network 15706 56 12 4 Sudatel Internet Exchange Aut 23889 49 16 14 MAURITIUS TELECOM 5713 45 294 35 Telkom SA Ltd 33774 43 29 24 AS Number for Telecom Algeria 16637 37 21 29 Johnnic e-Ventures 33776 36 2 2 Starcomms Nigeria Limited 8524 32 2 8 AUCEGYPT Autonomous System 12455 32 6 3 Jambonet Autonomous system 21280 28 4 4 Swift Global Kenya Ltd.Is an 10798 24 2 15 Standard Bank of South Africa Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4755 1243 1171 Videsh Sanchar Nigam Ltd. Aut 11492 1094 1071 Cable One 4134 1347 1065 CHINANET-BACKBONE 18566 1011 1002 Covad Communications 6478 1124 971 AT&T Worldnet Services 4323 1318 950 Time Warner Telecom 9498 980 914 BHARTI BT INTERNET LTD. 9583 1107 713 Sify Limited 22773 728 684 Cox Communications, Inc. 17488 706 657 Hathway IP Over Cable Interne 8151 854 643 UniNet S.A. de C.V. 5668 614 593 CenturyTel Internet Holdings, 7545 689 579 TPG Internet Pty Ltd 19262 779 577 Verizon Global Networks 18101 565 529 Reliance Infocom Ltd Internet 6517 560 525 Yipes Communications, Inc. 7029 602 522 Alltel Information Services, 19916 568 517 OLM LLC 15270 551 516 PaeTec.net -a division of Pae 6197 1024 514 BellSouth Network Solutions, List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65332 PRIVATE 63.166.106.192/27 1803 SPRINT 43190 UNALLOCATED 77.95.248.0/21 39637 PE Netlogics BV 43065 UNALLOCATED 77.247.112.0/22 8342 Rostelecom Internet 42923 UNALLOCATED 88.199.162.0/24 12968 Crowley Data Poland, 39701 UNALLOCATED 88.204.14.0/24 29047 Stack Ltd. Autonomou 43211 UNALLOCATED 89.45.72.0/21 35002 HERTZA Computers 42935 UNALLOCATED 91.123.208.0/24 5617 TPNET 42842 UNALLOCATED 91.193.176.0/22 12389 JSC Rostelecom 43196 UNALLOCATED 91.194.154.0/23 174 Cogent Communication 42301 UNALLOCATED 193.33.38.0/23 6820 LEIVO Autonomous Sys 42856 UNALLOCATED 193.200.137.0/24 8495 Internet GmbH Autono 43078 UNALLOCATED 193.200.190.0/24 21219 Datacom Autonomous S 43138 UNALLOCATED 193.200.245.0/24 702 UUNET - Commercial I 42452 UNALLOCATED 194.0.129.0/24 8751 Media Sat S.A. 24410 UNALLOCATED 203.119.28.0/24 4134 CHINANET-BACKBONE 22895 UNALLOCATED 216.174.38.0/24 19094 Adelphia Business So 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:36 /12:126 /13:252 /14:464 /15:903 /16:9511 /17:4023 /18:6508 /19:13698 /20:15858 /21:14295 /22:18656 /23:19621 /24:118249 /25:792 /26:995 /27:480 /28:76 /29:10 /30:14 /31:0 /32:13 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6478 1114 1124 AT&T Worldnet Services 11492 1085 1094 Cable One 18566 993 1011 Covad Communications 9583 949 1107 Sify Limited 2386 904 1211 AT&T Data Communications Serv 7018 800 1474 AT&T WorldNet Services 6197 777 1024 BellSouth Network Solutions, 23577 761 775 Korea Telecom (ATM-MPLS) 7011 748 849 Citizens Utilities 9498 651 980 BHARTI BT INTERNET LTD. 4755 641 1243 Videsh Sanchar Nigam Ltd. Aut 4766 596 789 Korea Telecom (KIX) 19916 563 568 OLM LLC 4323 551 1318 Time Warner Telecom 17488 529 706 Hathway IP Over Cable Interne 6517 526 560 Yipes Communications, Inc. 15270 518 551 PaeTec.net -a division of Pae 4668 498 508 LG-EDS Systems Inc. 18101 480 565 Reliance Infocom Ltd Internet 5668 479 614 CenturyTel Internet Holdings, Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:8 7:1 8:84 9:1 12:1806 15:18 16:3 17:3 18:11 20:38 24:939 25:1 32:50 33:3 38:330 40:61 41:181 44:2 47:4 52:4 55:3 56:3 57:25 58:424 59:392 60:313 61:992 62:879 63:1972 64:3129 65:2356 66:3295 67:747 68:633 69:1891 70:432 71:107 72:1333 73:2 74:545 75:265 76:73 77:258 78:2 80:813 81:816 82:705 83:374 84:417 85:844 86:343 87:488 88:287 89:878 90:7 91:386 97:6 98:3 116:213 117:57 121:214 122:555 123:120 124:835 125:944 128:290 129:224 130:127 131:366 132:53 133:9 134:195 135:39 136:182 137:82 138:148 139:73 140:480 141:173 142:374 143:248 144:298 145:43 146:321 147:120 148:400 149:144 150:113 151:160 152:93 153:126 154:4 155:254 156:152 157:212 158:157 159:158 160:106 161:92 162:221 163:183 164:440 165:408 166:294 167:287 168:501 169:120 170:406 171:18 172:1 189:62 190:678 192:5767 193:3895 194:3171 195:2244 196:937 198:3825 199:3282 200:4902 201:1074 202:7406 203:7576 204:3961 205:2016 206:2414 207:2834 208:2702 209:3497 210:2465 211:958 212:1307 213:1471 214:403 215:40 216:3997 217:1149 218:360 219:382 220:979 221:412 222:264 End of report

1 0

Re: Thoughts on best practice for naming router infrastructure in DNS
by Brandon Butterworth 29 Jun '07

29 Jun '07

> If you have more routers than muppets, you have a problem. More muppets than routers is also a problem brandon

1 0

6to4 and Teredo relays deployment
by JORDI PALET MARTINEZ 29 Jun '07

29 Jun '07

Some weeks ago I started to work in documenting how to setup 6to4 and Teredo relays/servers in several platforms for the afripv6-discuss mailing list. There are many 6to4 relays already, but it becomes even more important to have them where the bandwidth is more expensive, because it avoids traffic going thru upstream links. The first message on this is here: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000061.html More information about 6to4 also available at: http://www.ipv6tf.org/index.php?page=using/connectivity/6to4 Similarly for Teredo: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000080.html And more info about Teredo at: http://www.ipv6tf.org/index.php?page=using/connectivity/teredo Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

trans-Atlantic latency?
by Neal R 29 Jun '07

29 Jun '07

I have a customer with IP transport from Sprint and McLeod and fiber connectivity to Sprint in the Chicago area. The person making the decisions is not a routing guy but is very sharp overall. He is currently examining the latency on trans-Atlantic links and has fixed on the idea that he needs 40ms or less to London through whatever carrier he picks. He has spoken to someone at Cogent about a point to point link. What is a reasonable latency to see on a link of that distance? I get the impression he is shopping for something that involves dilithium crystal powered negative latency inducers, wormhole technology, or an ethernet to tachyon bridge, but its been a long time (9/14/2001, to be exact) since I've had a trans-Atlantic circuit under my care and things were different back then. Anyone care to enlighten me on what these guys can reasonably expect on such a link? My best guess is he'd like service from Colt based on the type of customer he is trying to reach, but its a big muddle and I don't get to talk to all of the players ...

10 9