July 2018 - Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 20 Jul '18

20 Jul '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 21 Jul, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 706689 Prefixes after maximum aggregation (per Origin AS): 271490 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 339522 Total ASes present in the Internet Routing Table: 61277 Prefixes per ASN: 11.53 Origin-only ASes present in the Internet Routing Table: 52941 Origin ASes announcing only one prefix: 23079 Transit ASes present in the Internet Routing Table: 8336 Transit-only ASes present in the Internet Routing Table: 278 Average AS path length visible in the Internet Routing Table: 4.1 Max AS path length visible: 34 Max AS path prepend of ASN ( 30873) 32 Prefixes from unregistered ASNs in the Routing Table: 56 Number of instances of unregistered ASNs: 59 Number of 32-bit ASNs allocated by the RIRs: 23343 Number of 32-bit ASNs visible in the Routing Table: 18822 Prefixes from 32-bit ASNs in the Routing Table: 78370 Number of bogon 32-bit ASNs visible in the Routing Table: 27 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 289 Number of addresses announced to Internet: 2856751939 Equivalent to 170 /8s, 70 /16s and 147 /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: 235774 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 192804 Total APNIC prefixes after maximum aggregation: 54910 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 191212 Unique aggregates announced from the APNIC address blocks: 78530 APNIC Region origin ASes present in the Internet Routing Table: 8959 APNIC Prefixes per ASN: 21.34 APNIC Region origin ASes announcing only one prefix: 2522 APNIC Region transit ASes present in the Internet Routing Table: 1335 Average APNIC Region AS path length visible: 4.1 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3919 Number of APNIC addresses announced to Internet: 767822850 Equivalent to 45 /8s, 196 /16s and 12 /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: 209991 Total ARIN prefixes after maximum aggregation: 99923 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 210273 Unique aggregates announced from the ARIN address blocks: 99476 ARIN Region origin ASes present in the Internet Routing Table: 18190 ARIN Prefixes per ASN: 11.56 ARIN Region origin ASes announcing only one prefix: 6725 ARIN Region transit ASes present in the Internet Routing Table: 1805 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: 2386 Number of ARIN addresses announced to Internet: 1102400672 Equivalent to 65 /8s, 181 /16s and 76 /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: 193597 Total RIPE prefixes after maximum aggregation: 92449 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 189728 Unique aggregates announced from the RIPE address blocks: 112597 RIPE Region origin ASes present in the Internet Routing Table: 25313 RIPE Prefixes per ASN: 7.50 RIPE Region origin ASes announcing only one prefix: 11414 RIPE Region transit ASes present in the Internet Routing Table: 3490 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: 7187 Number of RIPE addresses announced to Internet: 714018432 Equivalent to 42 /8s, 143 /16s and 14 /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: 91068 Total LACNIC prefixes after maximum aggregation: 20101 LACNIC Deaggregation factor: 4.53 Prefixes being announced from the LACNIC address blocks: 92487 Unique aggregates announced from the LACNIC address blocks: 40809 LACNIC Region origin ASes present in the Internet Routing Table: 7333 LACNIC Prefixes per ASN: 12.61 LACNIC Region origin ASes announcing only one prefix: 2029 LACNIC Region transit ASes present in the Internet Routing Table: 1382 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 25 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4880 Number of LACNIC addresses announced to Internet: 172083488 Equivalent to 10 /8s, 65 /16s and 201 /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: 19172 Total AfriNIC prefixes after maximum aggregation: 4062 AfriNIC Deaggregation factor: 4.72 Prefixes being announced from the AfriNIC address blocks: 22700 Unique aggregates announced from the AfriNIC address blocks: 7856 AfriNIC Region origin ASes present in the Internet Routing Table: 1175 AfriNIC Prefixes per ASN: 19.32 AfriNIC Region origin ASes announcing only one prefix: 389 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: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 450 Number of AfriNIC addresses announced to Internet: 99974400 Equivalent to 5 /8s, 245 /16s and 125 /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 4690 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4348 467 459 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 2948 1153 83 VIETEL-AS-AP Viettel Group, VN 4766 2853 11130 764 KIXS-AS-KR Korea Telecom, KR 9829 2813 1497 543 BSNL-NIB National Internet Backbone, IN 45899 2658 1633 114 VNPT-AS-VN VNPT Corp, VN 9394 2542 4907 31 CTTNET China TieTong Telecommunications 17974 2260 930 71 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2236 8699 26 CMNET-GD Guangdong Mobile Communication 4755 2115 417 205 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 3431 1324 84 SHAW - Shaw Communications Inc., CA 22773 3271 2968 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 11492 2550 247 462 CABLEONE - CABLE ONE, INC., US 16509 2248 4727 753 AMAZON-02 - Amazon.com, Inc., US 18566 2168 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2114 2591 478 CHARTER-NET-HKY-NC - Charter Communicat 30036 2004 343 154 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1994 5070 605 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16625 1966 988 1404 AKAMAI-AS - Akamai Technologies, Inc., 7018 1751 20201 1270 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 4543 1609 122 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 20940 2547 623 1880 AKAMAI-ASN1, US 8551 2536 377 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2014 1877 708 ROSTELECOM-AS, RU 34984 2009 335 499 TELLCOM-AS, TR 9121 1879 1692 19 TTNET, TR 13188 1604 100 43 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1210 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 5007 3299 589 Uninet S.A. de C.V., MX 10620 3560 541 256 Telmex Colombia S.A., CO 11830 2655 369 78 Instituto Costarricense de Electricidad 6503 1669 443 62 Axtel, S.A.B. de C.V., MX 7303 1507 1026 188 Telecom Argentina S.A., AR 28573 1035 2248 184 CLARO S.A., BR 3816 1023 508 129 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 936 377 31 Telefonica del Peru S.A.A., PE 11172 929 127 86 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 1172 396 48 LINKdotNET-AS, EG 37611 884 107 9 Afrihost, ZA 36903 778 391 137 MT-MPLS, MA 36992 744 1411 40 ETISALAT-MISR, EG 8452 635 1730 18 TE-AS TE-AS, EG 24835 635 818 18 RAYA-AS, EG 37492 472 470 57 ORANGE-, TN 29571 457 68 11 ORANGE-COTE-IVOIRE, CI 37342 386 32 1 MOVITEL, MZ 23889 378 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 5007 3299 589 Uninet S.A. de C.V., MX 4538 4690 4192 74 ERX-CERNET-BKB China Education and Rese 12479 4543 1609 122 UNI2-AS, ES 7545 4348 467 459 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 10620 3560 541 256 Telmex Colombia S.A., CO 6327 3431 1324 84 SHAW - Shaw Communications Inc., CA 22773 3271 2968 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 7552 2948 1153 83 VIETEL-AS-AP Viettel Group, VN 4766 2853 11130 764 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 4690 4616 ERX-CERNET-BKB China Education and Research Net 12479 4543 4421 UNI2-AS, ES 7545 4348 3889 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3431 3347 SHAW - Shaw Communications Inc., CA 10620 3560 3304 Telmex Colombia S.A., CO 22773 3271 3123 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 2948 2865 VIETEL-AS-AP Viettel Group, VN 11830 2655 2577 Instituto Costarricense de Electricidad y Telec 45899 2658 2544 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 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 65537 DOCUMENT 62.162.120.0/24 6821 MT-AS-OWN bul. Orce Nikolov bb 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:1095 /15:1894 /16:13348 /17:7939 /18:13760 /19:25331 /20:39376 /21:45625 /22:87778 /23:71260 /24:396097 /25:802 /26:607 /27:624 /28:35 /29:20 /30:19 /31:6 /32:52 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3291 4543 UNI2-AS, ES 6327 3217 3431 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 22773 2535 3271 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2061 2168 MEGAPATH5-US - MegaPath Corporation, US 11830 2004 2655 Instituto Costarricense de Electricidad y Telec 8551 1998 2536 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 1972 2550 CABLEONE - CABLE ONE, INC., US 30036 1756 2004 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1613 3560 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:1615 2:834 4:18 5:2854 6:40 7:1 8:1125 12:1869 13:206 14:1765 15:29 16:3 17:188 18:54 20:50 23:2460 24:2224 25:2 27:2475 31:2041 32:92 35:27 36:508 37:2821 38:1482 39:248 40:121 41:3152 42:690 43:1959 44:121 45:5012 46:3094 47:203 49:1332 50:1056 51:317 52:1070 54:372 55:4 56:12 57:39 58:1618 59:993 60:401 61:2102 62:1876 63:1790 64:5026 65:2196 66:4673 67:2423 68:1170 69:3266 70:1157 71:580 72:2137 74:2704 75:422 76:459 77:1545 78:1712 79:1817 80:1535 81:1384 82:1075 83:790 84:1077 85:2012 86:561 87:1351 88:929 89:2350 90:216 91:6433 92:1251 93:2383 94:2395 95:2917 96:781 97:359 98:935 99:133 100:85 101:1231 102:146 103:18174 104:3567 105:213 106:738 107:1789 108:694 109:3180 110:1624 111:1773 112:1309 113:1292 114:1133 115:1660 116:1631 117:1763 118:2209 119:1658 120:1003 121:1063 122:2462 123:1757 124:1448 125:1912 128:1082 129:674 130:489 131:1636 132:697 133:195 134:1020 135:225 136:502 137:651 138:1942 139:661 140:468 141:730 142:803 143:1022 144:801 145:486 146:1197 147:725 148:1644 149:756 150:749 151:1096 152:794 153:320 154:1429 155:789 156:1136 157:799 158:654 159:1779 160:1262 161:785 162:2574 163:604 164:1071 165:1521 166:449 167:1302 168:3113 169:821 170:3805 171:488 172:994 173:1983 174:905 175:769 176:1994 177:4067 178:2540 179:1235 180:2169 181:2358 182:2405 183:1238 184:1034 185:13807 186:3564 187:2439 188:2843 189:2045 190:8131 191:1309 192:9789 193:6062 194:4898 195:3977 196:2643 197:1588 198:5554 199:5906 200:7312 201:4988 202:10236 203:10256 204:4583 205:2893 206:3164 207:3179 208:3984 209:3997 210:3888 211:1984 212:3023 213:2784 214:1046 215:57 216:6035 217:2134 218:859 219:577 220:1785 221:985 222:971 223:1352 End of report

1 0

Re: Proving Gig Speed
by Scott Weeks 20 Jul '18

20 Jul '18

--- mark.tinka(a)seacom.mu wrote: From: Mark Tinka <mark.tinka(a)seacom.mu> On 19/Jul/18 22:43, Scott Weeks wrote: > I know we're talking about Africa and other less well > connected countries, but good luck with that in the > Pacific, which covers about 1/3 of the planet. > > https://oceanexplorer.noaa.gov/facts/pacific-size.html Yeah, things and people tend to work better if hosted on land... ----------------------------------------------------- I believe I'm on land here... ;) And there're a lot of islands with lots of people out here. 1/3 of the planet and all. :) ------------------------------------------------------ What I meant to say is a lot of folks get connectivity through satellite. 500msec plus and jitter to spare. Further it's expensive and all the 'busy' sites cost a lot of money to download the stuff folks on this list don't blink an eye at and you can't turn it off. I believe satellite coverage serves a lot of the planet's population. scott

2 1

NTT now treats RPKI ROAs as IRR route(6)-objects
by Job Snijders 20 Jul '18

20 Jul '18

Dear NANOG, [ TL:DR - From now on, NTT / AS 2914 allows customers to either register their announcements in the IRR, or as RPKI ROAs. This is a convenience service for relevant regions of the world where IRR is not the norm but RPKI is commonly available. Previously NTT only accepted IRR and ARIN-WHOIS. I hope competitors and partners will use this approach too! ] As most of you know, the Resource Public Key Infrastructure (RPKI) is a modern reimagination of the good ole' IRR system we have come to love and hate. The main advantage of the RPKI is that a consumer of the data can cryptographically verify whether it was the actual owner of the IP prefix that created a so-called "RPKI ROA". (more reading: https://en.wikipedia.org/wiki/Resource_Public_Key_Infrastructure) Given that RPKI ROAs are somewhat equivalent to IRR route-objects, but more reliable in terms of authoritativeness, NTT now has an automated nightly process that converts RPKI information into IRR format so that our toolchain can consume the data as if it were just another IRR source. Using RPKI ROAs as if they are IRR route(6)-objects is a transitional step towards increased security in the routing ecosystem. We are not the first to explore this method (see post-scriptum), but I think we are the first to republish elements from RPKI ROAs via a publicly accessible IRRd instance queryable with the RADB IRRd protocol. This means that anyone that points their bgpq3 or peval programs at rr.ntt.net can leverage this method without having to update anything else in the pipeline. An example can be inspected here: job@eng0 ~$ whois -h rr.ntt.net 193.0.6.139 [Querying rr.ntt.net] [rr.ntt.net] route: 193.0.0.0/21 descr: RIPE-NCC origin: AS3333 mnt-by: RIPE-NCC-MNT changed: unread(a)ripe.net 20000101 source: RIPE remarks: **************************** remarks: * THIS OBJECT IS MODIFIED remarks: * Please note that all data that is generally regarded as personal remarks: * data has been removed from this object. remarks: * To view the original object, please query the RIPE Database at: remarks: * http://www.ripe.net/whois remarks: **************************** route: 193.0.0.0/21 descr: RPKI ROA for 193.0.0.0/21 remarks: This route object represents routing data retrieved from the RPKI remarks: The original data can be found here: https://rpki.gin.ntt.net/r/AS3333/193.0.0.0/21 remarks: This route object is the result of an automated RPKI-to-IRR conversion process. remarks: maxLength 21 origin: AS3333 mnt-by: MAINT-JOB changed: job(a)ntt.net 20180718 source: RPKI # Trust Anchor: RIPE NCC RPKI Root job@eng0 ~$ The first object is an actual IRR "route:" object from the RIPE NCC operated IRR, the second object is a representation of the RPKI ROA in RPSL format published via rr.ntt.net. In general we can state that RPKI data is very good quality data, however please keep in mind that it may not be /correct/ data. In this context "Good Quality" means that it cannot easily be forged or tampered with by adversaries (but of course that doesn't protect the legitimate owner against making misconfigurations). Just like with IRR route(6)-objects, owners may input the wrong origin ASN in this type of object or configure the wrong MaxLength. NTT operates a "RPKI Cache Validator" at https://rpki.gin.ntt.net/ Everyone is free to inspect and click around in this webinterface. Instead of https://rpki.gin.ntt.net/, there also is a command line interface available via BGPMon's whois service: job@vurt ~$ whois -h whois.bgpmon.com 193.0.0.0/21 % This is the BGPmon.net whois Service % You can use this whois gateway to retrieve information % about an IP adress or prefix % We support both IPv4 and IPv6 address. % % For more information visit: % https://portal.bgpmon.net/bgpmonapi.php Prefix: 193.0.0.0/21 Prefix description: RIPE-NCC Country code: NL Origin AS: 3333 Origin AS Name: Reseaux IP Europeens Network Coordination Centre (RIPE NCC) RPKI status: ROA validation successful First seen: 2011-10-19 Last seen: 2018-07-19 Seen by #peers: 77 Notice in the above output the "ROA validation successful". Nota bene: the fact that NTT uses RPKI ROA information in the prefix filter generation process - does _not_ mean that NTT does "RPKI Origin Validation" for BGP updates (yet). RPKI Origin Validation is an additional security layer that we hope to deploy in the not too distant future. Using RPKI ROAs in this way is an important step forward in this process. Kind regards, Job Snijders Post scriptum on prior work: Dragon Research Labs implemented the idea in 2015: https://github.com/dragonresearch/rpki.net/blob/master/potpourri/roa-to-irr… RIPE NCC's RPKI Validator added RPSL export functionality in 2015: https://mailman.nanog.org/pipermail/nanog/2015-May/075185.html Arouteserver added native support for this method in October 2017. https://github.com/pierky/arouteserver/issues/19

2 1

Re: Proving Gig Speed
by Scott Weeks 19 Jul '18

19 Jul '18

--- mark.tinka(a)seacom.mu wrote: From: Mark Tinka <mark.tinka(a)seacom.mu> On 19/Jul/18 22:43, Scott Weeks wrote: > I know we're talking about Africa and other less well > connected countries, but good luck with that in the > Pacific, which covers about 1/3 of the planet. > > https://oceanexplorer.noaa.gov/facts/pacific-size.html Yeah, things and people tend to work better if hosted on land... ----------------------------------------------------- I believe I'm on land here... ;) And there're a lot of islands with lots of people out here. 1/3 of the planet and all. :) scott

1 0

Re: Proving Gig Speed
by Scott Weeks 19 Jul '18

19 Jul '18

--- mark.tinka(a)seacom.mu wrote: From: Mark Tinka <mark.tinka(a)seacom.mu> On 18/Jul/18 16:58, K. Scott Helms wrote: > ... What's really interesting is how gaming is changing > and within the next few years I do expect a lot of games > to move into the remote rendering world. You need to > have <=30 ms of latency to sustain 1080p gaming and > obviously jitter and packet loss are also problematic. > The traffic is also pretty impressive with spikes of > over 50 mbps down and sustained averages over 21 mbps. And what we need is for them to ensure all these remote rendering farms are evenly distributed around the world to ensure that 30ms peak latency is achievable. ----------------------------------------------- I know we're talking about Africa and other less well connected countries, but good luck with that in the Pacific, which covers about 1/3 of the planet. https://oceanexplorer.noaa.gov/facts/pacific-size.html scott

2 1

Re: deploying RPKI based Origin Validation
by Joshua Vijsma / True 19 Jul '18

19 Jul '18

Hi all, Just wanted to share our (AS15703, True B.V.) experience as a hosting provider with enabling RPKI invalid filtering (invalid == reject). We've secured (most of) our routes since 2014 with ROAs but last Tuesday we have deployed filters which reject RPKI invalid routes. We have had two tickets regarding users in one certain RPKI invalid prefix not being able to reach our network, but those people quickly understood that this wasn't our problem but a problem with their hosting partner. They took it up with their hosting partner and it was fixed within a day. Overal, I would certainly recommend filtering RPKI invalids (and create ROAs for your prefixes!!) to prevent hijacks. -- Met vriendelijke groet / Best regards, Joshua Vijsma > On 13 Jul 2018, at 14:00, nanog-request(a)nanog.org wrote: > > > ------------------------------ > > Message: 2 > Date: Thu, 12 Jul 2018 17:50:29 +0000 > From: Job Snijders <job(a)ntt.net> > To: nanog(a)nanog.org > Subject: deploying RPKI based Origin Validation > Message-ID: <20180712175029.GC3037(a)vurt.meerval.net> > Content-Type: text/plain; charset=us-ascii > > Hi all, > > I wanted to share with you that a ton of activity is taking place in the > Dutch networker community to deploy RPKI based BGP Origin Validation. > The mantra is "invalid == reject" on all EBGP sessions. > > What's of note here is that we're now seeing the first commercial ISPs > doing Origin Validation. This is a significant step forward compared to > what we observed so far (it seemed OV was mostly limited to academic > institutions & toy networks). But six months ago Amsio (https://www.amsio.com/en/) > made the jump, and today Fusix deployed (https://fusix.nl/deploying-rpki/) > > We've also seen an uptake of Origin Validation at Internet Exchange > route servers: AMS-IX and FranceIX have already deployed. I've read that > RPKI OV is under consideration at a number of other exchanges. > > Other cool news is that Cloudflare launched a Certificate Transparency > initiative to help keep everyone honest. Announcement at: > https://twitter.com/grittygrease/status/1017224762542587907 > Certificate Transparency is a fascinating tool, really a necessity to > build confidence in any PKI systems. > > Anyone here working to deploy RPKI based Origin Validation in their > network and reject invalid announcements? Anything of note to share? > > Kind regards, > > Job

1 0

Centurylink/Level3 Plans
by James Breeden 19 Jul '18

19 Jul '18

Does anyone know what the plans or even watercooler chat is concerning Centurylink (AS209) and Level3 (AS3356) integration, direct peering, or continuing separation? We are looking at a IP Transit deal involving one or both networks and while I'd love to have transit routes from both, I don't want to design to be shot in the foot later on either if they are talking about soon-to-be integrated or something. TIA... James W. Breeden Managing Partner [logo_transparent_background] Arenal Group: Arenal Consulting Group | Acilis Telecom | Pines Media PO Box 1063 | Smithville, TX 78957 Email: james(a)arenalgroup.co<mailto:james@arenalgroup.co> | office 512.360.0000 | cell 512.304.0745 | www.arenalgroup.co<http://www.arenalgroup.co>

4 3

Quickstart Guide to IRR/RPSL
by Kenneth Finnegan 19 Jul '18

19 Jul '18

Greetings, As part of setting up a new Internet Exchange in Fremont, California, we've been investigating prefix filtering on the route servers based on IRR. Unfortunately, we were not satisfied with any of the existing documentation available online as far as taking a network engineer from "zero" to "just enough IRR to post our prefixes for filtering". Lacking this documentation, it was rather unreasonable for us to turn on filtering and drop most of our peer's prefixes without a relevant whitepaper to point them to to get started. So, we wrote our own guide: http://fcix.net/whitepaper/2018/07/14/intro-to-irr-rpsl.html I thought others on this list would find our whitepaper interesting, and/or have valuable feedback based on their experience applying IRR themselves. -- Kenneth Finnegan Technical Director Fremont Cabal Internet Exchange http://fcix.net/

2 3

Implementation plan and dates for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.
by Nathalie Trenaman 19 Jul '18

19 Jul '18

Dear colleagues, In February 2018, the RIPE Database Working Group reached consensus on NWI-5 - creating out of region ROUTE(6) objects in the RIPE Database. We will soon be making changes to the way out-of-region objects are handled in the RIPE Database. It's important that database users are aware of these changes and what they mean: 1. The RIPE Routing Registry will no longer support the creation of out-of-region ROUTE(6) and AUT-NUM objects 2. Existing out-of-region objects will have their "source:” attribute changed to "RIPE-NONAUTH” 3. The creation of ROUTE(6) objects will no longer need authorisation from the ASN holder We will implement these changes in the Release Candidate environment on Thursday, 2 August and go to full production on Tuesday, 4 September. Our implementation plan can be found at: https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-imple… <https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-imple…> The RIPE Database Working Group chairs also wrote a RIPE Labs article that describes the background of NWI-5: https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec… <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec…> <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec… <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec…>> Please contact ripe-dbm(a)ripe.net <mailto:ripe-dbm@ripe.net> if you still have questions after reading the implementation plan. Best regards, Nathalie Trenaman Product Manager RIPE NCC

1 0

Re: Proving Gig Speed
by nanog-isp＠mail.com 19 Jul '18

19 Jul '18

No, but you can connect iPhones with gigabit Ethernet over copper. Jared >-----Original Message----- >From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Mike >Hammett >Cc: NANOG list >Subject: Re: Proving Gig Speed > > I don't think iPhones have SFP cages. > > > > >----- >Mike Hammett >Intelligent Computing Solutions >http://www.ics-il.com > >Midwest-IX >http://www.midwest-ix.com

1 0