- Test - lists.nanog.org

are underwater routers a thing?
by Michael Thomas 16 Apr '22

16 Apr '22

I was reading an article in the Economist about a new fiber route down the Red Sea from Israel and wondered if there were any branches off of those lines and where the routers were for them. The route kind of made it look like it was completely at sea, but it would kind of make sense to leave them at sea if you could put a router there. Mike

13 13

Copper Termination Blocks
by Mike Hammett 15 Apr '22

15 Apr '22

I know I'm discussing what some consider ancient technology. I counter that it meets or exceeds the needs of many, many people. Currently, we use 100-pr Telect-style termination blocks. They don't offer much in terms of ease of use for testing and don't organize well on a 19" or 23" rack. I was recommended to look at Krone blocks. They look just great. Easy to break into for testing with their "look both ways" plug as well as their preterminated blocks looked much easier to rack-mount. Well, Krone was bought by ADC. ADC was bought by Tyco Electronics. TE was bought by Commscope. Commscope discontinued everything I found interesting with no replacements. Some of the stuff is on eBay (even NIB), some not. Any recommendations for places to get old telco blocks, testers, mounts, etc.? Any recommendations for alternatives that are easier to source? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

9 12

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 15 Apr '22

15 Apr '22

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 16 Apr, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 896801 Prefixes after maximum aggregation (per Origin AS): 337333 Deaggregation factor: 2.66 Unique aggregates announced (without unneeded subnets): 429950 Total ASes present in the Internet Routing Table: 73005 Prefixes per ASN: 12.28 Origin-only ASes present in the Internet Routing Table: 62657 Origin ASes announcing only one prefix: 25706 Transit ASes present in the Internet Routing Table: 10348 Transit-only ASes present in the Internet Routing Table: 372 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 65 Max AS path prepend of ASN (267602) 58 Prefixes from unregistered ASNs in the Routing Table: 1047 Number of instances of unregistered ASNs: 1053 Number of 32-bit ASNs allocated by the RIRs: 39109 Number of 32-bit ASNs visible in the Routing Table: 32469 Prefixes from 32-bit ASNs in the Routing Table: 152871 Number of bogon 32-bit ASNs visible in the Routing Table: 28 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 668 Number of addresses announced to Internet: 3067665792 Equivalent to 182 /8s, 216 /16s and 221 /24s Percentage of available address space announced: 82.9 Percentage of allocated address space announced: 82.9 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: 303952 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 235767 Total APNIC prefixes after maximum aggregation: 66532 APNIC Deaggregation factor: 3.54 Prefixes being announced from the APNIC address blocks: 230569 Unique aggregates announced from the APNIC address blocks: 94543 APNIC Region origin ASes present in the Internet Routing Table: 12548 APNIC Prefixes per ASN: 18.37 APNIC Region origin ASes announcing only one prefix: 3569 APNIC Region transit ASes present in the Internet Routing Table: 1725 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7750 Number of APNIC addresses announced to Internet: 774131456 Equivalent to 46 /8s, 36 /16s and 79 /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-151865 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: 260766 Total ARIN prefixes after maximum aggregation: 119680 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 260793 Unique aggregates announced from the ARIN address blocks: 124356 ARIN Region origin ASes present in the Internet Routing Table: 18991 ARIN Prefixes per ASN: 13.73 ARIN Region origin ASes announcing only one prefix: 6886 ARIN Region transit ASes present in the Internet Routing Table: 1949 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4439 Number of ARIN addresses announced to Internet: 1295176960 Equivalent to 77 /8s, 50 /16s and 213 /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: 256871 Total RIPE prefixes after maximum aggregation: 117354 RIPE Deaggregation factor: 2.19 Prefixes being announced from the RIPE address blocks: 254279 Unique aggregates announced from the RIPE address blocks: 150463 RIPE Region origin ASes present in the Internet Routing Table: 28122 RIPE Prefixes per ASN: 9.04 RIPE Region origin ASes announcing only one prefix: 12044 RIPE Region transit ASes present in the Internet Routing Table: 3978 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10674 Number of RIPE addresses announced to Internet: 714141824 Equivalent to 42 /8s, 144 /16s and 240 /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: 114644 Total LACNIC prefixes after maximum aggregation: 27585 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 114546 Unique aggregates announced from the LACNIC address blocks: 48315 LACNIC Region origin ASes present in the Internet Routing Table: 10952 LACNIC Prefixes per ASN: 10.46 LACNIC Region origin ASes announcing only one prefix: 2641 LACNIC Region transit ASes present in the Internet Routing Table: 2199 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 65 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8647 Number of LACNIC addresses announced to Internet: 176352512 Equivalent to 10 /8s, 130 /16s and 237 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 27706 Total AfriNIC prefixes after maximum aggregation: 5457 AfriNIC Deaggregation factor: 5.08 Prefixes being announced from the AfriNIC address blocks: 35946 Unique aggregates announced from the AfriNIC address blocks: 11730 AfriNIC Region origin ASes present in the Internet Routing Table: 1627 AfriNIC Prefixes per ASN: 22.09 AfriNIC Region origin ASes announcing only one prefix: 566 AfriNIC Region transit ASes present in the Internet Routing Table: 331 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 34 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 959 Number of AfriNIC addresses announced to Internet: 107402240 Equivalent to 6 /8s, 102 /16s and 212 /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 9808 9229 8884 44 CHINAMOBILE-CN China Mobile Communicati 7545 5911 789 699 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4722 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3607 1330 19 VIETEL-AS-AP Viettel Group, VN 7713 3500 1038 51 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3426 1880 56 VNPT-AS-VN VNPT Corp, VN 4766 2497 11121 601 KIXS-AS-KR Korea Telecom, KR 9498 2395 491 238 BBIL-AP BHARTI Airtel Ltd., IN 45090 2165 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 4755 2115 429 197 TATACOMM-AS TATA Communications formerl Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 6216 10270 2693 AMAZON-02, US 11492 4473 297 692 CABLEONE, US 22773 3937 3076 365 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3900 264 31 VIASAT-SP-BACKBONE, US 16625 3621 1856 2555 AKAMAI-AS, US 6327 3431 1318 62 SHAW, CA 749 2882 50780 2138 DNIC-AS-00749, US 30036 2616 374 118 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2521 4962 423 CENTURYLINK-US-LEGACY-QWEST, US 20115 2255 3042 494 CHARTER-20115, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6823 1730 149 UNI2-AS, ES 9121 6719 1692 17 TTNET, TR 8551 4009 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3928 3360 201 AKAMAI-ASN1, NL 39891 3751 216 33 ALJAWWALSTC-AS, SA 12389 2954 2274 909 ROSTELECOM-AS, RU 6849 2762 355 21 UKRTELNET, UA 9009 2463 245 1275 M247, GB 34984 2236 357 633 TELLCOM-AS, TR 47331 2084 328 1595 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10546 3392 559 Uninet S.A. de C.V., MX 10620 3466 518 753 Telmex Colombia S.A., CO 11830 2430 369 63 Instituto Costarricense de Electricidad 13999 1735 294 473 Mega Cable, S.A. de C.V., MX 6503 1452 354 523 Axtel, S.A.B. de C.V., MX 28573 1397 2333 253 CLARO S.A., BR 3816 1255 667 147 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1084 369 21 Telefonica del Peru S.A.A., PE 11664 1009 193 449 Techtel LMDS Comunicaciones Interactiva 11172 960 133 63 Alestra, S. de R.L. de C.V., MX Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1645 393 21 LINKdotNET-AS, EG 24835 1473 523 33 RAYA-AS, EG 36992 1314 1519 263 ETISALAT-MISR, EG 36903 1199 545 114 MT-MPLS, MA 29571 902 65 59 ORANGE-COTE-IVOIRE, CI 36935 771 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 520 51 35 WANANCHI-, KE 37342 468 32 1 MOVITEL, MZ 23889 424 232 16 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10546 3392 559 Uninet S.A. de C.V., MX 9808 9229 8884 44 CHINAMOBILE-CN China Mobile Communicati 12479 6823 1730 149 UNI2-AS, ES 9121 6719 1692 17 TTNET, TR 16509 6216 10270 2693 AMAZON-02, US 7545 5911 789 699 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4722 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4473 297 692 CABLEONE, US 8551 4009 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 22773 3937 3076 365 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9229 9185 CHINAMOBILE-CN China Mobile Communications Grou 9121 6719 6702 TTNET, TR 12479 6823 6674 UNI2-AS, ES 7545 5911 5212 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4722 4647 ERX-CERNET-BKB China Education and Research Net 8551 4009 3970 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3900 3869 VIASAT-SP-BACKBONE, US 11492 4473 3781 CABLEONE, US 20940 3928 3727 AKAMAI-ASN1, NL 39891 3751 3718 ALJAWWALSTC-AS, SA Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 19397 UNALLOCATED 8.5.244.0/24 3257 GTT-BACKBONE GTT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 19397 UNALLOCATED 8.15.12.0/24 7843 TWC-7843-BB, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW 41.57.124.0/23 Origin: 37442 UNASSIGNED 41.57.124.0/23 Transit: 37204 TELONE, ZW 41.57.124.0/24 Origin: 37442 UNASSIGNED 41.57.124.0/24 Transit: 37204 TELONE, ZW Complete listing at https://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:40 /11:100 /12:303 /13:590 /14:1209 /15:2058 /16:13532 /17:8247 /18:13900 /19:25181 /20:43713 /21:52350 /22:108483 /23:95912 /24:530324 /25:830 /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 9121 5874 6719 TTNET, TR 12479 5801 6823 UNI2-AS, ES 8151 4204 10546 Uninet S.A. de C.V., MX 8551 3475 4009 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3379 4473 CABLEONE, US 6327 3243 3431 SHAW, CA 39891 3067 3751 ALJAWWALSTC-AS, SA 7155 2990 3900 VIASAT-SP-BACKBONE, US 22773 2936 3937 ASN-CXA-ALL-CCI-22773-RDC, US 6849 2624 2762 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1941 2:1035 3:154 4:7 5:3800 6:103 7:5 8:1561 9:1 11:172 12:1708 13:293 14:2388 15:192 16:45 17:381 18:156 20:194 21:4 22:188 23:5618 24:2294 25:4 27:2593 29:19 31:2423 32:96 34:1 35:74 36:1755 37:4414 38:2776 39:731 40:153 41:3944 42:1073 43:2183 44:289 45:16088 46:4135 47:337 49:1675 50:1934 51:100 52:1410 53:1 54:363 55:708 56:8 57:58 58:1804 59:1203 60:957 61:2267 62:2487 63:1957 64:5511 65:2303 66:4854 67:2976 68:1181 69:4156 70:1339 71:658 72:3051 74:2666 75:1388 76:589 77:2168 78:3902 79:3113 80:1984 81:1750 82:1483 83:1201 84:1363 85:3649 86:708 87:1964 88:2726 89:3267 90:524 91:7621 92:1989 93:2595 94:3480 95:4775 96:1298 97:348 98:988 99:739 100:74 101:1040 102:2028 103:29058 104:4371 105:466 106:857 107:2540 108:830 109:4228 110:2071 111:3306 112:2031 113:1530 114:1488 115:1960 116:1909 117:2539 118:2328 119:1866 120:1698 121:1066 122:2567 123:2125 124:1593 125:2116 128:1222 129:1225 130:967 131:2055 132:768 133:373 134:1930 135:289 136:883 137:874 138:2441 139:1495 140:858 141:1400 142:1296 143:1474 144:1244 145:342 146:1803 147:1498 148:2226 149:1667 150:862 151:1083 152:1844 153:458 154:3538 155:1440 156:1874 157:1222 158:1033 159:2085 160:2467 161:1318 162:3454 163:1250 164:1630 165:1609 166:708 167:1712 168:3803 169:708 170:4460 171:830 172:3142 173:3093 174:1021 175:1127 176:3516 177:4641 178:3417 179:2018 180:2284 181:2951 182:3243 183:1953 184:2385 185:19471 186:4376 187:3654 188:3879 189:3189 190:8887 191:1321 192:10993 193:8603 194:6961 195:4953 196:2952 197:2399 198:6041 199:6040 200:7505 201:5684 202:10498 203:10035 204:4566 205:3382 206:3769 207:3410 208:4060 209:4674 210:4265 211:2453 212:4018 213:3420 214:1159 215:67 216:6446 217:2671 218:1272 219:572 220:1946 221:979 222:843 223:2150 End of report

1 0

FYI - ARIN submission in response to FCC 22-90 on Secure Internet Routing
by John Curran 15 Apr '22

15 Apr '22

NANOGers - As noted earlier, the FCC is in the midst of a consultation right now regarding vulnerabilities threatening the security and integrity of the Border Gateway Protocol (BGP). Please note that ARIN did file comments on this docket, and they may found online here in our government engagement section of the ARIN website - https://www.arin.net/about/relations/governance/documents/ Best wishes, /John John Curran President and CEO American Registry for Internet Numbers On 4 Apr 2022, at 9:59 PM, John Curran <jcurran(a)arin.net<mailto:jcurran@arin.net>> wrote: Along these lines, I’d like to remind everyone of a fairly important consultation that Andrew Hadenfeldt posted here last month <https://mailman.nanog.org/pipermail/nanog/2022-March/218365.html> – https://www.federalregister.gov/documents/2022/03/11/2022-05121/secure-inte… https://www.fcc.gov/document/fcc-launches-inquiry-internet-routing-vulnerab… (FCC) seeks comment on vulnerabilities threatening the security and integrity of the Border Gateway Protocol (BGP), which is central to the Internet's global routing system, its impact on the transmission of data from email, e-commerce, and bank transactions to interconnected Voice-over Internet Protocol (VoIP) and 9-1-1 calls, and how best to address them. Comments are due on or before April 11, 2022 If you have particular views on this important consultation, please take the time to file comments as appropriate.

1 0

Keep Ukraine Connected
by Markus 14 Apr '22

14 Apr '22

Hi NANOG, for those wanting to help - please see below and https://keepukraineconnected.org for an up-to-date list of needed equipment. Also: "Our contacts in Ukraine are desperately seeking professional grade fiber splicers. If you think you can help, either by donating equipment or financing a splicer, we’d appreciate an email." Forwarded with permission. ----- Forwarded message from Jan Zorz - Go6 <jan(a)go6.si> ----- Dear community, Sorry for another rather long email, but there are more and more requests from Ukraine operators coming in and we have no other way of getting specific equipment other than ask you - the community! Lately we got specific requests for fiber optics welding/splicing kits, specially from Kharkiv region that is/was under brutal attacks and lots of infrastructure is damaged. Let me copy/paste parts of messages that keep coming in so you get the feeling what people that are trying to keep the lights on in the fibers in Ukraine are dealing with: "In Kharkiv we provide continuous network access to other Ukrainian operators and providers. Our network suffers critical loads now because of shelling, and our co-workers repair it, sometimes, under the shots. We lack necessary equipment and tools and are not able to order. There is an urgent need for an optical fiber welding machine (as we have to work in difficult conditions). The amount of work is growing, but the maintenance is missing. We want to ask you, if it's possible, to give us at least one machine fujikura or fitel. We'll be glad to receive even a used one, the most important is it should work." "I also wanted to ask - Do you have, maybe some power backup systems? Also there are our partners in the city - internet provider, who have de-energized nodes for 2-3 thousand active subscribers, in which there is simply no electricity ..." "is there any possibility to send some more of the same optical fiber machines? and if it is possible two or three of the simplest optical reflectometers." We are getting more and more similar requests, so our question to community would be if anyone has any new/used/spare FO welding/splicing kit to donate to Ukraine friends to keep the Internet up&running and people connected? Same goes for UPS systems... We at GNA have secured one Fujikura 41S+ Fusion Splicer Kit with CT50 Cleaver - partially donated by one of their distributors, partially covered by money donations to GNA "Keep Ukraine Connected" initiative that many of you sent in last couple of weeks and we are very grateful for!!! First delivery of requested hardware to Ukraine is now being coordinated with with our colleagues from the Ukrainian Association of Rights Holders and Content Providers, the Ukrainian Internet Association (UAI) and Ukraine Ministry of Digital Transformation and will take place next week. We would like to secure more fiber optics repair equipment and UPS systems before next delivery, so please - if you are willing and can help - contact us at ukraine(a)nogalliance.org for hardware donation or donate some funds at below web page so we are able to purchase needed equipment and send it to Ukraine with next delivery. https://keepukraineconnected.org/ Thank you again, Jan Zorz on behalf of GNA/KUC initiative

1 0

ping across infomart ix, please
by Randy Bush 14 Apr '22

14 Apr '22

could someone who sees 198.180.152.0/24 (as 4128) over equinix infomart please ping 198.189.152.132 (and trace) and respond to me privately? thanks. rand

1 2

Hulu Contact?
by Jason Lamb 13 Apr '22

13 Apr '22

Hi all, We are having some issues with customers logging into Hulu on some recent IPv4 ranges we have added to our network. I think it is likely an IPv4 geolocation issue since the issue only appears on our newer IPv4 ranges. If anyone from Hulu NetOps is monitoring this, or if anyone has a Hulu NetOps contact they would share, please reach out to me. Thanks! Jason [PRTC] <http://www.prtcnet.org> Jason Lamb, Software Engineering/IT Supervisor Peoples Rural Telephone Cooperative <http://www.prtcnet.org> 259 Main St. S. | P.O. Box 159 | McKee, KY 40447 Main: (606) 287-7101 | Direct: (606) 287-5488 | Email: jason.lamb(a)prtc.org<mailto:jason.lamb@prtc.org> CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please notify the sender by return e-mail and delete it immediately. Do not print or disseminate its contents. The information in this message is intended for the listed recipients only. This message may contain information that is privileged, confidential or otherwise protected from disclosure to parties other than the listed recipients. If you are not one of the listed recipients, any disclosure, copying, distribution, or the taking of any action based on the contents of this message is prohibited.

2 1

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN74 Policy Forum
by Jacques Latour 13 Apr '22

13 Apr '22

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN74 Policy Forum In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN74 Public Forum being held as a hybrid meeting from 13-16 June 2022 in the Central European Time Zone (UTC +1). This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN73 Community Forum on Wednesday 09 March 2022. The presentations and transcripts are available at https://73.schedule.icann.org/meetings/qGWqRxCjbWHqdGLxN, https://73.schedule.icann.org/meetings/pm4Zz3yN3CgjoTXp2 and https://73.schedule.icann.org/meetings/qiGweLr2MS7zJwy8o. The DNSSEC Workshop Program Committee is developing a program for the upcoming meeting. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN74 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? * Do you still submit/accept DS records with Digest Type 1? * What is the best practice around key rollovers? * What about Algorithm rollovers? * Do you use and support DNSKEY Algorithms 13-16? * How often do you review your disaster recovery procedures? * Is there operational familiarity within your customer support teams? * What operational statistics have been gathered about DNSSEC? * Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: * Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) * What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? * What do you expect DNSSEC to do for you and what doesn't it do? * What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS, DNSSEC, routing and other topics that could impact the security and/or stability of the Internet. We are looking for presentations that cover implementation issues, challenges, opportunities and best practices for: * Emerging threats that could impact the security and/or stability of the Internet * DoH and DoT * RPKI (Resource Public Key Infrastructure) * BGP routing & secure implementations * MANRS ( Mutually Agreed Norms for Routing Security) * Browser security – DNS, DNSSEC, DoH * EMAIL & DNS related security – DMARC, DKIM, TLSA, etc… If you are interested in participating, please send a brief (1-3 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by COB Friday, 29 April 2022. Thank you, Kathy and Andrew On behalf of the DNSSEC Workshop Program Committee: Steve Crocker, Shinkuro Mark Elkins, DNS/ZACR Jacques Latour, .CA Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Fred Baker, ISC Dan York, Internet Society

1 0

Oahu HI undersea cable attack disrupted by federal agents
by Sean Donelan 13 Apr '22

13 Apr '22

https://www.hawaiinewsnow.com/2022/04/13/hsi-agents-honolulu-disrupted-cybe… Homeland Security Investigations says it was able to disrupt a cyberattack of a critical undersea cable, adding the hackers sought to target “infrastructure on Oahu.” The cable links Hawaii and Pacific to critical telecommunications, including internet and cell phones. HSI said its agents, based on a tip from their counterparts on the mainland, were able to disrupt last week a “significant breach involving a private company’s services” associated with the undersea cable.

1 0

IMPORTANT NOTICE - Retirement of ARIN Non-Authenticated IRR rescheduled for 4 April 2022
by John Curran 13 Apr '22

13 Apr '22

NANOGers - An important reminder – On 4 April 2022, ARIN's non-authenticated Internet Routing Registry (IRR) will be retired. Please review the attached notice for details, and do not hesitate to contact ARIN if you have any questions about this transition or need assistance. I ask that you do not hesitate to forward this notice to any others you know that are potentially unaware & impacted by this important transition. 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] UPDATE: Retirement of ARIN Non-Authenticated IRR rescheduled for 4 April 2022 Date: 28 January 2022 at 9:01:07 PM GMT+4 To: "arin-announce(a)arin.net<mailto:arin-announce@arin.net>" <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> This announcement is to inform you that the retirement of the ARIN non-authenticated Internet Routing Registry (IRR) has been rescheduled to 4 April 2022 at 12:00 PM EST. After this time, users will no longer be able to create, update, or delete records in the ARIN-NONAUTH database, and the ARIN-NONAUTH data stream will no longer be available in Near Real Time Mirroring (NRTM) or via FTP or Whois Port 43. This date change is being made in order to ensure that the first day after retirement does not fall on a Friday. The following information is from the initial announcement: ARIN has been engaged in a multi-year project to create and deploy a new and improved Internet Routing Registry (IRR). As a result of these efforts, ARIN now provides users with the ability to create, update, and delete objects in ARIN’s authenticated IRR database using ARIN Online or ARIN’s RESTful API. Unfortunately, use of ARIN’s previous non-authenticated email-based IRR service actually increased after ARIN released its authenticated IRR, in opposition to the outcome ARIN anticipated when improving its IRR. On 8 February 2021, ARIN held a consultation to solicit input on the retirement of ARIN’s non-authenticated email-based IRR service. This retirement was originally scheduled for 30 September 2021. Based on community input, the proposed date for the ARIN-NONAUTH retirement was delayed to 31 March 2022 to allow more transition time for users. We also notified by email Points of Contact (POCs) of organizations who have objects in the ARIN-NONAUTH database of the retirement date and offered them our assistance with the transition. If you have questions about this transition or need assistance, you can contact us by: • submitting an Ask ARIN ticket or chat with us using your ARIN Online account • emailing the Routing Security Team at routing.security(a)arin.net<mailto:routing.security@arin.net> • contacting the Registration Services Help Desk by phone Monday through Friday, 7:00 AM to 7:00 PM ET at +1.703.227.0660 Regards, Brad Gorman Senior Product Owner, Routing Security American Registry for Internet Numbers (ARIN)

21 62