November 2020 - Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 27 Nov '20

27 Nov '20

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 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 28 Nov, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 831835 Prefixes after maximum aggregation (per Origin AS): 318703 Deaggregation factor: 2.61 Unique aggregates announced (without unneeded subnets): 398430 Total ASes present in the Internet Routing Table: 69978 Prefixes per ASN: 11.89 Origin-only ASes present in the Internet Routing Table: 60160 Origin ASes announcing only one prefix: 24897 Transit ASes present in the Internet Routing Table: 9818 Transit-only ASes present in the Internet Routing Table: 298 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 35 Max AS path prepend of ASN ( 45582) 27 Prefixes from unregistered ASNs in the Routing Table: 931 Number of instances of unregistered ASNs: 932 Number of 32-bit ASNs allocated by the RIRs: 34274 Number of 32-bit ASNs visible in the Routing Table: 28363 Prefixes from 32-bit ASNs in the Routing Table: 129598 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 467 Number of addresses announced to Internet: 2864993408 Equivalent to 170 /8s, 196 /16s and 84 /24s Percentage of available address space announced: 77.4 Percentage of allocated address space announced: 77.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 282996 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 217118 Total APNIC prefixes after maximum aggregation: 63778 APNIC Deaggregation factor: 3.40 Prefixes being announced from the APNIC address blocks: 213143 Unique aggregates announced from the APNIC address blocks: 87157 APNIC Region origin ASes present in the Internet Routing Table: 11054 APNIC Prefixes per ASN: 19.28 APNIC Region origin ASes announcing only one prefix: 3133 APNIC Region transit ASes present in the Internet Routing Table: 1602 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6175 Number of APNIC addresses announced to Internet: 778321920 Equivalent to 46 /8s, 100 /16s and 64 /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-143673 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: 240547 Total ARIN prefixes after maximum aggregation: 111324 ARIN Deaggregation factor: 2.16 Prefixes being announced from the ARIN address blocks: 240762 Unique aggregates announced from the ARIN address blocks: 115400 ARIN Region origin ASes present in the Internet Routing Table: 18670 ARIN Prefixes per ASN: 12.90 ARIN Region origin ASes announcing only one prefix: 6787 ARIN Region transit ASes present in the Internet Routing Table: 1915 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3574 Number of ARIN addresses announced to Internet: 1093758208 Equivalent to 65 /8s, 49 /16s and 109 /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-401308 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, 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: 237330 Total RIPE prefixes after maximum aggregation: 111915 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 233264 Unique aggregates announced from the RIPE address blocks: 137417 RIPE Region origin ASes present in the Internet Routing Table: 27545 RIPE Prefixes per ASN: 8.47 RIPE Region origin ASes announcing only one prefix: 11875 RIPE Region transit ASes present in the Internet Routing Table: 3892 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9691 Number of RIPE addresses announced to Internet: 709602432 Equivalent to 42 /8s, 75 /16s and 172 /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-213403 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: 111432 Total LACNIC prefixes after maximum aggregation: 26186 LACNIC Deaggregation factor: 4.26 Prefixes being announced from the LACNIC address blocks: 112508 Unique aggregates announced from the LACNIC address blocks: 47806 LACNIC Region origin ASes present in the Internet Routing Table: 10597 LACNIC Prefixes per ASN: 10.62 LACNIC Region origin ASes announcing only one prefix: 2620 LACNIC Region transit ASes present in the Internet Routing Table: 1960 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 33 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8190 Number of LACNIC addresses announced to Internet: 174209792 Equivalent to 10 /8s, 98 /16s and 59 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 24475 Total AfriNIC prefixes after maximum aggregation: 4764 AfriNIC Deaggregation factor: 5.14 Prefixes being announced from the AfriNIC address blocks: 31691 Unique aggregates announced from the AfriNIC address blocks: 10240 AfriNIC Region origin ASes present in the Internet Routing Table: 1411 AfriNIC Prefixes per ASN: 22.46 AfriNIC Region origin ASes announcing only one prefix: 481 AfriNIC Region transit ASes present in the Internet Routing Table: 286 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 733 Number of AfriNIC addresses announced to Internet: 108658688 Equivalent to 6 /8s, 122 /16s and 0 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 7545 5737 777 656 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4751 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3564 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3264 1896 55 VNPT-AS-VN VNPT Corp, VN 7713 3219 936 519 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2545 9044 57 CMNET-GD Guangdong Mobile Communication 4766 2350 11102 553 KIXS-AS-KR Korea Telecom, KR 9498 2293 466 231 BBIL-AP BHARTI Airtel Ltd., IN 4755 2136 441 189 TATACOMM-AS TATA Communications formerl 9394 2058 4913 16 CTTNET China TieTong Telecommunications 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 11492 4727 314 753 CABLEONE, US 16509 4477 9054 2065 AMAZON-02, US 7155 4019 264 32 VIASAT-SP-BACKBONE, US 22773 3735 2994 197 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3355 1323 82 SHAW, CA 16625 3167 1651 2256 AKAMAI-AS, US 209 2493 5059 509 CENTURYLINK-US-LEGACY-QWEST, US 30036 2487 369 91 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2314 2982 1626 FRONTIER-FRTR, US 20115 2162 2899 504 CHARTER-20115, 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 47331 6235 860 3603 TTNET, TR 12479 6214 1667 141 UNI2-AS, ES 39891 3459 195 22 ALJAWWALSTC-AS, SA 20940 3316 3347 202 AKAMAI-ASN1, EU 8551 3243 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2869 2281 890 ROSTELECOM-AS, RU 9009 2203 227 1195 M247, GB 34984 2171 354 576 TELLCOM-AS, TR 13188 1610 100 31 TRIOLAN, UA 58224 1408 850 528 TCI, IR 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 7812 3435 600 Uninet S.A. de C.V., MX 10620 3386 526 563 Telmex Colombia S.A., CO 11830 2558 369 63 Instituto Costarricense de Electricidad 13999 1503 426 404 Mega Cable, S.A. de C.V., MX 7303 1474 948 269 Telecom Argentina S.A., AR 6503 1468 311 475 Axtel, S.A.B. de C.V., MX 28573 1360 2258 225 CLARO S.A., BR 6147 1150 379 39 Telefonica del Peru S.A.A., PE 3816 1111 536 151 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 1007 213 421 Techtel LMDS Comunicaciones Interactiva 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 1568 393 22 LINKdotNET-AS, EG 24835 1286 476 26 RAYA-AS, EG 36992 1218 1529 131 ETISALAT-MISR, EG 36903 950 496 96 MT-MPLS, MA 29571 707 68 12 ORANGE-COTE-IVOIRE, CI 6713 532 1863 34 IAM-AS, MA 37342 476 32 1 MOVITEL, MZ 36935 456 522 40 Vodafone-, EG 15399 451 46 16 WANANCHI-, KE 36914 373 82 3 KENET-AS, KE 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 7812 3435 600 Uninet S.A. de C.V., MX 47331 6235 860 3603 TTNET, TR 12479 6214 1667 141 UNI2-AS, ES 7545 5737 777 656 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4751 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4727 314 753 CABLEONE, US 16509 4477 9054 2065 AMAZON-02, US 7155 4019 264 32 VIASAT-SP-BACKBONE, US 22773 3735 2994 197 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3564 1330 21 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 6214 6073 UNI2-AS, ES 7545 5737 5081 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4751 4678 ERX-CERNET-BKB China Education and Research Net 7155 4019 3987 VIASAT-SP-BACKBONE, US 11492 4727 3974 CABLEONE, US 7552 3564 3543 VIETEL-AS-AP Viettel Group, VN 22773 3735 3538 ASN-CXA-ALL-CCI-22773-RDC, US 39891 3459 3437 ALJAWWALSTC-AS, SA 6327 3355 3273 SHAW, CA 45899 3264 3209 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 Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 393489 UNALLOCATED 12.7.109.0/24 7018 ATT-INTERNET4, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.142.80.0/24 Origin: 397294 UNASSIGNED Transit: 398559 TUNBROKER, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 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:8 /9:13 /10:40 /11:101 /12:292 /13:577 /14:1177 /15:1934 /16:13469 /17:8256 /18:14066 /19:25626 /20:41465 /21:50331 /22:103077 /23:87401 /24:482763 /25:1239 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 47331 5490 6235 TTNET, TR 12479 5187 6214 UNI2-AS, ES 11492 3814 4727 CABLEONE, US 6327 3151 3355 SHAW, CA 7155 3108 4019 VIASAT-SP-BACKBONE, US 22773 2864 3735 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3459 ALJAWWALSTC-AS, SA 8551 2703 3243 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 8151 2596 7812 Uninet S.A. de C.V., MX 30036 2227 2487 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1877 2:1189 3:35 4:19 5:3410 6:53 8:1489 9:1 11:1 12:1763 13:349 14:2399 15:72 16:12 17:306 18:92 20:113 23:4078 24:2358 25:3 27:2344 31:2149 32:111 34:1 35:35 36:1108 37:3468 38:1992 39:467 40:151 41:3804 42:625 43:2141 44:229 45:14561 46:3614 47:321 49:1576 50:1677 51:90 52:1127 54:215 55:766 56:7 57:54 58:1689 59:1139 60:820 61:2329 62:2190 63:2009 64:5223 65:2378 66:5118 67:2927 68:1170 69:4110 70:1400 71:684 72:3067 74:2545 75:1457 76:688 77:2041 78:3133 79:2495 80:1874 81:1702 82:1369 83:1078 84:1267 85:3131 86:620 87:1790 88:2398 89:2865 90:393 91:7160 92:1635 93:2541 94:2896 95:4199 96:1247 97:340 98:956 99:976 100:89 101:1048 102:1169 103:24910 104:3641 105:387 106:775 107:2160 108:690 109:3726 110:1992 111:2347 112:1654 113:1539 114:1510 115:1854 116:1857 117:2096 118:2268 119:1811 120:935 121:1034 122:2278 123:2121 124:1627 125:2139 128:1362 129:1237 130:766 131:2012 132:756 133:312 134:1387 135:329 136:676 137:896 138:2305 139:1150 140:768 141:1141 142:1022 143:1236 144:1212 145:330 146:1361 147:1255 148:2134 149:1256 150:755 151:1194 152:1589 153:443 154:2287 155:1254 156:1380 157:1127 158:903 159:2035 160:2009 161:1070 162:3190 163:913 164:1421 165:1324 166:593 167:1714 168:3615 169:633 170:4359 171:742 172:2002 173:2934 174:964 175:1063 176:2889 177:4413 178:2785 179:1853 180:2281 181:2558 182:3160 183:1502 184:2436 185:17443 186:4011 187:2971 188:3297 189:2672 190:9044 191:1360 192:10597 193:7843 194:6361 195:4556 196:3093 197:2212 198:6079 199:5908 200:7297 201:5100 202:10552 203:10160 204:4654 205:3102 206:3284 207:3308 208:4007 209:4554 210:4213 211:2081 212:3557 213:3184 214:1189 215:60 216:6145 217:2493 218:864 219:627 220:2059 221:927 222:970 223:1678 End of report

1 0

Fw: [lacnog] Update on LACNIC's IRR: Near-Real-Time Mirroring Now Available
by Job Snijders 23 Nov '20

23 Nov '20

FYI ----- Forwarded message from "Carlos M. Martinez" <carlosm3011(a)gmail.com> ----- Date: Mon, 23 Nov 2020 16:18:44 -0300 From: "Carlos M. Martinez" <carlosm3011(a)gmail.com> To: Latin America and Caribbean Region Network Operators Group <lacnog(a)lacnic.net> Subject: [lacnog] Update on LACNIC's IRR: Near-Real-Time Mirroring Now Available Colleagues, We are pleased to inform that LACNIC's Internet Routing Registry (IRR) which came into production earlier this year now supports Near-Real-Time Mirroring (NRTM) using IRRd Version 4. The mirroring policy is an open policy and those organizations that wish to mirror the information contained in LACNIC's IRR can do so. To set up a mirror, you will need the following information: NOC: noc(a)lacnic.net Dump: ftp://irr.lacnic.net/lacnic.db.gz / http://irr.lacnic.net/lacnic.db.gz CURRENT SERIAL: ftp://irr.lacnic.net/LACNIC.CURRENTSERIAL http://irr.lacnic.net/LACNIC.CURRENTSERIAL NRTM Host: irr.lacnic.net NRTM Port:43 When LACNIC enables NRTM in the coming days, other IRRs such as RADB and NTT will begin mirroring the LACNIC source. We would also like to thank the DashCare team (https://dashcare.nl/) Job Snijders (NTT) and the RADB team for their support. Should you have any questions or doubts, please don't hesitate to contact us at tecnologia(a)lacnic.net/ The LACNIC Team _______________________________________________ LACNOG mailing list LACNOG(a)lacnic.net https://mail.lacnic.net/mailman/listinfo/lacnog Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog ----- End forwarded message -----

2 1

A letter from the CEO
by 6x7 Networks - Lady Benjamin, CEO 23 Nov '20

23 Nov '20

** A letter from the CEO of 6x7: 6x7 Networks and Communications Authority of Kenya announce type approval to import 8tbps/second internet routers. ------------------------------------------------------------ Hi, Lady Benjamin from 6x7 here, and I'm proud to share with you an update on me and the company. Through our adjunct division, 6x7 just received type approval from the Kenyan government to import core routers capable of over 8tbps (8 terrabits per second). This will enable us to enter the Kenyan IP transit and transport markets, and service both datacenter and soon office buildings and eventually residences with high speed, safe, secure global fiber connectivity. The market in Kenya is severely impacted now due to limited fiber availability, and 6x7 will leverage it's undersea connections to bring more wholesale bandwidth into the area, creating the economy by which we expect to grow. ** Thanks for reading, I'll be doing a regular set of these newsletters, and if you like them or want to reach out, please contact us at kar(a)6by7.net! ------------------------------------------------------------ -LB Ms. Lady Benjamin Cannon, ASCE. Find Out More (https://www.issuewire.com/6x7-networks-and-communications-authority-of-keny…) ============================================================ ** Facebook (http://www.facebook.com) ** Twitter (http://www.twitter.com/) ** Link (http://www.instagram.com/) ** Website (http://mailchimp.com) Copyright © 2020 6x7 Networks, LLC, All rights reserved. You are receiving this email because you opted in via our website. Our mailing address is: 6x7 Networks, LLC 44 montgomery st suite 2310 San Francisco, CA 94104 USA Want to change how you receive these emails? You can ** update your preferences (https://6x7networks.us19.list-manage.com/profile?u=6fbc79e84e5db9abf437b960…) or ** unsubscribe from this list (https://6x7networks.us19.list-manage.com/unsubscribe?u=6fbc79e84e5db9abf437…) . Email Marketing Powered by Mailchimp http://www.mailchimp.com/email-referral/?utm_source=freemium_newsletter&utm…

23 35

Re: Cable Company Hotspots
by Rob Seastrom 23 Nov '20

23 Nov '20

On Nov 22, 2020, at 12:42, Lady Benjamin PD Cannon <ben(a)6by7.net> wrote: > > Rod, that’s exactly how they are delivering it. Unclear wether it’s over a separately provisioned bandwidth channel, or wether it shares the aggregate capacity of the HFC. It shares the aggregate bandwidth of the HFC but not your contracted bandwidth. Itmight be possible, but its extremely unlikely, to dedicate downstream or particularly upstream DOCSIS channels for this, and if you’re running docsis 3.1 “channel” takes on a rather different shade of meaning anyway. This is done with “service flows” which are part of the docsis spec. They’re more like CAR with an ACL than DSCP. Your cable modem already has at least four service flows defined in its profile: one each for upstream and downstream, cablemodem management and contracted-bandwidth commodity internet. If there is a built in phone jack (NANOG would call this an ATA, but the cablelabs term for it is an MTA or eMTA) then add a couple of more flows to it for the voip. There could be still more; uses are up to your imagination. I haven’t seen better than 10-20m service flows for guest wifi... Shared vs dedicated wifi radio for guest would be dependent on the CPE. I believe they are mostly shared, but my information is dated at this point and radios have gotten stupid cheap in the meantime. Likewise, backhaul technology is implementation dependent; L2TP is what I’ve generally seen, not GRE, but again that info is five years out of date at this point. So in short, assuming minimal interference and good wifi config (which may be a lot to ask in some environments) someone running speedtest on the guest wifi should have almost no effect on your contracted network performance, modulo any timing effects of the docsis channel transmission time slot allocator. HTH, -r Sent from my iPad

3 2

Career Opportunities In Network Engineering — Watch it on NANOG TV 👉
by NANOG News 21 Nov '20

21 Nov '20

*Career Opportunities In Network Engineering * “Be curious and passionate; this is a lifelong journey.” — Selva Srinivasan, Microsoft Big thanks to all who attended our first NANOG U Webinar last week! And of course, to each of our guest speakers — it was a great conversation, all around. Didn't get to attend? No worries! Watch the full webinar this weekend, on NANOG TV. Watch Now <https://nanog.org/news-stories/nanog-tv/nanog-u/> *Save the date — 2021 Webinars * *January 22, 2021 — DNS Fundamentals* 11am - 1pm PST / 2pm - 4pm EST *Speaker:* Eddy Winstead, Internet Systems Consortium (ISC) *February 26, 2021 — BGP Fundamentals* 11am - 1pm PST / 2pm - 4pm EST *Speaker:* Aaron Atac, Akamai Technologies Learn More <https://www.nanog.org/meetings/nanog-u-webinars/> *Partner with us to empower and inspire* A NANOG Outreach partnership provides your organization a way to directly support the communities who need access to our tools and resources most, and the opportunity to inspire and connect with the next generation of networking professionals. In turn, we’ll publicly recognize your contributions as a partner in meaningful ways that resonate with the communities we serve. Interested in collaborating with us? Connect with Shawn Winstead <swinstead(a)nanog.org>, NANOG's Business Development Specialist, to start a conversation + learn more.

2 1

ARIN RDAP-related changes (was: ARIN Software and System Updates)
by John Curran 21 Nov '20

21 Nov '20

NANOGers - ARIN updated some of its software this morning, and I’d like to call to your attention the variety of changes related to RDAP. In particular, if you utilize ARIN’s RDAP bootstrap server, please pay careful attention regarding upcoming deprecation of the prior URL used for access. Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] ARIN Software and System Updates Date: 21 November 2020 at 7:00:03 AM HST To: "arin-announce(a)arin.net<mailto:arin-announce@arin.net>" <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> ARIN recently made updates to its software and systems, including ARIN Online. Full release notes are included at the end of this message. ARIN systems are operating normally. If you have questions, comments, or issues, please submit an Ask ARIN ticket using your ARIN Online account, or contact the Registration Services Help Desk by phone Monday through Friday, 7:00 AM to 7:00 PM ET at +1.703.227.0660. Release Notes We completed a number of infrastructure improvements and bug fixes, including the following updates. ARIN Online Updates - Updated financial and billing functions in ARIN Online. - Fixed zonegen timing issue that caused slow publishing of zones for ERX snippets received from other RIRs. ARIN Whois Updates The URL for Registration Data Access Protocol (RDAP) bootstrap queries has changed to https://rdap-bootstrap.arin.net/bootstrap. If you have queries that use our RDAP bootstrap server, please update your links. Note that the current URL, https://rdap.arin.net/bootstrap, will be supported for 90 days, and that support will end on 18 February, 2021. Please use this 90-day period to migrate to the new URL. After 90 days, the old URL (https://rdap.arin.net/bootstrap) will no longer be supported. RDAP Bootstrap Server Software Updates The new RDAP bootstrap server version 2.0.1 is available on github at https://github.com/arineng/rdap_bootstrap_server/releases/tag/2.0.1 and the README file is available at https://github.com/arineng/rdap_bootstrap_server/blob/2.0.1/README.md This RDAP server software version includes the following changes: - Updated IANA bootstrap files to the latest version - Provided a built-in scheduler to configure downloading of IANA bootstrap files at certain intervals (fulfilling a request for this functionality) - Added ability to build a Docker image of the software - Added ability to run as a Spring Boot application - Upgraded to build against Java 11 or higher Notice of Upcoming nicinfo Release To comply with the RDAP bootstrap URL update, our RDAP client, nicinfo, will be updated soon. We suggest that users update to nicinfo version 1.5.0 when it is released. More information about nicinfo is available on github at https://github.com/arineng/nicinfo – if you are logged in to github, you can select the Watch icon to be notified of new releases. _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net<mailto:ARIN-announce@arin.net>). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues.

1 0

Disney+ Geolocation (again)
by Seth Mattinen 21 Nov '20

21 Nov '20

People can't watch Disney+. Looked at old emails, read them. Checked every geolocation site for my netblocks (which return ok). Emailed to netadmin(a)disneystreaming.com They responded with "We do not service these requests via this email". Now what? Anyone have a secret contact that can actually help? ~Seth

12 24

Neteng field laptop/tablet
by Brandon Martin 20 Nov '20

20 Nov '20

Sorry if this is perhaps a bit OT... Can anyone recommend a smallish (10-13" display), relatively lightweight tablet or laptop (or convertible) with a native PCIe multi-gig Ethernet port, ideally both 10GBASE-T + 2.5GBASE-T (and 5GBASE-T perhaps). I'm not seeing a lot out there, and it's hard to search for multi-gig in a laptop at this point. Failing that, I'm sure someone has a recommendation for a similar device with native PCIe 1000BASE-T + a thunderbolt or similar port I can hang a dongle off of? Ruggedness is useful but not essential. 6-8 hour practical battery life is important but almost implied these days. Must be able to nicely run Linux (distro is unimportant). -- Brandon Martin

2 1

inspecting RPKI data: console.rpki-client.org
by Job Snijders 20 Nov '20

20 Nov '20

Dear all, I'd like to introduce another tool to inspect RPKI data... the rpki-client console! Comes with an authentic 90s look & feel :-) The Frontpage - http://console.rpki-client.org/ ----------------------------------------------- On the front page you can see stdout + stderr of the most recent rpki-client run. The log shows which publication points were contacted and prints any issues encountered with specific RPKI files. Those of us publishing RPKI data should keep an eye out not to show up in this type of log with warnings or errors. For example: rpki-client: cc.rg.net/rpki/RGnet-cc/1opByAd8x8R2F-SzstgaYzVXK8Q.mft: mft expired on Oct 12 17:58:45 2020 GMT However, the above line might be the result of some kind of experiment someone is conducting :-) The RPKI distributed database currently is more than 120,000 (!) certificate/roa/manifest files, and only a handful of files have some kind of completeness or expiration date issue. Good job everyone! :-) The ASN specific pages - http://console.rpki-client.org/AS2914.html ------------------------------------------------------------------- You can substitute the 'AS2914' portion in the URL for any ASN to see which .roa files reference the given ASN. Another example, here one can see all ROAs which authorize AS 8283 as origin: https://console.rpki-client.org/AS8283.html If you encounter a HTTP 404 error, no ROAs reference the ASN. On the 'per ASN page' you can search click the .roa files on the left side to inspect the ROA. Each object in the RPKI has a unique Subject Key Identifier (SKI). An example of a SKI is this hexadecimal identifier '06:96:B3:F7:CC:AD:55:45:A5:3A:64:32:31:2B:7F:E1:2B:7A:15:22' which maps to a filename like 'rpki.apnic.net/member_repository/A91A4C60/B526FF74D84111E9A4521413C4F9AE02/…' Yeah... compared to DNS names mapping to IPv6 addresses, in the RPKI neither the path name nor the SKI are easy to remember :-) The console can show that .roa file in human readable format, just append .html: http://console.rpki-client.org/rpki.apnic.net/member_repository/A91A4C60/B5… Every object in the RPKI is subordinate to another object (all objects are signed by a parent certificate, except the Trust Anchors). The parent is identified by the Authority Key Identifier (AKI). So one object's AKI is another object's SKI! If you click the AKI, the console brings you to the parent object, from where you can continue to explore other objects related to parent. Certificates point to Manifests, and .mft files contain the 'directory indexes' of the RPKI: http://console.rpki-client.org/rpki.apnic.net/member_repository/A91A4C60/B5… >From the manifest overview you can jump to the parent, click the referenced .roa, .cer or .crl files. All directories on the webserver are 'open', except the root. This allows you to explore this RPKI cache by browsing through the filesystem directly, example: http://console.rpki-client.org/rpki.apnic.net/member_repository/ Final notes ----------- The rpki-client console provides a view on *validated* RPKI data. First rpki-client runs and prunes bad files, then all HTML is generated. The console provides a view on the data as used in production Internet routers. Please note: the console's rendering is delayed by a bit over an hour compared to the real thing. Another entry point, you can use your browser's 'find on page' function to search for anything in all of it on this humongous page: http://console.rpki-client.org/roas.html The RPKI is very intricate collection of references, I hope this console offers another useful perspective on the tree-like structures. Enjoy! Kind regards, Job

3 3

Ingress filtering on transits, peers, and IX ports
by Brian Knight 20 Nov '20

20 Nov '20

We recently received an email notice from a group of security researchers who are looking at the feasibility of attacks using spoofed traffic. Their methodology, in broad strokes, was to send traffic to our DNS servers with a source IP that looked like it came from our network. Their attacks were successful, and they included a summary of what they found. So this message has started an internal conversation on what traffic we should be filtering and how. This security test was not about BCP 38 for ingress traffic from our customers, nor was it about BGP ingress filtering. This tested our ingress filtering from the rest of the Internet. It seems to me like we should be filtering traffic with spoofed IPs on our transit, IX, and peering links. I have done this filtering in the enterprise world extensively, and it's very helpful to keep out bad traffic. BCP 84 also discusses ingress filtering for SP's briefly and seems to advocate for it. We have about 15 IP blocks allocated to us. With a network as small as ours, I chose to go with a static ACL approach to start the conversation. I crafted a static ACL, blocking all ingress traffic sourced from any of our assigned IP ranges. I made sure to include: * Permit entries for P-t-P WAN subnets on peering links * Permit entries for IP assignments to customers running multi-homed BGP * The "permit ipv4 any any" at the end :) The questions I wanted to ask the SP community are: * What traffic filtering do you do on your transits, on IX ports, and your direct peering links? * How is it accomplished? Through static ACL or some flavor of uRPF? * If you use static ACLs, what is the administrative overhead like? What makes it easy or difficult to update? * How did you test your filters when they were implemented? Thanks a lot, -Brian

23 48