- Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 03 Aug '18

03 Aug '18

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, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG 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 04 Aug, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 709541 Prefixes after maximum aggregation (per Origin AS): 272353 Deaggregation factor: 2.61 Unique aggregates announced (without unneeded subnets): 340445 Total ASes present in the Internet Routing Table: 61400 Prefixes per ASN: 11.56 Origin-only ASes present in the Internet Routing Table: 53022 Origin ASes announcing only one prefix: 23103 Transit ASes present in the Internet Routing Table: 8378 Transit-only ASes present in the Internet Routing Table: 271 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 34 Max AS path prepend of ASN ( 30873) 32 Prefixes from unregistered ASNs in the Routing Table: 69 Number of instances of unregistered ASNs: 69 Number of 32-bit ASNs allocated by the RIRs: 23546 Number of 32-bit ASNs visible in the Routing Table: 18953 Prefixes from 32-bit ASNs in the Routing Table: 79380 Number of bogon 32-bit ASNs visible in the Routing Table: 37 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 286 Number of addresses announced to Internet: 2857337412 Equivalent to 170 /8s, 79 /16s and 130 /24s Percentage of available address space announced: 77.2 Percentage of allocated address space announced: 77.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.0 Total number of prefixes smaller than registry allocations: 236740 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 193849 Total APNIC prefixes after maximum aggregation: 55014 APNIC Deaggregation factor: 3.52 Prefixes being announced from the APNIC address blocks: 192078 Unique aggregates announced from the APNIC address blocks: 78887 APNIC Region origin ASes present in the Internet Routing Table: 8980 APNIC Prefixes per ASN: 21.39 APNIC Region origin ASes announcing only one prefix: 2527 APNIC Region transit ASes present in the Internet Routing Table: 1331 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3937 Number of APNIC addresses announced to Internet: 767366915 Equivalent to 45 /8s, 189 /16s and 23 /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: 210390 Total ARIN prefixes after maximum aggregation: 100012 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 210547 Unique aggregates announced from the ARIN address blocks: 99642 ARIN Region origin ASes present in the Internet Routing Table: 18194 ARIN Prefixes per ASN: 11.57 ARIN Region origin ASes announcing only one prefix: 6731 ARIN Region transit ASes present in the Internet Routing Table: 1810 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2391 Number of ARIN addresses announced to Internet: 1103191200 Equivalent to 65 /8s, 193 /16s and 92 /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: 194343 Total RIPE prefixes after maximum aggregation: 92754 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 190547 Unique aggregates announced from the RIPE address blocks: 112905 RIPE Region origin ASes present in the Internet Routing Table: 25366 RIPE Prefixes per ASN: 7.51 RIPE Region origin ASes announcing only one prefix: 11433 RIPE Region transit ASes present in the Internet Routing Table: 3511 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7254 Number of RIPE addresses announced to Internet: 714013824 Equivalent to 42 /8s, 142 /16s and 252 /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: 91640 Total LACNIC prefixes after maximum aggregation: 20428 LACNIC Deaggregation factor: 4.49 Prefixes being announced from the LACNIC address blocks: 93081 Unique aggregates announced from the LACNIC address blocks: 40845 LACNIC Region origin ASes present in the Internet Routing Table: 7379 LACNIC Prefixes per ASN: 12.61 LACNIC Region origin ASes announcing only one prefix: 2020 LACNIC Region transit ASes present in the Internet Routing Table: 1393 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 32 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4922 Number of LACNIC addresses announced to Internet: 172281632 Equivalent to 10 /8s, 68 /16s and 207 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + 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: 19249 Total AfriNIC prefixes after maximum aggregation: 4087 AfriNIC Deaggregation factor: 4.71 Prefixes being announced from the AfriNIC address blocks: 23002 Unique aggregates announced from the AfriNIC address blocks: 7917 AfriNIC Region origin ASes present in the Internet Routing Table: 1180 AfriNIC Prefixes per ASN: 19.49 AfriNIC Region origin ASes announcing only one prefix: 392 AfriNIC Region transit ASes present in the Internet Routing Table: 236 Average AfriNIC Region AS path length visible: 4.5 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 449 Number of AfriNIC addresses announced to Internet: 100038144 Equivalent to 5 /8s, 246 /16s and 118 /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 4694 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4383 467 464 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 2979 1153 84 VIETEL-AS-AP Viettel Group, VN 4766 2855 11135 767 KIXS-AS-KR Korea Telecom, KR 9829 2813 1497 543 BSNL-NIB National Internet Backbone, IN 45899 2658 1636 109 VNPT-AS-VN VNPT Corp, VN 9394 2541 4907 31 CTTNET China TieTong Telecommunications 17974 2260 946 70 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2240 8699 26 CMNET-GD Guangdong Mobile Communication 4755 2115 433 206 TATACOMM-AS TATA Communications formerl 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 6327 3435 1324 82 SHAW - Shaw Communications Inc., CA 22773 3261 2968 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 11492 2691 252 436 CABLEONE - CABLE ONE, INC., US 16509 2247 4790 767 AMAZON-02 - Amazon.com, Inc., US 18566 2167 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2124 2640 485 CHARTER-NET-HKY-NC - Charter Communicat 30036 2016 344 147 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16625 2013 1037 1447 AKAMAI-AS - Akamai Technologies, Inc., 209 1993 5085 603 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 7018 1761 20206 1278 ATT-INTERNET4 - AT&T Services, Inc., US 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 12479 4657 1611 123 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 2847 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2541 622 1886 AKAMAI-ASN1, US 12389 2041 1891 731 ROSTELECOM-AS, RU 34984 1999 334 511 TELLCOM-AS, TR 9121 1855 1692 19 TTNET, TR 13188 1605 100 39 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1214 544 14 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 8151 5178 3349 606 Uninet S.A. de C.V., MX 10620 3515 535 387 Telmex Colombia S.A., CO 11830 2656 369 78 Instituto Costarricense de Electricidad 6503 1667 444 64 Axtel, S.A.B. de C.V., MX 7303 1507 1026 188 Telecom Argentina S.A., AR 28573 1088 2245 185 CLARO S.A., BR 3816 1020 508 129 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 931 377 31 Telefonica del Peru S.A.A., PE 11172 929 126 85 Alestra, S. de R.L. de C.V., MX 18881 913 1078 30 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 1170 396 48 LINKdotNET-AS, EG 37611 888 107 9 Afrihost, ZA 36903 778 391 137 MT-MPLS, MA 36992 742 1411 40 ETISALAT-MISR, EG 24835 635 818 18 RAYA-AS, EG 8452 617 1730 18 TE-AS TE-AS, EG 37492 473 470 57 ORANGE-, TN 29571 458 68 12 ORANGE-COTE-IVOIRE, CI 37342 386 32 1 MOVITEL, MZ 23889 377 231 15 MauritiusTelecom, MU 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 8151 5178 3349 606 Uninet S.A. de C.V., MX 4538 4694 4192 74 ERX-CERNET-BKB China Education and Rese 12479 4657 1611 123 UNI2-AS, ES 7545 4383 467 464 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 10620 3515 535 387 Telmex Colombia S.A., CO 6327 3435 1324 82 SHAW - Shaw Communications Inc., CA 22773 3261 2968 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 7552 2979 1153 84 VIETEL-AS-AP Viettel Group, VN 4766 2855 11135 767 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 4538 4694 4620 ERX-CERNET-BKB China Education and Research Net 12479 4657 4534 UNI2-AS, ES 7545 4383 3919 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3435 3353 SHAW - Shaw Communications Inc., CA 10620 3515 3128 Telmex Colombia S.A., CO 22773 3261 3112 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 2979 2895 VIETEL-AS-AP Viettel Group, VN 8551 2847 2803 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11830 2656 2578 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 64514 PRIVATE 5.42.231.0/24 35753 ITC ITC AS number, SA 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 64500 DOCUMENT 45.43.56.0/24 135391 AOFEI-HK AOFEI DATA INTERNATIO 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 4200015017 PRIVATE 47.74.136.0/24 45102 CNNIC-ALIBABA-CN-NET-AP Alibab 4200015017 PRIVATE 47.74.161.0/24 45102 CNNIC-ALIBABA-CN-NET-AP Alibab 4200015017 PRIVATE 47.74.203.0/24 45102 CNNIC-ALIBABA-CN-NET-AP Alibab 4200015017 PRIVATE 47.88.147.0/24 45102 CNNIC-ALIBABA-CN-NET-AP Alibab 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 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.66.224.0/19 209 CENTURYLINK-US-LEGACY-QWEST - Qwest Communicati 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.136.0/24 37500 -Reserved AS-, ZZ 41.76.138.0/24 37500 -Reserved AS-, ZZ 41.76.139.0/24 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 43.251.84.0/22 133676 PNPL-AS Precious netcom pvt ltd, IN 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:14 /9:11 /10:36 /11:99 /12:291 /13:570 /14:1096 /15:1897 /16:13374 /17:7928 /18:13775 /19:25377 /20:39399 /21:45804 /22:87910 /23:71570 /24:398231 /25:797 /26:605 /27:625 /28:35 /29:20 /30:19 /31:4 /32:54 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3399 4657 UNI2-AS, ES 6327 3222 3435 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 22773 2522 3261 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2309 2847 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 2110 2691 CABLEONE - CABLE ONE, INC., US 18566 2061 2167 MEGAPATH5-US - MegaPath Corporation, US 11830 2004 2656 Instituto Costarricense de Electricidad y Telec 30036 1768 2016 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1593 3515 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1612 2:846 4:18 5:2825 6:41 7:1 8:1125 12:1872 13:208 14:1787 15:31 16:3 17:189 18:54 20:50 23:2465 24:2223 25:2 27:2473 31:2037 32:86 35:27 36:509 37:2777 38:1483 39:246 40:122 41:3155 42:695 43:1967 44:122 45:5227 46:3094 47:205 49:1331 50:1054 51:318 52:1076 54:365 55:1 56:12 57:39 58:1626 59:992 60:400 61:2118 62:1873 63:1788 64:5045 65:2199 66:4683 67:2471 68:1162 69:3288 70:1154 71:580 72:2135 74:2716 75:420 76:460 77:1635 78:1698 79:2149 80:1545 81:1381 82:1067 83:786 84:1069 85:1987 86:566 87:1358 88:920 89:2361 90:214 91:6435 92:1258 93:2382 94:2387 95:2918 96:778 97:355 98:936 99:133 100:86 101:1237 102:172 103:18311 104:3566 105:216 106:768 107:1796 108:696 109:3170 110:1626 111:1792 112:1332 113:1298 114:1135 115:1654 116:1644 117:1896 118:2211 119:1678 120:1009 121:1057 122:2472 123:1766 124:1448 125:1922 128:1101 129:684 130:492 131:1609 132:729 133:195 134:1023 135:232 136:503 137:651 138:1930 139:660 140:476 141:734 142:803 143:1007 144:809 145:484 146:1211 147:727 148:1643 149:754 150:743 151:1095 152:816 153:321 154:1463 155:799 156:1256 157:795 158:655 159:1784 160:1277 161:804 162:2593 163:597 164:1074 165:1525 166:462 167:1307 168:3126 169:827 170:3828 171:492 172:1022 173:2001 174:929 175:771 176:2000 177:4051 178:2552 179:1247 180:2176 181:2412 182:2399 183:1239 184:1053 185:13899 186:3601 187:2376 188:2922 189:2045 190:8173 191:1352 192:9810 193:6092 194:4973 195:3984 196:2617 197:1608 198:5554 199:5900 200:7335 201:5040 202:10248 203:10268 204:4561 205:2870 206:3176 207:3199 208:3969 209:4009 210:3867 211:1983 212:3051 213:2813 214:1025 215:56 216:6037 217:2123 218:853 219:578 220:1817 221:992 222:973 223:1375 End of report

1 0

[Nanog] BGPMon RPKI Validation Failed (Code: 9)
by Michel Py 03 Aug '18

03 Aug '18

Hi Nanog, I received recently some of these messages, and I don't understand the logic of them. If there is no ROA found, the code should be 1, and the status unknown / not found. What is the logic behind getting a Validation failure if there is no ROA ? Please help RPKI n00b, Thanks. ==================================================================== RPKI Validation Failed (Code: 9) ==================================================================== Your prefix: 216.230.25.0/24: Prefix Description: TSI Semiconductors Update time: 2018-07-20 00:10 (UTC) Detected by #peers: 4 Detected prefix: 216.230.25.0/24 Announced by: AS14051 (Consolidated Communications, Inc.) Upstream AS: AS2914 (NTT America, Inc.) ASpath: 25291 2914 14051 Alert details: https://portal.bgpmon.net/alerts.php?details&alert_id=82315862 Mark as false alert: https://portal.bgpmon.net/fp.php?aid=82315862 RPKI Status: No ROA found TSI Disclaimer: This message and any files or text attached to it are intended only for the recipients named above and contain information that may be confidential or privileged. If you are not the intended recipient, you must not forward, copy, use or otherwise disclose this communication or the information contained herein. In the event you have received this message in error, please notify the sender immediately by replying to this message, and then delete all copies of it from your system. Thank you!...

3 3

Confirming source-routed multicast is dead on the public Internet
by Sean Donelan 03 Aug '18

03 Aug '18

Its tought to prove a negative. I'm extremely confident the answer is yes, public internet multicast is not viable. I did all the google searches, check all the usual CAIDA and ISP sites. IP Multicast is used on private enterprise networks, and some ISPs use it for some closed services. I got sent back with a random comment from a senior official saying "but I heard different." I bit my tongue, and said I would double (now quadruple) check. If any ISPs have working IP source-routed multicast on the public Internet that I missed, or what I got wrong. That's what content distribution networks (cdn's) are for instead.

17 24

Re: possible hawaii weather issue next week
by Scott Weeks 02 Aug '18

02 Aug '18

________________________________ If you have stuff in Hawaii, you might want to start thinking about your DR plan. Things can change a lot for the better in 7 days, but they can also get ugly fast. Best to prepare just in case... https://www.nhc.noaa.gov/refresh/graphics_ep5+shtml/204426.shtml?cone https://www.nhc.noaa.gov/refresh/graphics_ep5+shtml/204426.shtml?tswind120 M is >110MPH -------------------------------------------- --- radevita(a)mejeticks.com wrote: From: Robert DeVita <radevita(a)mejeticks.com> Especially with the main carrier Hotel being located next to the ocean. -------------------------------------------- I'm guessing you mean DR Fortress. Most everything is next to the ocean here. :) However, DRF is likely pretty well protected from storm surge from a hurricane. It's also pretty well protected from flying debris, which is the main worry, especially when the winds are in excess of 100MPH. However, other facilities will have trouble (electric, fuel, etc), thus my suggestion to dust off DR plans and test if you haven't. We're the closest to the Asia Pacific countries you can get and still be in a US state and, as well, a good timezone between west coast going home and Asia coming in, so there may be a lot of folks here for some of the big networks, which is why I sent out the note. scott

1 0

Re: Confirming source-routed multicast is dead on the public Internet
by Jakob Heitz (jheitz) 02 Aug '18

02 Aug '18

Hey, there's a better way. Split the movie into segments: Segment 1: Minute 1. Segment 2: Minute 2. Segment 3: Minutes 3,4. Segment 4: Minutes 5-8. Segment 5: Minutes 9-16. etc. Then send each segment in a loop. Each receiver receives every loop simultaneously. Each segment may start receiving part way through, but then it starts again. By the time a segment needs to play, it is completely received. A 128 minute movie needs 8 streams. While waiting for the first minute, you can play ads :) The shorter segments don't need to be sent for long: Receivers can stop receiving the short segments once they have received one loop of it. When no receiver is receiving a loop, you can stop sending it. Regards, Jakob. -----Original Message----- Date: Wed, 1 Aug 2018 19:24:21 +0300 From: Saku Ytti <saku(a)ytti.fi> Imagine someone like youtube or netflix would like to use multicast, instead of caches. They'd need to start new multicast stream for every content with small delay (to get more viewers on given stream), how much delay would consumer tolerate before content starts? 1min? 5min? So every minute or every 5 minute new stream of movie would be sent, except it would need to be sent many times, for each bitrate supported.

2 4

possible hawaii weather issue next week
by Scott Weeks 02 Aug '18

02 Aug '18

If you have stuff in Hawaii, you might want to start thinking about your DR plan. Things can change a lot for the better in 7 days, but they can also get ugly fast. Best to prepare just in case... https://www.nhc.noaa.gov/refresh/graphics_ep5+shtml/204426.shtml?cone https://www.nhc.noaa.gov/refresh/graphics_ep5+shtml/204426.shtml?tswind120 M is >110MPH scott

2 1

SAFNOG-4/EANOG/tzNOG Registration Now Open!
by Mark Tinka 02 Aug '18

02 Aug '18

Hi all. Pleased to inform you that registration for the upcoming SAFNOG-4/EANOG/tzNOG meeting in Dar Es Salaam, 24th - 29th September, is now open. You may register at the URL below: http://www.safnog.org/ We look forward to seeing you there. Mark.

1 0

California fires: smart speakers and emergency alerts
by Sean Donelan 01 Aug '18

01 Aug '18

Has anyone heard if the smart speaker companies (Amazon Echo, Google Home) plan to include emergency alert capability? An estimate 10% of households own a smart speaker, and Gartner (well-known for its forecasting accuracy) predicts 75% of US households will have a smart speaker by 2020. Although most silicon valley tech nerds are still in the "invincible" years, were the california fires close enough to silicon valley that smart speaker developers might think an emergency could affect them. And an emergency alert capability in their smart speakers might be important?

30 54

Re: Confirming source-routed multicast is dead on the public Internet
by John Kristoff 01 Aug '18

01 Aug '18

On Tue, 31 Jul 2018 21:28:31 +0000 Sean Donelan <sean(a)donelan.com> wrote: > I did all the google searches, check all the usual CAIDA and ISP > sites. IP Multicast is used on private enterprise networks, and some > ISPs use it for some closed services. More anecdotal evidence. Probably the best place to know what is going on with multicast is on the mboned list (yea that still exists): <https://mailarchive.ietf.org/arch/browse/mboned/> Second best might be the Internet2 community where a number of institutions that have always had it might still have it turned on. Though there has been only one post in all of 2018 on their list if that tells you anything. There is almost no public multicast monitoring anymore. Practically all dead. You could poke around the I2 router proxies and see what is happening on some of the last of the remaining IP multicast-enabled Internet (hint, mostly noise from odd devices that have strayed outside the local institution): show multicast routes show pim join ... I keep hearing about some research project in the deep blue sea that uses it. You might find a small amount of it out there, but I'd bet overall its usage is teeny tiny and limited to a shrinking number of networks. Turned off interdomain multicast when I returned here in 2016. John

2 1

Re: Confirming source-routed multicast is dead on the public Internet
by John Kristoff 01 Aug '18

01 Aug '18

On Wed, 1 Aug 2018 15:45:44 +0000 Adam Davenport <adam(a)davenpro.com> wrote: > I can confirm that GTT does indeed filter IP sourced from 224.0.0.0/4 at its edge. Do you mean sent to 224/4 or literally anything with a source address of 224/4? For those that are or are considering filtering, you might also want to consider limiting IGMP at router interfaces. The only known use of IGMP past the local link I'm aware of was for mtrace tool, but allowing it can pose some danger in two forms. One is yet another DDoS reflection and amplification vector, another is a some router system and configuration disclosure. See the following for details: <https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p27-sargent.pdf> In experiments I ran in early parts of that work I found that Cogent did not forward IGMP messages through its network in my tests, but this may be due to the routing hardware/software they were using at the time rather than an explicit filtering policy. John

1 0