- NANOG - lists.nanog.org

Weekly Routing Table Report
by Routing Analysis Role Account 25 Oct '13

25 Oct '13

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 26 Oct, 2013 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 470253 Prefixes after maximum aggregation: 189267 Deaggregation factor: 2.48 Unique aggregates announced to Internet: 233307 Total ASes present in the Internet Routing Table: 41263 Prefixes per ASN: 11.40 Origin-only ASes present in the Internet Routing Table: 35299 Origin ASes announcing only one prefix: 16281 Transit ASes present in the Internet Routing Table: 5957 Transit-only ASes present in the Internet Routing Table: 161 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 35 Max AS path prepend of ASN ( 55644) 31 Prefixes from unregistered ASNs in the Routing Table: 713 Unregistered ASNs in the Routing Table: 192 Number of 32-bit ASNs allocated by the RIRs: 5249 Number of 32-bit ASNs visible in the Routing Table: 7 Prefixes from 32-bit ASNs in the Routing Table: 12489 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 847 Number of addresses announced to Internet: 2652267476 Equivalent to 158 /8s, 22 /16s and 99 /24s Percentage of available address space announced: 71.6 Percentage of allocated address space announced: 71.6 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 95.1 Total number of prefixes smaller than registry allocations: 164267 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 111549 Total APNIC prefixes after maximum aggregation: 33829 APNIC Deaggregation factor: 3.30 Prefixes being announced from the APNIC address blocks: 113639 Unique aggregates announced from the APNIC address blocks: 46970 APNIC Region origin ASes present in the Internet Routing Table: 4880 APNIC Prefixes per ASN: 23.29 APNIC Region origin ASes announcing only one prefix: 1218 APNIC Region transit ASes present in the Internet Routing Table: 839 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 35 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1 Number of APNIC addresses announced to Internet: 729582016 Equivalent to 43 /8s, 124 /16s and 137 /24s Percentage of available APNIC address space announced: 85.3 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: 162893 Total ARIN prefixes after maximum aggregation: 81514 ARIN Deaggregation factor: 2.00 Prefixes being announced from the ARIN address blocks: 163685 Unique aggregates announced from the ARIN address blocks: 75962 ARIN Region origin ASes present in the Internet Routing Table: 15905 ARIN Prefixes per ASN: 10.29 ARIN Region origin ASes announcing only one prefix: 6003 ARIN Region transit ASes present in the Internet Routing Table: 1670 Average ARIN Region AS path length visible: 4.1 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2 Number of ARIN addresses announced to Internet: 1073475200 Equivalent to 63 /8s, 251 /16s and 238 /24s Percentage of available ARIN address space announced: 56.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: 118701 Total RIPE prefixes after maximum aggregation: 61311 RIPE Deaggregation factor: 1.94 Prefixes being announced from the RIPE address blocks: 122310 Unique aggregates announced from the RIPE address blocks: 78965 RIPE Region origin ASes present in the Internet Routing Table: 17512 RIPE Prefixes per ASN: 6.98 RIPE Region origin ASes announcing only one prefix: 8301 RIPE Region transit ASes present in the Internet Routing Table: 2841 Average RIPE Region AS path length visible: 5.1 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 1 Number of RIPE addresses announced to Internet: 656716388 Equivalent to 39 /8s, 36 /16s and 178 /24s Percentage of available RIPE address space announced: 95.5 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-200191 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: 52444 Total LACNIC prefixes after maximum aggregation: 9927 LACNIC Deaggregation factor: 5.28 Prefixes being announced from the LACNIC address blocks: 57512 Unique aggregates announced from the LACNIC address blocks: 26693 LACNIC Region origin ASes present in the Internet Routing Table: 2040 LACNIC Prefixes per ASN: 28.19 LACNIC Region origin ASes announcing only one prefix: 560 LACNIC Region transit ASes present in the Internet Routing Table: 388 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 35 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2 Number of LACNIC addresses announced to Internet: 141095728 Equivalent to 8 /8s, 104 /16s and 243 /24s Percentage of available LACNIC address space announced: 84.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: 11607 Total AfriNIC prefixes after maximum aggregation: 2559 AfriNIC Deaggregation factor: 4.54 Prefixes being announced from the AfriNIC address blocks: 12260 Unique aggregates announced from the AfriNIC address blocks: 4004 AfriNIC Region origin ASes present in the Internet Routing Table: 667 AfriNIC Prefixes per ASN: 18.38 AfriNIC Region origin ASes announcing only one prefix: 199 AfriNIC Region transit ASes present in the Internet Routing Table: 136 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 24 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1 Number of AfriNIC addresses announced to Internet: 48076544 Equivalent to 2 /8s, 221 /16s and 151 /24s Percentage of available AfriNIC address space announced: 47.8 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 2938 11558 943 Korea Telecom (KIX) 17974 2717 903 89 PT TELEKOMUNIKASI INDONESIA 7545 2095 319 112 TPG Internet Pty Ltd 4755 1782 391 187 TATA Communications formerly 9829 1557 1241 45 BSNL National Internet Backbo 9498 1206 309 74 BHARTI Airtel Ltd. 9583 1187 90 513 Sify Limited 4808 1164 2127 341 CNCGROUP IP network: China169 7552 1156 1080 13 Vietel Corporation 24560 1091 380 164 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 6389 3062 3689 58 BellSouth.net Inc. 22773 2185 2941 139 Cox Communications, Inc. 18566 2059 379 180 Covad Communications 1785 2035 684 130 PaeTec Communications, Inc. 20115 1682 1653 613 Charter Communications 4323 1615 1101 417 Time Warner Telecom 701 1509 11145 784 UUNET Technologies, Inc. 30036 1387 313 577 Mediacom Communications Corp 7018 1336 17778 865 AT&T WorldNet Services 6983 1293 755 578 ITC^Deltacom 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 8402 1839 544 17 OJSC "Vimpelcom" 34984 1361 244 223 TELLCOM ILETISIM HIZMETLERI A 20940 1081 394 828 Akamai Technologies European 31148 1000 44 19 FreeNet ISP 13188 885 99 58 TOV "Bank-Inform" 6830 770 2327 423 UPC Distribution Services 8551 755 370 41 Bezeq International 12479 686 800 49 Uni2 Autonomous System 35228 542 246 16 Avatar Broadband Limited 34744 515 158 54 SC GVM SISTEM 2003 SRL 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 3451 1780 88 NET Servicos de Comunicao S.A 10620 2610 424 240 TVCABLE BOGOTA 7303 1725 1135 234 Telecom Argentina Stet-France 18881 1486 844 20 Global Village Telecom 8151 1348 2827 417 UniNet S.A. de C.V. 11830 865 364 15 Instituto Costarricense de El 27947 843 93 92 Telconet S.A 6147 789 373 27 Telefonica Del Peru 6503 788 434 62 AVANTEL, S.A. 7738 780 1498 36 Telecomunicacoes da Bahia 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 36998 1864 112 5 Sudanese Mobile Telephone (ZA 24863 882 338 30 LINKdotNET AS number 6713 554 633 26 Itissalat Al-MAGHRIB 8452 409 956 9 TEDATA 24835 294 144 9 RAYA Telecom - Egypt 3741 258 921 216 The Internet Solution 36992 226 501 29 Etisalat MISR 29571 224 17 12 Ci Telecom Autonomous system 15706 221 32 6 Sudatel Internet Exchange Aut 29975 192 668 21 Vodacom 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 3451 1780 88 NET Servicos de Comunicao S.A 6389 3062 3689 58 BellSouth.net Inc. 4766 2938 11558 943 Korea Telecom (KIX) 17974 2717 903 89 PT TELEKOMUNIKASI INDONESIA 10620 2610 424 240 TVCABLE BOGOTA 22773 2185 2941 139 Cox Communications, Inc. 7545 2095 319 112 TPG Internet Pty Ltd 18566 2059 379 180 Covad Communications 1785 2035 684 130 PaeTec Communications, Inc. 36998 1864 112 5 Sudanese Mobile Telephone (ZA 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 3062 3004 BellSouth.net Inc. 17974 2717 2628 PT TELEKOMUNIKASI INDONESIA 10620 2610 2370 TVCABLE BOGOTA 22773 2185 2046 Cox Communications, Inc. 4766 2938 1995 Korea Telecom (KIX) 7545 2095 1983 TPG Internet Pty Ltd 1785 2035 1905 PaeTec Communications, Inc. 18566 2059 1879 Covad Communications 36998 1864 1859 Sudanese Mobile Telephone (ZA 8402 1839 1822 OJSC "Vimpelcom" Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 62734 UNALLOCATED 8.31.128.0/24 6939 Hurricane Electric 62773 UNALLOCATED 8.35.180.0/22 3356 Level 3 Communicatio 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 62719 UNALLOCATED 12.27.130.0/24 4323 Time Warner Telecom 13317 UNALLOCATED 12.44.10.0/24 7018 AT&T WorldNet Servic 23502 UNALLOCATED 12.44.44.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.103.0/24 209 Qwest 17300 UNALLOCATED 12.45.110.0/24 701 UUNET Technologies, 16476 UNALLOCATED 12.46.27.0/24 7018 AT&T WorldNet Servic 14764 UNALLOCATED 12.108.237.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.100.0.0/24 4847 China Networks Inter-Exchange Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.90.128.0/18 27418 OUTOFWALL INC. 23.90.192.0/18 36086 Broad Communications Technolo 23.91.0.0/19 40676 Psychz Networks 23.91.32.0/19 36315 Servpac Inc. 23.91.80.0/20 21560 Capital Technology Services G 23.91.96.0/20 40676 Psychz Networks 23.91.112.0/21 32475 MidPhase Inc. 23.91.160.0/19 36493 3757277 Canada Inc. (oa 295.c 23.91.160.0/22 36493 3757277 Canada Inc. (oa 295.c 23.91.164.0/22 36493 3757277 Canada Inc. (oa 295.c 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:11 /10:31 /11:92 /12:253 /13:480 /14:917 /15:1630 /16:12844 /17:6719 /18:11266 /19:22958 /20:32707 /21:35361 /22:49971 /23:43374 /24:249130 /25:871 /26:990 /27:469 /28:50 /29:79 /30:20 /31:0 /32:14 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 2012 2059 Covad Communications 36998 1829 1864 Sudanese Mobile Telephone (ZA 6389 1712 3062 BellSouth.net Inc. 8402 1535 1839 OJSC "Vimpelcom" 22773 1451 2185 Cox Communications, Inc. 30036 1235 1387 Mediacom Communications Corp 11492 1197 1238 Cable One 1785 1085 2035 PaeTec Communications, Inc. 6983 1034 1293 ITC^Deltacom 22561 965 1241 Digital Teleport, Inc Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:857 2:820 3:3 4:17 5:999 6:20 8:614 12:1888 13:3 14:884 15:11 16:3 17:17 18:19 20:21 23:498 24:1736 27:1604 31:1484 32:45 33:2 34:5 36:82 37:1841 38:920 39:4 40:181 41:3171 42:248 44:14 46:2031 47:7 49:681 50:837 52:12 54:39 55:6 56:2 57:26 58:1154 59:576 60:359 61:1473 62:1205 63:1979 64:4559 65:2340 66:4138 67:2116 68:1099 69:3291 70:877 71:491 72:2021 74:2566 75:328 76:309 77:1167 78:1074 79:656 80:1291 81:1015 82:657 83:635 84:590 85:1241 86:415 87:1009 88:563 89:1661 90:155 91:5658 92:618 93:1596 94:2037 95:1597 96:508 97:344 98:1048 99:42 100:31 101:613 103:3481 105:525 106:143 107:213 108:526 109:1912 110:974 111:1098 112:590 113:809 114:751 115:1035 116:990 117:838 118:1174 119:1294 120:372 121:745 122:1875 123:1252 124:1369 125:1434 128:647 129:237 130:328 131:661 132:348 133:158 134:545 135:67 136:278 137:268 138:351 139:176 140:203 141:334 142:544 143:420 144:501 145:89 146:519 147:405 148:767 149:356 150:142 151:592 152:410 153:205 154:49 155:486 156:286 157:424 158:282 159:768 160:356 161:483 162:805 163:227 164:634 165:574 166:256 167:624 168:1045 169:128 170:1122 171:181 172:25 173:1607 174:682 175:510 176:1275 177:2328 178:1947 179:195 180:1579 181:779 182:1341 183:454 184:661 185:951 186:2651 187:1502 188:1861 189:1290 190:7194 192:7111 193:5408 194:4040 195:3319 196:1321 197:1027 198:4744 199:5483 200:6106 201:2524 202:8974 203:8914 204:4517 205:2639 206:2836 207:2894 208:3983 209:3639 210:3012 211:1563 212:2140 213:1977 214:894 215:91 216:5402 217:1691 218:622 219:317 220:1275 221:566 222:326 223:508 End of report

1 0

A9K-MPA-20X1GE in ASR9001
by Julian Eble 25 Oct '13

25 Oct '13

Hello, Did you tried the service unsupported-transceiver command? Eng. Julian Eble

1 0

Re: A9K-MPA-20X1GE in ASR9001
by Nikolay Shopik 25 Oct '13

25 Oct '13

I don't have any GBIC/SPF inserted in it right now, it just turn off whole module. So won't allow me even fpd upgrade. On 25/10/13 14:02, Ray Ludendorff wrote: > > > It means that you did not purchase a original Cisco GBIC for the interface .. > Therefore it will not be TAC supported if you have problems with the interface. > There is a command to override this error and still use the interfaces. > > Sent from mobile device > >> On Oct 25, 2013, at 11:56, "Nikolay Shopik" <shopik(a)inblock.ru> wrote: >> >> Hey, anyone had issues with A9K-MPA-20X1GE in ASR9001? >> >> It get disabled for us after 20 seconds finishing initialization, with >> such message. >> >> %PLATFORM-SCC-2-BAD_ID_HW : Failed Identification Test in 0/130/0 [1/0] >> The module in 0/130/0 in this router may not be a genuineCisco product. >> >>

1 0

Re: BGP failure analysis and recommendations
by Scott Weeks 25 Oct '13

25 Oct '13

--- courtneysmith(a)comcast.net wrote: From: Courtney Smith <courtneysmith(a)comcast.net> > From: JRC NOC <nospam-nanog(a)jensenresearch.com> > Regrettably, during the outage our BGP session remained active and we > continued receiving full routes from the affected AS. And our prefixes > continued to be advertised at their border. However basically none of the Did you provider provide an official written RFO yet? ------------------------------------------------------------ When deciding to keep or change providers after a major mistake like this is do they send out an honest description of the mistake and what has been done to stop it from happening again in the future. Corporatespeak reports are grounds for dismissal! ;-) scott

1 0

Cogent 100M DIA in Denver
by Tri Tran 25 Oct '13

25 Oct '13

They're lit in the bulding and have a much faster installation interval. How reliable are they? Tri Tran

12 13

Re: BGP failure analysis and recommendations
by Courtney Smith 25 Oct '13

25 Oct '13

On Oct 24, 2013, at 2:13 AM, nanog-request(a)nanog.org wrote: > Message: 7 > Date: Wed, 23 Oct 2013 22:40:34 -0400 > From: JRC NOC <nospam-nanog(a)jensenresearch.com> > To: nanog(a)nanog.org > Subject: BGP failure analysis and recommendations > Message-ID: > <5.1.0.14.0.20131023214304.0396ead0(a)authsmtp.jensenresearch.com> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > Hello Nanog - > > On Saturday, October 19th at about 13:00 UTC we experienced an IP failure > at one of our sites in the New York area. > It was apparently a widespread outage on the East coast, but I haven't seen > it discussed here. > > We are multihomed, using EBGP to three (diverse) upstream providers. One > provider experienced a hardware failure in a core component at one POP. > Regrettably, during the outage our BGP session remained active and we > continued receiving full routes from the affected AS. And our prefixes > continued to be advertised at their border. However basically none of the > traffic between those prefixes over that provider was delivered. The bogus > routes stayed up for hours. We shutdown the BGP peering session when the > nature of the problem became clear. This was effective. I believe that all > customer BGP routes were similarly affected, including those belonging to > some large regional networks and corporations. I have raised the questions > below with the provider but haven't received any information or advice. > > Did you provider provide an official written RFO yet? Courtney Smith courtneysmith(a)comcast.net () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

1 0

EFF needs your help to stop patent trolls
by Peter Eckersley 24 Oct '13

24 Oct '13

Hi network operators, Apologies for a non-technical post, but I believe this is an issue of relevance to the NANOG community. EFF is collecting signatures from prominent engineers and technologists for a letter to the US Congress calling for reform of the software patent system to protect inventors and inventive companies against patent trolls, who use patents for extortionate purposes without ever shipping any products. We're doing this now because there is a window of political opportunity to actually get this problem fixed in the next few months. Draft text of the letter is below. If you broadly agree and would like to sign on, please send me a private reply with: - Your name; - A 1-3 line bio that summarizes your main career achievements, which might be a current or past affiliation, RFCs you wrote, networks you built, companies you founded, etc; - Whether you hold US patents; if so, how many you hold, and (if you know them) the patent numbers ============================================================= Dear Senators and Congressmen, We, the undersigned, are a group of inventors, technologists and entrepreneurs. Many of us have founded technology businesses; we have invented many of the protocols, systems and devices that make the Internet work, and we are collectively listed as the inventors on [n thousand] patents. We write to you today about the U.S. patent system. That system is broken. Based on our experiences building and deploying new digital technologies, we believe that software patents are doing more harm than good. Perhaps it is time to reexamine the idea, dating from the 1980s, that government-issued monopolies on algorithms, protocols and data structures are the best way to promote the advancement of computer science. But that will be a hard task, and one we don't expect to happen quickly. Unfortunately, aspects of the problem have become so acute they must be addressed immediately. Broad, vague patents covering software-type inventions--some of which we ourselves are listed as inventors on--are a malfunctioning component of America's inventive machinery. This is particularly the case when those patents end up in the hands of non-practicing patent trolls. These non-practicing entities do not make or sell anything. Their exploitation of patents as a tool for extortion is undermining America’s technological progress; patent trolls are collecting taxes on innovation by extracting billions of dollars in dubious licensing fees, and wasting the time and management resources of creative businesses. Many of us would have achieved much less in our careers if the trolling problem had been as dire in past decades as it is now. Some legislative proposals under current consideration would fix the trolling problem. These include: - Requiring that patent lawsuits actually explain which patents are infringed by which aspects of a defendant's technology, and how; - Making clear who really owns the patent at issue; - Allowing courts to shift fees to winning parties, making it rational for those threatened with an egregious patent suit to actually fight against the threat rather than paying what amounts to protection money; - Ensuring that those who purchase common, off-the-shelf technologies are shielded if they are sued for using them; and - Increasing opportunities for streamlined patent review at the patent office. While subduing the trolling threat, these proposed changes will not fix the software patent problem. Congress should consider ways to stop software patents from interfering with open standards and open source software; from being claimed on problems, rather than solutions; and from being drafted so obscurely that they teach us nothing and cannot be searched. Congress needs to examine the very question of whether their net impact is positive. But for now, we urge you to implement simple and urgently necessary reforms. We believe in the promise of technology and the power of creation to increase access to information, to create jobs, and to make the world a better place. Please do not let patent trolls continue to frustrate that purpose. -- Peter Eckersley pde(a)eff.org Technology Projects Director Tel +1 415 436 9333 x131 Electronic Frontier Foundation Fax +1 415 436 9993

1 0

Looking for Juniper P-1GE-SFP-QPP in NYC area
by Eric Wieling 24 Oct '13

24 Oct '13

We had a P-1GE-SFP-QPP card go out today, looking for a source in the NYC area to get it replaced ASAP. Thanks!

1 0

Point to Point Ethernet request
by Phibee Network Operation Center 24 Oct '13

24 Oct '13

Hello, Looking for a solution to connect two sitesto my POP: Site A: Frederick, MD 21701 USA Site B: Archbold, OH 43502 USA My POP: New York (into a DC: Equinix or Telehouse New York) A Layer 2 connection at 4, 6 or 10 Mbits Any one know a good operator for this ? Best Regards Jerome SCHEVINGT

6 5

Fundamental questions of backbone design
by Anurag Bhatia 24 Oct '13

24 Oct '13

Hello everyone I have some fundamental questions about backbone design. Feel free to point me to any discussions/presentation material related to these questions. 1. As I understand it's (sort off) common practice to give highest localpref to customer routes then peering and finally transit. Does this works well or you see issues with people who have 10+ prepends on some peering routes calling you to not send traffic via those circuits? Does it makes sense to put a rule to avoid routes 2-3 AS path away when changing local preference? 2. If I have more peering capacity and relatively less capacity between my own PoPs and I start injecting routes in my IGP then how to prevent change of choking of backbone? Is it standard practice to have more capacity on backbone then peering links? Or I have to inject less routes in IGP - say a few % of total routes? 3. How can I maintain use of routes I am learning from various other networks (transit+peers+customer) across my IGP? Is BGP community tagging good way out? 4. How is iBGP Vs OSPF for IGP? I keep on hearing that OSPF is good & lot more faster in changing routes during a breakdown as compared to slow hold time based iBGP session. Is there's more clear comparison of limitations of both when designing? Appreciate your time & help. Thanks. -- Anurag Bhatia anuragbhatia.com Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia> Skype: anuragbhatia.com

6 8