- Test - lists.nanog.org

[NANOG-announce] NANOG Reminders
by Betty Burke <betty＠nanog.org> 15 Aug '14

15 Aug '14

NANOGers: As we wrap up summer vacation and look toward to fall, let me share a few NANOG reminders with you. ARIN+NOTR - Madison <https://www.nanog.org/meetings/road4/home>- September 9, 2014. The agenda <https://www.nanog.org/meetings/road4/agenda> has been published. This is a one day free mini NANOG which does require registration. NANOG Fellowship Opportunities <https://www.nanog.org/resources/fellowships>. This is a great opportunity for those new to NANOG, who are interested in attending NANOG 62 and could benefit from travel assistance. Education Classes - Baltimore <https://www.nanog.org/meetings/education/home> are a great opportunity for new and mid career engineers to gain network operational experience, taught by real world operators. Make sure to pass along the information. NANOG 62 <https://www.nanog.org/meetings/nanog62/home> Update Agenda <https://www.nanog.org/meetings/nanog62/preagenda> - The PC is hard at work reviewing all of the submissions. A Topics list will be published shortly. Travel <https://www.nanog.org/meetings/nanog62/inandaround> and Socials <https://www.nanog.org/meetings/nanog62/socials> - Be sure to make your travel plans and hotel reservations <https://www.nanog.org/meetings/nanog62/hotelinformation>such that you will be in Baltimore for the ever popular NANOG Socials. We have evening activities Sunday, Monday, Tuesday, and Wednesday, October 5-8, 2014. ARIN 34 <http://www.cvent.com/events/arin-34-public-policy-and-members-meeting/event…> will follow NANOG on Thursday and Friday, October 9-10, 2014. Sponsorship Opportunities <https://www.nanog.org/sponsors/opportunities> - NANOG 62 <https://www.nanog.org/meetings/nanog62/sponsors> sponsorship opportunities remain, be sure your company is supporting NANOG and its efforts to make the Internet better. Lastly, the NANOG Election <https://www.nanog.org/governance/elections/2014> process is underway. Be sure to become a NANOG Member <https://www.nanog.org/membership/join> and participate in the process. Nominations <https://www.bigpulse.com/97752/signin> are open. I hope you find these reminders helpful. However, should you have any questions, please do not hesitate to contact us via nanog-support(a)nanog.org. Sincerely, Betty Betty Burke NANOG Executive Director 48377 Fremont Boulevard, Suite 117 Fremont, CA 94538 Tel: +1 510 492 4030 _______________________________________________ NANOG-announce mailing list NANOG-announce(a)mailman.nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 15 Aug '14

15 Aug '14

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, LacNOG, TRNOG, CaribNOG and the RIPE Routing Working Group. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 16 Aug, 2014 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 507509 Prefixes after maximum aggregation: 196575 Deaggregation factor: 2.58 Unique aggregates announced to Internet: 249334 Total ASes present in the Internet Routing Table: 47477 Prefixes per ASN: 10.69 Origin-only ASes present in the Internet Routing Table: 36058 Origin ASes announcing only one prefix: 16386 Transit ASes present in the Internet Routing Table: 6134 Transit-only ASes present in the Internet Routing Table: 175 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 53 Max AS path prepend of ASN ( 50404) 51 Prefixes from unregistered ASNs in the Routing Table: 1779 Unregistered ASNs in the Routing Table: 470 Number of 32-bit ASNs allocated by the RIRs: 7204 Number of 32-bit ASNs visible in the Routing Table: 5285 Prefixes from 32-bit ASNs in the Routing Table: 19068 Number of bogon 32-bit ASNs visible in the Routing Table: 535 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 417 Number of addresses announced to Internet: 2711918852 Equivalent to 161 /8s, 164 /16s and 153 /24s Percentage of available address space announced: 73.3 Percentage of allocated address space announced: 73.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 96.8 Total number of prefixes smaller than registry allocations: 174269 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 123030 Total APNIC prefixes after maximum aggregation: 35904 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 126507 Unique aggregates announced from the APNIC address blocks: 52010 APNIC Region origin ASes present in the Internet Routing Table: 4971 APNIC Prefixes per ASN: 25.45 APNIC Region origin ASes announcing only one prefix: 1229 APNIC Region transit ASes present in the Internet Routing Table: 873 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 24 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1050 Number of APNIC addresses announced to Internet: 734277248 Equivalent to 43 /8s, 196 /16s and 46 /24s Percentage of available APNIC address space announced: 85.8 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-63999, 131072-133631 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 170844 Total ARIN prefixes after maximum aggregation: 84598 ARIN Deaggregation factor: 2.02 Prefixes being announced from the ARIN address blocks: 172712 Unique aggregates announced from the ARIN address blocks: 80555 ARIN Region origin ASes present in the Internet Routing Table: 16362 ARIN Prefixes per ASN: 10.56 ARIN Region origin ASes announcing only one prefix: 6125 ARIN Region transit ASes present in the Internet Routing Table: 1698 Average ARIN Region AS path length visible: 4.0 Max ARIN Region AS path length visible: 22 Number of ARIN region 32-bit ASNs visible in the Routing Table: 171 Number of ARIN addresses announced to Internet: 1091945216 Equivalent to 65 /8s, 21 /16s and 195 /24s Percentage of available ARIN address space announced: 57.8 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, 46080-47103 53248-55295, 62464-63487, 393216-394239 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 124601 Total RIPE prefixes after maximum aggregation: 62933 RIPE Deaggregation factor: 1.98 Prefixes being announced from the RIPE address blocks: 129392 Unique aggregates announced from the RIPE address blocks: 81997 RIPE Region origin ASes present in the Internet Routing Table: 17702 RIPE Prefixes per ASN: 7.31 RIPE Region origin ASes announcing only one prefix: 8235 RIPE Region transit ASes present in the Internet Routing Table: 2874 Average RIPE Region AS path length visible: 5.0 Max RIPE Region AS path length visible: 53 Number of RIPE region 32-bit ASNs visible in the Routing Table: 2729 Number of RIPE addresses announced to Internet: 658888580 Equivalent to 39 /8s, 69 /16s and 215 /24s Percentage of available RIPE address space announced: 95.8 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-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 196608-202239 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 58825 Total LACNIC prefixes after maximum aggregation: 10369 LACNIC Deaggregation factor: 5.67 Prefixes being announced from the LACNIC address blocks: 66665 Unique aggregates announced from the LACNIC address blocks: 29888 LACNIC Region origin ASes present in the Internet Routing Table: 2223 LACNIC Prefixes per ASN: 29.99 LACNIC Region origin ASes announcing only one prefix: 581 LACNIC Region transit ASes present in the Internet Routing Table: 450 Average LACNIC Region AS path length visible: 4.6 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 1286 Number of LACNIC addresses announced to Internet: 167946496 Equivalent to 10 /8s, 2 /16s and 169 /24s Percentage of available LACNIC address space announced: 100.1 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 262144-263679 plus ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 11052 Total AfriNIC prefixes after maximum aggregation: 2733 AfriNIC Deaggregation factor: 4.04 Prefixes being announced from the AfriNIC address blocks: 11816 Unique aggregates announced from the AfriNIC address blocks: 4540 AfriNIC Region origin ASes present in the Internet Routing Table: 733 AfriNIC Prefixes per ASN: 16.12 AfriNIC Region origin ASes announcing only one prefix: 216 AfriNIC Region transit ASes present in the Internet Routing Table: 162 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 28 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 49 Number of AfriNIC addresses announced to Internet: 58431744 Equivalent to 3 /8s, 123 /16s and 153 /24s Percentage of available AfriNIC address space announced: 58.0 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 2952 11590 920 Korea Telecom 17974 2812 901 75 PT Telekomunikasi Indonesia 7545 2322 336 120 TPG Telecom Limited 4755 1872 393 200 TATA Communications formerly 9829 1654 1307 32 National Internet Backbone 9583 1315 104 537 Sify Limited 9498 1300 317 93 BHARTI Airtel Ltd. 7552 1238 1098 14 Viettel Corporation 4808 1215 2159 371 CNCGROUP IP network China169 24560 1162 403 189 Bharti Airtel Ltd., Telemedia Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7029 3165 1958 305 Windstream Communications Inc 6389 2938 3688 51 BellSouth.net Inc. 22773 2937 2940 142 Cox Communications Inc. 18566 2047 379 178 MegaPath Corporation 20115 1758 1744 530 Charter Communications 4323 1631 1072 411 tw telecom holdings, inc. 30036 1527 319 580 Mediacom Communications Corp 701 1439 11227 724 MCI Communications Services, 6983 1434 817 313 ITC^Deltacom 22561 1307 407 235 CenturyTel Internet Holdings, Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 34984 1736 298 282 TELLCOM ILETISIM HIZMETLERI A 20940 1460 567 1075 Akamai International B.V. 8402 1289 544 15 OJSC "Vimpelcom" 13188 1049 97 53 TOV "Bank-Inform" 31148 1043 45 21 Freenet Ltd. 8551 988 371 41 Bezeq International-Ltd 6849 790 356 27 JSC "Ukrtelecom" 12479 775 798 58 France Telecom Espana SA 6830 772 2334 427 Liberty Global Operations B.V 9198 605 346 28 JSC Kazakhtelecom Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 28573 3727 2046 108 NET Serviços de Comunicação S 10620 2943 476 228 Telmex Colombia S.A. 18881 2068 1036 22 Global Village Telecom 7303 1770 1179 231 Telecom Argentina S.A. 8151 1448 2988 426 Uninet S.A. de C.V. 6503 1091 434 60 Axtel, S.A.B. de C.V. 6147 1049 374 29 Telefonica del Peru S.A.A. 7738 977 1882 41 Telemar Norte Leste S.A. 27947 898 130 51 Telconet S.A 26615 869 2325 35 Tim Celular S.A. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 932 280 26 Link Egypt (Link.NET) 6713 669 744 37 Office National des Postes et 8452 593 958 13 TE-AS 24835 307 144 9 Vodafone Data 36992 300 784 26 ETISALAT MISR 3741 249 920 212 Internet Solutions 29571 237 22 17 Cote d'Ivoire Telecom 37054 236 19 6 Data Telecom Service 15706 187 32 6 Sudatel (Sudan Telecom Co. Lt 12258 175 26 72 MWEB CONNECT (PROPRIETARY) LI Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 28573 3727 2046 108 NET Serviços de Comunicação S 7029 3165 1958 305 Windstream Communications Inc 4766 2952 11590 920 Korea Telecom 10620 2943 476 228 Telmex Colombia S.A. 6389 2938 3688 51 BellSouth.net Inc. 22773 2937 2940 142 Cox Communications Inc. 17974 2812 901 75 PT Telekomunikasi Indonesia 7545 2322 336 120 TPG Telecom Limited 18881 2068 1036 22 Global Village Telecom 18566 2047 379 178 MegaPath Corporation Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 6389 2938 2887 BellSouth.net Inc. 7029 3165 2860 Windstream Communications Inc 22773 2937 2795 Cox Communications Inc. 17974 2812 2737 PT Telekomunikasi Indonesia 10620 2943 2715 Telmex Colombia S.A. 7545 2322 2202 TPG Telecom Limited 18881 2068 2046 Global Village Telecom 4766 2952 2032 Korea Telecom 18566 2047 1869 MegaPath Corporation 4755 1872 1672 TATA Communications formerly Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 2828 XO Communications 20260 UNALLOCATED 8.25.160.0/24 3356 Level 3 Communicatio 20260 UNALLOCATED 8.25.161.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.122.0/24 12180 Internap Network Ser 46473 UNALLOCATED 8.27.124.0/24 12180 Internap Network Ser 55020 UNALLOCATED 8.30.123.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I 33628 UNALLOCATED 12.0.239.0/24 1239 Sprint Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.231.96.0/24 21548 MTO Telecom Inc. 27.100.7.0/24 56096 >>UNKNOWN<< 41.70.8.0/21 37098 globe internet limited 41.70.16.0/20 37098 globe internet limited 41.70.40.0/21 37098 globe internet limited 41.70.64.0/21 37098 globe internet limited 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.10.0/24 37004 >>UNKNOWN<< 41.73.11.0/24 37004 >>UNKNOWN<< Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:30 /11:91 /12:259 /13:498 /14:983 /15:1707 /16:13044 /17:7016 /18:11716 /19:24689 /20:35142 /21:37581 /22:54586 /23:47878 /24:270181 /25:803 /26:818 /27:404 /28:12 /29:17 /30:10 /31:1 /32:14 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 22773 2173 2937 Cox Communications Inc. 18566 2002 2047 MegaPath Corporation 7029 1704 3165 Windstream Communications Inc 6389 1691 2938 BellSouth.net Inc. 30036 1376 1527 Mediacom Communications Corp 11492 1192 1240 CABLE ONE, INC. 6983 1141 1434 ITC^Deltacom 34984 1057 1736 TELLCOM ILETISIM HIZMETLERI A 10620 1033 2943 Telmex Colombia S.A. 8402 1008 1289 OJSC "Vimpelcom" Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1320 2:661 3:3 4:15 5:1066 6:21 8:724 12:1859 13:4 14:1108 15:15 16:2 17:40 18:21 19:1 20:53 23:894 24:1811 27:1792 31:1470 32:41 33:2 34:5 36:141 37:1840 38:965 39:10 40:210 41:2583 42:266 43:184 44:16 45:52 46:2165 47:24 49:733 50:817 52:12 54:48 55:4 56:4 57:32 58:1247 59:631 60:425 61:1599 62:1239 63:1856 64:4416 65:2303 66:4217 67:2058 68:1040 69:3338 70:901 71:464 72:2103 74:2623 75:337 76:412 77:1620 78:801 79:722 80:1314 81:1212 82:759 83:770 84:766 85:1321 86:422 87:1142 88:463 89:1780 90:136 91:5699 92:754 93:1767 94:2018 95:1603 96:510 97:362 98:1126 99:49 100:65 101:709 103:5398 104:194 105:37 106:178 107:593 108:582 109:2011 110:1027 111:1348 112:687 113:860 114:783 115:1110 116:1118 117:933 118:1529 119:1424 120:418 121:862 122:2168 123:1604 124:1435 125:1561 128:573 129:346 130:363 131:716 132:412 133:162 134:317 135:74 136:300 137:286 138:390 139:172 140:228 141:391 142:562 143:428 144:505 145:116 146:621 147:506 148:954 149:397 150:432 151:598 152:452 153:219 154:326 155:516 156:354 157:329 158:275 159:938 160:329 161:576 162:1695 163:337 164:694 165:640 166:346 167:670 168:1113 169:124 170:1385 171:181 172:64 173:1519 174:711 175:609 176:1475 177:3417 178:2051 179:781 180:1789 181:1360 182:1621 183:540 184:692 185:1943 186:2929 187:1643 188:2192 189:1464 190:7668 191:691 192:7483 193:5504 194:4062 195:3561 196:1433 197:681 198:5130 199:5559 200:6360 201:2783 202:9181 203:9015 204:4549 205:2665 206:2975 207:2951 208:3963 209:3801 210:3286 211:1836 212:2341 213:2125 214:871 215:87 216:5709 217:1682 218:616 219:385 220:1370 221:641 222:480 223:596 End of report

1 0

Muni Fiber and Politics
by Jay Ashworth 15 Aug '14

15 Aug '14

Over the last decade, 19 states have made it illegal for municipalities to own fiber networks -- encouraged largely, I am told, by Verizon and other cable companies/MSOs[1]. Verizon, of course, isn't doing any new FiOS deployments, per a 2010 press release[2]. FCC Chair Tom Wheeler has been making noises lately that he wants the FCC to preempt the field on this topic, making such deployments legal. Congressional Republicans think that's a bad idea: http://www.vox.com/2014/7/20/5913363/house-republicans-and-obamas-fcc-are-a… [ and here's the backgrounder on the amendment: http://www.broadcastingcable.com/news/washington/blackburn-bill-would-block… ] While I generally try to avoid bringing up topics on NANOG that are political; this one seems to be directly in our wheelhouse, and unavoidably political. My apologies in advance; let's all try to be grownups, shall we? Cheers, -- jra [1] http://motherboard.vice.com/read/hundreds-of-cities-are-wired-with-fiberbut… [2] https://secure.dslreports.com/shownews/Verizon-Again-Confirms-FiOS-Expansio… -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

49 199

Re: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard look today
by vristevs＠ramapo.edu 14 Aug '14

14 Aug '14

Sent from my Verizon Wireless 4GLTE sm ----- Reply message ----- From: "William Herrin" <bill(a)herrin.us> To: "Randy Bush" <randy(a)psg.com> Cc: "North American Network Operators' Group" <nanog(a)nanog.org> Subject: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard look today Date: Thu, Aug 14, 2014 6:04 pm On Thu, Aug 14, 2014 at 4:57 PM, Randy Bush <randy(a)psg.com> wrote: >> My point was that Randy's BGP RIB pruning knobs are missing for a >> different reason than your router FIB pruning knobs. Neither the >> science nor the technology exists to create Randy's BGP pruning knobs. > > ahhh, you dug out the [j]tac tickets, or are you just conjecturbating? Neither. I'm reporting the state of the science having been engrossed in its research for the better part of a decade. Places like the IRTF RRG. Because no science, also no tech. If you think have some magic new algorithm that the RRG didn't consider, feel free to explain it and I'll demonstrate a scenario for you where it fails too. And I tip my hat to the router vendors for declining to implement knobs which would damage the network, despite the demands of Randy Bush. Regards, Bill Herrin -- William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/> Can I solve your unusual networking challenges?

1 0

Shaw routing issue 12 Aug 2014
by Leah Ungstad 14 Aug '14

14 Aug '14

Hi Nanog, anyone know what's up with a nationwide (Canadian) routing issue on Shaw? http://www.theregister.co.uk/2014/08/12/nationwide_outage_at_canadian_isp_s… https://community.shaw.ca/docs/DOC-3455 thanks Leah

4 5

ASR9K xml agent vs netconf
by Jeremy 14 Aug '14

14 Aug '14

Hi There! I'm currently working on writing some automation around the ASR9K platform and I've been looking at both the netconf and xml interfaces. Anyone have experience with either? It looks like the XML interface is much more feature rich, supporting both config and operational state objects where netconf is limited to config only. Currently I'm leaning towards the xml interface, but netconf would come with the appeal of using a standard and any libraries I write for it may be usable with other platforms. Thoughts? experiences? mistakes? wins? Thanks! Jeremy

6 5

[HFC] pooling modems in layer2
by Toney Mareo 14 Aug '14

14 Aug '14

Hello I think it's kind of an isp secret but I would be curious how do people distribute modems to pools before they would even reach the actual IP network so on layer2: http://dl.packetstormsecurity.net/papers/evaluation/docsis/Service_Distribu… For this I would like to get some clarification because I do not work in the telco industry. As I can figure out of the docsis, cablelabs documents. The CMTS device is connected to the coax segments through fiber. Therefore one could say that the "modem facing" side is a fiber optic interface but it's not 1000 Base-FX, not a regular Ethernet over fiber. It sends signals through a broad range of frequencies. So what I would like to accomplish to provide a different pool of dhcp servers, which provides different config file, tod server, router, dns etc. infos to the modems but to do all this in Layer2. I don't have hands on experience with CMTS-es but I would think that they are able to pool clients by MACs and able to send eg 500 clients to DHCP server1 and the other 1500 to DHCP server2 before they would even get an IP, so I talking of pure layer2 here! Let's say if the CMTS device does not support this, what are the other options for routing layer2 traffic coming out of the CMTS? If I would know more about the device I would say that put a linuxbox after it (on the ISP facing nic) and mark the packets going out with arptables/ebtables then send them out of different nics to different dhcp servers. Any suggestions are welcome.

4 6

fire ants
by Eduardo A. Suárez 14 Aug '14

14 Aug '14

Hi, it's not a joke. Here we have a fire ants nest in the fiber patch panel. Are there any DIY ways to manage that? Thanks, Eduardo.- -- Eduardo A. Suarez Facultad de Ciencias Astronómicas y Geofísicas - UNLP FCAG: (0221)-4236593 int. 172/Cel: (0221)-15-4557542/Casa: (0221)-4526589 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

13 12

Re: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard look today
by Hank Nussbacher 14 Aug '14

14 Aug '14

At 18:10 12/08/2014 -0400, William Herrin wrote: We went with 768 - enough time to replace the routers with ASR9010s. It is merely a stop-gap measure to give everyone time to replace their routers in an orderly fashion. -Hank >On Tue, Aug 12, 2014 at 2:42 PM, Hank Nussbacher <hank(a)efes.iucc.ac.il> wrote: > > > http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-swi… > >I note that the recommended command in that article, "mls cef >maximum-routes ip 1000", will throw most of your IPv6 routes out of >the TCAM instead. Which if you have any IPv6 traffic of substance just >kills you in the other direction. Might want to try something more >like "mls cef maximum-routes ip 900". > >Regards, >Bill Herrin > >-- >William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us >Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/> >Can I solve your unusual networking challenges?

8 9

RTT of ICMP "TTL exceeded" messages in Level3 network remains the same throughout the network
by Martin T 13 Aug '14

13 Aug '14

Hi, if I make a traceroute to a host in San Jose in Level3 network from DigitalOcean server in Amsterdam, then in Level3 network(hop 6 in example below) the RTT remains the same: # traceroute -q 1 -I ZYNGA-INC.edge1.SanJose3.Level3.net traceroute to ZYNGA-INC.edge1.SanJose3.Level3.net (4.53.208.114), 30 hops max, 60 byte packets 1 5.101.103.253 (5.101.103.253) 0.265 ms 2 95.85.0.229 (95.85.0.229) 0.236 ms 3 ix-4-2-0-0.tcore1.AV2-Amsterdam.as6453.net (195.219.194.25) 0.275 ms 4 if-7-2.tcore1.AD1-Amsterdam.as6453.net (195.219.194.46) 0.630 ms 5 4.68.63.41 (4.68.63.41) 0.635 ms 6 vl-3603-ve-227.csw2.Amsterdam1.Level3.net (4.69.162.153) 155.309 ms 7 ae-56-221.ebr2.Amsterdam1.Level3.net (4.69.153.201) 155.627 ms 8 ae-46-46.ebr2.London1.Level3.net (4.69.143.74) 153.470 ms 9 * 10 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 148.972 ms 11 * 12 ae-2-2.ebr1.SanJose1.Level3.net (4.69.135.185) 147.881 ms 13 ae-91-91.csw4.SanJose1.Level3.net (4.69.153.14) 149.632 ms 14 ae-4-90.edge1.SanJose3.Level3.net (4.69.152.208) 151.107 ms 15 ZYNGA-INC.edge1.SanJose3.Level3.net (4.53.208.114) 154.431 ms # In other words, one sees the RTT of the end-host as a RTT for all the hops in Level3 netwotk. If I make the traceroute to penultimate hop ae-4-90.edge1.SanJose3.Level3.net, then RTT is as expected: root@vserver:~# traceroute -q 1 -I ae-4-90.edge1.SanJose3.Level3.net traceroute to ae-4-90.edge1.SanJose3.Level3.net (4.69.152.208), 30 hops max, 60 byte packets 1 5.101.103.254 (5.101.103.254) 0.228 ms 2 95.85.0.237 (95.85.0.237) 0.217 ms 3 ix-4-2-0-0.tcore1.AV2-Amsterdam.as6453.net (195.219.194.25) 0.276 ms 4 if-7-2.tcore1.AD1-Amsterdam.as6453.net (195.219.194.46) 0.656 ms 5 4.68.63.41 (4.68.63.41) 0.607 ms 6 vl-3604-ve-228.csw2.Amsterdam1.Level3.net (4.69.162.157) 0.696 ms 7 ae-56-221.ebr2.Amsterdam1.Level3.net (4.69.153.201) 0.677 ms 8 ae-45-45.ebr2.London1.Level3.net (4.69.143.70) 7.059 ms 9 ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 76.311 ms 10 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 76.265 ms 11 ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41) 76.820 ms 12 ae-2-2.ebr1.SanJose1.Level3.net (4.69.135.185) 149.101 ms 13 ae-91-91.csw4.SanJose1.Level3.net (4.69.153.14) 150.557 ms 14 ae-4-90.edge1.SanJose3.Level3.net (4.69.152.208) 162.022 ms root@vserver:~# All the ICMP "TTL exceeded" messages except the first and the penultimate one in Level3 network have MPLS extensions header(s24.postimg.org/4z9at9z45/ICMP_echo_reply_MPLS_extensions.png) which is always the same except the tag value changes. How does this technically work? What are the advantages of such setup? thanks, Martin

3 2