- Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 14 Jul '17

14 Jul '17

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, MENOG, SAFNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG. 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 15 Jul, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 654847 Prefixes after maximum aggregation (per Origin AS): 254687 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 315827 Total ASes present in the Internet Routing Table: 57784 Prefixes per ASN: 11.33 Origin-only ASes present in the Internet Routing Table: 49994 Origin ASes announcing only one prefix: 22094 Transit ASes present in the Internet Routing Table: 7790 Transit-only ASes present in the Internet Routing Table: 227 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 41 Max AS path prepend of ASN ( 55644) 36 Prefixes from unregistered ASNs in the Routing Table: 103 Numnber of instances of unregistered ASNs: 107 Number of 32-bit ASNs allocated by the RIRs: 19455 Number of 32-bit ASNs visible in the Routing Table: 15125 Prefixes from 32-bit ASNs in the Routing Table: 61489 Number of bogon 32-bit ASNs visible in the Routing Table: 64 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 449 Number of addresses announced to Internet: 2848853092 Equivalent to 169 /8s, 206 /16s and 12 /24s Percentage of available address space announced: 76.9 Percentage of allocated address space announced: 76.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.7 Total number of prefixes smaller than registry allocations: 218082 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 179419 Total APNIC prefixes after maximum aggregation: 51490 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 178463 Unique aggregates announced from the APNIC address blocks: 73928 APNIC Region origin ASes present in the Internet Routing Table: 8234 APNIC Prefixes per ASN: 21.67 APNIC Region origin ASes announcing only one prefix: 2307 APNIC Region transit ASes present in the Internet Routing Table: 1169 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 41 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3079 Number of APNIC addresses announced to Internet: 763526756 Equivalent to 45 /8s, 130 /16s and 126 /24s 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-64098, 64297-64395, 131072-137529 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: 199397 Total ARIN prefixes after maximum aggregation: 94990 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 201288 Unique aggregates announced from the ARIN address blocks: 92639 ARIN Region origin ASes present in the Internet Routing Table: 17926 ARIN Prefixes per ASN: 11.23 ARIN Region origin ASes announcing only one prefix: 6646 ARIN Region transit ASes present in the Internet Routing Table: 1767 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2091 Number of ARIN addresses announced to Internet: 1108935584 Equivalent to 66 /8s, 25 /16s and 3 /24s 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, 64198-64296, 393216-397212 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: 175704 Total RIPE prefixes after maximum aggregation: 85943 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 171448 Unique aggregates announced from the RIPE address blocks: 103121 RIPE Region origin ASes present in the Internet Routing Table: 24189 RIPE Prefixes per ASN: 7.09 RIPE Region origin ASes announcing only one prefix: 11133 RIPE Region transit ASes present in the Internet Routing Table: 3406 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5996 Number of RIPE addresses announced to Internet: 712565120 Equivalent to 42 /8s, 120 /16s and 225 /24s 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, 64396-64495 196608-207259 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: 83068 Total LACNIC prefixes after maximum aggregation: 18437 LACNIC Deaggregation factor: 4.51 Prefixes being announced from the LACNIC address blocks: 84305 Unique aggregates announced from the LACNIC address blocks: 38878 LACNIC Region origin ASes present in the Internet Routing Table: 6124 LACNIC Prefixes per ASN: 13.77 LACNIC Region origin ASes announcing only one prefix: 1678 LACNIC Region transit ASes present in the Internet Routing Table: 1144 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 27 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3637 Number of LACNIC addresses announced to Internet: 170821600 Equivalent to 10 /8s, 46 /16s and 135 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 17154 Total AfriNIC prefixes after maximum aggregation: 3773 AfriNIC Deaggregation factor: 4.55 Prefixes being announced from the AfriNIC address blocks: 18894 Unique aggregates announced from the AfriNIC address blocks: 6930 AfriNIC Region origin ASes present in the Internet Routing Table: 1052 AfriNIC Prefixes per ASN: 17.96 AfriNIC Region origin ASes announcing only one prefix: 329 AfriNIC Region transit ASes present in the Internet Routing Table: 207 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 31 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 322 Number of AfriNIC addresses announced to Internet: 92379904 Equivalent to 5 /8s, 129 /16s and 155 /24s 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 4538 5549 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3985 406 384 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2972 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2795 11134 754 KIXS-AS-KR Korea Telecom, KR 9829 2753 1499 540 BSNL-NIB National Internet Backbone, IN 9808 2172 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2090 423 223 TATACOMM-AS TATA Communications formerl 45899 2055 1428 111 VNPT-AS-VN VNPT Corp, VN 7552 1641 1104 73 VIETEL-AS-AP Viettel Corporation, VN 9498 1598 361 141 BBIL-AP BHARTI Airtel Ltd., IN 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 22773 3814 2953 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3436 1325 84 SHAW - Shaw Communications Inc., CA 18566 2178 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2066 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2011 2172 418 CHARTER-NET-HKY-NC - Charter Communicat 209 1841 5067 639 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16509 1829 3698 599 AMAZON-02 - Amazon.com, Inc., US 30036 1803 326 292 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1694 854 231 ITCDELTA - Earthlink, Inc., US 701 1560 10559 630 UUNET - MCI Communications Services, In 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 39891 3387 186 23 ALJAWWALSTC-AS, SA 8551 2974 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2927 970 2113 AKAMAI-ASN1, US 34984 2023 330 413 TELLCOM-AS, TR 9121 1967 1691 17 TTNET, TR 13188 1603 100 55 TRIOLAN, UA 12479 1590 1046 54 UNI2-AS, ES 12389 1514 1408 625 ROSTELECOM-AS, RU 6849 1225 355 21 UKRTELNET, UA 8402 1073 544 15 CORBINA-AS OJSC "Vimpelcom", RU 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 10620 3538 543 194 Telmex Colombia S.A., CO 8151 2503 3398 585 Uninet S.A. de C.V., MX 11830 2090 369 57 Instituto Costarricense de Electricidad 6503 1554 437 53 Axtel, S.A.B. de C.V., MX 7303 1552 1012 243 Telecom Argentina S.A., AR 6147 1282 377 27 Telefonica del Peru S.A.A., PE 3816 1024 501 93 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 966 2299 182 CLARO S.A., BR 11172 914 126 81 Alestra, S. de R.L. de C.V., MX 18881 894 1052 23 TELEFÔNICA BRASIL S.A, BR 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 1230 398 51 LINKdotNET-AS, EG 37611 736 91 8 Afrihost, ZA 36903 711 357 129 MT-MPLS, MA 36992 648 1375 26 ETISALAT-MISR, EG 24835 501 850 15 RAYA-AS, EG 37492 405 320 75 ORANGE-, TN 29571 401 36 10 CITelecom-AS, CI 15399 354 35 7 WANANCHI-, KE 8452 335 1730 17 TE-AS TE-AS, EG 2018 304 327 74 TENET-1, ZA 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 4538 5549 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3985 406 384 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3814 2953 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3538 543 194 Telmex Colombia S.A., CO 6327 3436 1325 84 SHAW - Shaw Communications Inc., CA 39891 3387 186 23 ALJAWWALSTC-AS, SA 8551 2974 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 17974 2972 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2927 970 2113 AKAMAI-ASN1, US 4766 2795 11134 754 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3814 3656 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3985 3601 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3387 3364 ALJAWWALSTC-AS, SA 6327 3436 3352 SHAW - Shaw Communications Inc., CA 10620 3538 3344 Telmex Colombia S.A., CO 8551 2974 2934 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 17974 2972 2899 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9829 2753 2213 BSNL-NIB National Internet Backbone, IN 9808 2172 2140 CMNET-GD Guangdong Mobile Communication Co.Ltd. 18566 2178 2069 MEGAPATH5-US - MegaPath Corporation, US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65530 PRIVATE 45.249.40.0/24 133720 SOFTCALLCOC-AS SOFT CALL CUST- 65010 PRIVATE 46.56.192.0/21 42772 VELCOM-AS, BY 65010 PRIVATE 46.56.224.0/21 42772 VELCOM-AS, BY 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 4294901876 PRIVATE 59.101.19.0/24 2764 AAPT AAPT Limited, AU 4294902000 PRIVATE 59.101.45.0/24 2764 AAPT AAPT Limited, AU Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.48.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.49.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.50.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.51.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/24 64091 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.12.0/23 62878 XLITT - Xlitt, US 41.78.180.0/23 37265 -Reserved AS-, ZZ 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:15 /9:13 /10:36 /11:104 /12:284 /13:552 /14:1048 /15:1847 /16:13458 /17:7643 /18:13423 /19:24663 /20:38644 /21:41266 /22:77851 /23:64618 /24:367168 /25:866 /26:605 /27:641 /28:34 /29:22 /30:18 /31:2 /32:26 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3236 3436 SHAW - Shaw Communications Inc., CA 22773 2984 3814 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 39891 2946 3387 ALJAWWALSTC-AS, SA 8551 2439 2974 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2071 2178 MEGAPATH5-US - MegaPath Corporation, US 30036 1594 1803 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 11830 1480 2090 Instituto Costarricense de Electricidad y Telec 10620 1474 3538 Telmex Colombia S.A., CO 11492 1403 1559 CABLEONE - CABLE ONE, INC., US 6389 1372 2066 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1583 2:803 4:18 5:2427 6:34 8:1052 12:1809 13:126 14:1736 15:28 16:2 17:159 18:90 20:61 23:2411 24:1889 25:2 27:2450 31:1933 32:84 33:15 35:21 36:384 37:2361 38:1332 39:67 40:98 41:3003 42:471 43:1946 44:74 45:2891 46:2800 47:158 49:1236 50:992 51:19 52:835 54:365 55:6 56:4 57:43 58:1559 59:1049 60:389 61:1959 62:1681 63:1903 64:4588 65:2222 66:4558 67:2272 68:1242 69:3357 70:1151 71:586 72:2226 74:2677 75:387 76:426 77:1545 78:1438 79:2369 80:1407 81:1389 82:1000 83:723 84:941 85:1793 86:460 87:1165 88:756 89:2116 90:172 91:6190 92:987 93:2376 94:2394 95:2678 96:630 97:352 98:1062 99:90 100:154 101:1191 103:15349 104:2995 105:180 106:508 107:1769 108:830 109:2878 110:1457 111:1724 112:1194 113:1259 114:1044 115:1724 116:1805 117:1720 118:2143 119:1607 120:1057 121:1109 122:2265 123:1822 124:1482 125:1906 128:788 129:647 130:434 131:1404 132:537 133:200 134:666 135:223 136:447 137:427 138:1939 139:491 140:399 141:610 142:774 143:914 144:804 145:179 146:1045 147:700 148:1464 149:583 150:717 151:977 152:701 153:299 154:847 155:757 156:621 157:655 158:461 159:1524 160:699 161:737 162:2515 163:539 164:877 165:1400 166:380 167:1242 168:2969 169:824 170:3428 171:319 172:1022 173:1958 174:805 175:745 176:1862 177:4041 178:2539 179:1135 180:2195 181:1894 182:2361 183:996 184:866 185:10099 186:3258 187:2214 188:2605 189:1824 190:8327 191:1352 192:9514 193:5775 194:4677 195:3921 196:2096 197:1375 198:5506 199:5893 200:7476 201:4346 202:10366 203:10014 204:4486 205:2817 206:3023 207:3134 208:3954 209:3959 210:3936 211:2121 212:2847 213:2534 214:868 215:66 216:5802 217:2111 218:865 219:598 220:1691 221:933 222:759 223:1189 End of report

1 0

Testing methodology for the Chinese quantum satellite link?
by Bill Woodcock 14 Jul '17

14 Jul '17

Does anyone who understands quantum networking better than I do have an opinion on the testing methodology that the Chinese team used to confirm entanglement? I guess, more specifically, my question is: when they say that they got 911 positive results out of “millions” of attempts, does this significantly exceed any expected false-positive rate for the confirmation methodology? If so, by what margin? Obviously, if you were just flipping coins, and measured the results once, you’d get 50% positive correlation, twice and you’d get 25% correlation, ten times and you’d get 0.1% correlation, and you’d be at 911 out of a million. So, how much better than that are we talking about? -Bill

2 1

BGP peering question
by craig washington 13 Jul '17

13 Jul '17

Hello, Newbie question, what criteria do you look for when you decide that you want to peer with someone or if you will accept peering with someone from an ISP point of view. Thanks.

17 20

Yahoo Mail Delivery Problems
by Josiah Ritchie 13 Jul '17

13 Jul '17

We're seeing our deferred queues fill up with mail to Yahoo. Some mail appears to be delivering, but many are not. Is anyone else experiencing problems delivering mail to Yahoo? The Internet suggests that this error has been a result of Yahoo stability in the past. The following message is coming back: host mta5.am0.yahoodns.net[98.136.217.203] said: 451 4.3.2 Internal error > reading data (in reply to MAIL FROM command) > lost connection with mta5.am0.yahoodns.net[98.136.217.203] while sending > RCPT TO Thanks, Josiah

1 0

noction vs border6 vs kentik vs fcp vs ?
by ShaColby Jackson 13 Jul '17

13 Jul '17

I know this topic has gone around a couple times but wondering if there are any new strong opinions on inbound+outbound traffic analysis with a bonus for excellence in traffic engineering at the edge. A typical use case would be finding an AS or prefix representing a large volume of inbound and/or outbound traffic via provider A that could just as well or better be moved via provider B. I know solutions like Kentik do a lot more but I’m focusing on just the above use case. Also ignoring the cloud vs. on-prem difference, assume that doesn’t matter. Will reward any helpful advice with a picture of me give you a virtual high-five or 2 thumbs up. Your choice.

4 4

10G MetroE 1-2U Switch
by Erik Sundberg 13 Jul '17

13 Jul '17

Hey Nanog, Looking for a new metroE Edge switch that has more that 10x 10G ports. I am having a hard time finding anything worthwhile without buying a full blown ASR9K Chassis or another vendor's chassis. Requirements MEF compliant 1-2U small foot print 10G Ports will be used for ENNI's and UNI Ports Prefer MPLS support for L2VPN's (EoMPLS and VPLS) QOS per Sub interface\vlan on a ENNI Cost effect 10G Ports 100G Not required Looking at the ASR920's - Great box for 1G but not enough 10G Ports Only 4 NCS5001/NCS5501 - New\unproven\probably buggy, Lacking some features & QOS issues :/ ASR900 - Looks good, but was hoping for a smaller foot print. If I remember right the 8x10G Cards can't go in every slot. Any other platforms I should be looking at? Ciena, Brocade, Juniper? Thanks in advance! -Erik ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.

16 28

Hacked DVRs again?! (Probably the wrong forum, but probably of interest nonetheless)
by Large Hadron Collider 12 Jul '17

12 Jul '17

So, I run a small chat service and it has attracted abuse from multiple kinds of open device. Most recently, I've found DVRs being spammed through. This is the kind of "default password"/"open Cisco" abuse that is very hard to detect with an open proxy scanner without, well, logging in and seeing if you get a shell. Has anyone ever seen this? What can I do to prevent it?

1 0

Some advice on IPv6 planning and ARIN request, please
by Oliver O'Boyle 12 Jul '17

12 Jul '17

Hello, If anyone out there could provide some input or advice on how to best handle our upcoming leap into IPv6, it would be much appreciated. I want to make sure we're playing nicely and not causing anyone any unnecessary grief before we deploy. We're currently in the planning stage and can make whatever changes we need to. Situation: We're an end-user org and qualify for a /40 assignment because we operate over 60 sites and some of those are/will be multihomed. We manage hotels in Canada only, but from coast to coast to coast and everywhere in between. Our corporate network and org structure is optimized for three regions. We also have, and continue to grow into, cloud infrastructure and foresee wanting to bring our own addresses (.e.g., to AWS VPC when that option becomes available). As such, an obvious design strategy would be to break the /40 into 4 x /42's. However, due to an imbalance in national site distribution, 50% of our sites are located in one region (Region A). Additionally, historical and forecasted growth indicates that it's perfectly reasonable for us to expect growth of an additional 16 sites in that same region over the next 3-5 years. We would prefer to summarize at the /42 level, announced from our last-mile providers. There are 3 primary last-mile providers so this strategy would help significantly reduce the number of global routes being injected. If we split regions evenly at /42 and if we follow the /48-per-site best practice (which I believe is justifiable in our situation - see below), Region A will be at 50% usage immediately. Adding 16 more sites brings it to 75% usage in only a few years. The other regions would be at ~33% usage (Region B) and 15% usage (Region C) and will see moderate growth in 3-5 years. Cloud will initially be at 2-4% usage (Region D) but will also grow quickly within 3-5 years. Ideal situation: ARIN assigns us a /36 and we don't need to worry about re-addressing. Even if they can offer us contiguous space with a second request to increase our assignment, we would likely need to re-address a significant portion of our sites which would be painful and time-consuming. Less ideal situation #1: Split the first level of subnets unevenly at 1 x /41 and 2 x /42 and hope we can carve out some of that space for use in our cloud infrastructure. This strategy would solve our Region A problem and would keep Regions B and C from going to 68% and 34% utilization immediately but it would mess up Region D and impact Regions B and C. Less ideal situation #2: Split the first level of subnets unevenly at 1 x /41, 1 x /42, and 2 x /43. This strategy would solve our Region A and Region B problems but would constrain Region C and Region D future growth options somewhat. Less ideal situation #3: Drop the /48 per site default to somewhere between a /49 and /53 and hope we don't bust out of those. This strategy would allow us to keep top-level aggregation at /42's but would move the site assignments off the nibble boundaries. Less ideal situation #4: Keep 4 x /42's and hope we don't expand out of them in Region A. This strategy would imply we don't wish for our business to grow and is pretty risky. I feel the /48 site default is justifiable because of the various applications and services that are currently, or could likely be offered at hotels. E.g., each room gets a /64 for all guest-internet devices registered to that room. + IoT could result in the same rule (each room gets a /64) or, perhaps a bit simpler, each class of IoT device is on a /64 or each IoT vendor is on a /64. There will also be new applications that come out with similar possible needs. With some of our hotels in the 500-1000 room range, we're looking at as many as 2000 /64's per site in the next 5 or so years. Plus backoffice/admin subnets. I think the ideal situation is out as ARIN policy wouldn't allow them to assign us a /36 at this time. Unless someone knows something that can help us here. Assuming we can't get a /36, my feeling is that less ideal situation #2 is better than #3 is better than #1 is better than #4, assuming we're following the following design best-practices: a) assign top-level aggregations evenly (which we'd be breaking a bit with option #2) b) reduce global routes as much as possible c) stay on the nibble boundary as much as possible d) default to /48 per site Any thoughts or advice would be much appreciated. Thanks in advance, Oliver

14 21

Re: loc.gov
by Joly MacFie 10 Jul '17

10 Jul '17

I also noticed an outages-announce - is that for people who don't sub to the other two, or should one do all 3 to be fully notified? j On Sun, Jul 9, 2017 at 10:28 PM, Damian Menscher via NANOG <nanog(a)nanog.org> wrote: > There are two lists, depending on whether you're reporting an ongoing > outage, or just talking about one: > > https://puck.nether.net/mailman/listinfo/outages > https://puck.nether.net/mailman/listinfo/outages-discussion > > Damian > > On Sat, Jul 8, 2017 at 6:41 PM, Nicholas Oas <nicholas.oas(a)gmail.com> > wrote: > > > I'd be interested to know the answer to this one as well, as I've gone > > looking for the outages list in the past and found the same result. > > > > Have isitdownorjustme sites simply superceded the need for such lists? > > > > On Jul 8, 2017 6:59 PM, "Joly MacFie" <joly(a)punkcast.com> wrote: > > > > > Actually, now I go to https://www.nanog.org/list/faq/other > > > > > > I don't see any such thing, just http://www.outages.org/ where the > > latest > > > report is 2013. > > > > > > Also "See *http://www.isp-lists.com/* <http://www.isp-lists.com/> for > > many > > > other topic-specific lists." takes one somewhere else entirely! > > > > > > j > > > > > > > > > > > > On Sat, Jul 8, 2017 at 6:47 PM, Doug Barton <dougb(a)dougbarton.us> > wrote: > > > > > > > Isn't that a problem that suggests its own solution? > > > > > > > > > > > > > > > > On 7/8/2017 1:43 PM, Joly MacFie wrote: > > > > > > > >> (sorry I'm not on the outage list) > > > >> > > > >> -- > > > >> --------------------------------------------------------------- > > > >> Joly MacFie 218 565 9365 Skype:punkcast > > > >> -------------------------------------------------------------- > > > >> - > > > >> > > > > > > > > > > -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

2 1

loc.gov
by Joly MacFie 09 Jul '17

09 Jul '17

(sorry I'm not on the outage list) Any clues as to what the problem is at the Library of Congress? Appears to be DNS. Is it a DDOS? http://www.loc.gov/ -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

12 14