- NANOG - lists.nanog.org

RIP Fred Baker
by Suresh Ramasubramanian 19 Jun '25

19 Jun '25

https://en.wikipedia.org/wiki/Fred_Baker_(engineer) End of an era --srs

5 4

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 13 Jun '25

13 Jun '25

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 UKNOF, 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 14 Jun, 2025 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 987315 Prefixes after maximum aggregation (per Origin AS): 381363 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 482560 Number of IPv4 prefixes with a valid ROA: 544429 Number of IPv4 prefixes with an invalid ROA: 1985 Number of IPv4 prefixes with no ROA: 440901 Total ASes present in the Internet Routing Table: 76982 Prefixes per ASN: 12.83 Origin-only ASes present in the Internet Routing Table: 65862 Origin ASes announcing only one prefix: 26875 Transit ASes present in the Internet Routing Table: 11120 Transit-only ASes present in the Internet Routing Table: 565 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 75 Max AS path prepend of ASN ( 7438) 64 Prefixes from unregistered ASNs in the Routing Table: 1137 Number of instances of unregistered ASNs: 1178 Number of 32-bit ASNs allocated by the RIRs: 46645 Number of 32-bit ASNs visible in the Routing Table: 38406 Prefixes from 32-bit ASNs in the Routing Table: 204489 Number of bogon 32-bit ASNs visible in the Routing Table: 110 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 436 Number of addresses announced to Internet: 3110769024 Equivalent to 185 /8s, 106 /16s and 145 /24s Percentage of available address space announced: 84.0 Percentage of allocated address space announced: 84.0 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 323428 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 259895 Total APNIC prefixes after maximum aggregation: 77917 APNIC Deaggregation factor: 3.34 Prefixes being announced from the APNIC address blocks: 251279 Unique aggregates announced from the APNIC address blocks: 104432 APNIC Region origin ASes present in the Internet Routing Table: 14661 APNIC Prefixes per ASN: 17.14 APNIC Region origin ASes announcing only one prefix: 4454 APNIC Region transit ASes present in the Internet Routing Table: 1965 Average APNIC Region AS path length visible: 5.4 Max APNIC Region AS path length visible: 39 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10163 Number of APNIC addresses announced to Internet: 749730560 Equivalent to 44 /8s, 175 /16s and 251 /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-155961 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: 290744 Total ARIN prefixes after maximum aggregation: 131511 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 292529 Unique aggregates announced from the ARIN address blocks: 139581 ARIN Region origin ASes present in the Internet Routing Table: 19241 ARIN Prefixes per ASN: 15.20 ARIN Region origin ASes announcing only one prefix: 7015 ARIN Region transit ASes present in the Internet Routing Table: 2011 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 34 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5235 Number of ARIN addresses announced to Internet: 1352798976 Equivalent to 80 /8s, 162 /16s and 19 /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-402332 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, 54/8, 55/8, 56/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: 275386 Total RIPE prefixes after maximum aggregation: 134813 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 273932 Unique aggregates announced from the RIPE address blocks: 175708 RIPE Region origin ASes present in the Internet Routing Table: 28945 RIPE Prefixes per ASN: 9.46 RIPE Region origin ASes announcing only one prefix: 12051 RIPE Region transit ASes present in the Internet Routing Table: 4022 Average RIPE Region AS path length visible: 5.3 Max RIPE Region AS path length visible: 69 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12499 Number of RIPE addresses announced to Internet: 731261568 Equivalent to 43 /8s, 150 /16s and 42 /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-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 53/8, 57/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: 124610 Total LACNIC prefixes after maximum aggregation: 29637 LACNIC Deaggregation factor: 4.20 Prefixes being announced from the LACNIC address blocks: 120914 Unique aggregates announced from the LACNIC address blocks: 48887 LACNIC Region origin ASes present in the Internet Routing Table: 11270 LACNIC Prefixes per ASN: 10.73 LACNIC Region origin ASes announcing only one prefix: 2661 LACNIC Region transit ASes present in the Internet Routing Table: 2546 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 75 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9227 Number of LACNIC addresses announced to Internet: 171832064 Equivalent to 10 /8s, 61 /16s and 243 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 35543 Total AfriNIC prefixes after maximum aggregation: 6730 AfriNIC Deaggregation factor: 5.28 Prefixes being announced from the AfriNIC address blocks: 48225 Unique aggregates announced from the AfriNIC address blocks: 13561 AfriNIC Region origin ASes present in the Internet Routing Table: 1923 AfriNIC Prefixes per ASN: 25.08 AfriNIC Region origin ASes announcing only one prefix: 694 AfriNIC Region transit ASes present in the Internet Routing Table: 377 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 59 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1282 Number of AfriNIC addresses announced to Internet: 104941568 Equivalent to 6 /8s, 65 /16s and 72 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & 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 9808 11144 8759 105 CHINAMOBILE-CN China Mobile Communication 7545 6171 847 649 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4779 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4411 534 308 BBIL-AP BHARTI Airtel Ltd., IN 7552 3919 1332 26 VIETEL-AS-AP Viettel Group, VN 7713 3716 1044 67 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3288 1869 103 VNPT-AS-VN VNPT Corp, VN 24560 2887 855 532 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2352 11521 616 KIXS-AS-KR Korea Telecom, KR 45090 2209 1439 86 TENCENT-NET-AP Shenzhen Tencent Computer 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 13689 40939 5231 AMAZON-02, US 11492 4762 316 595 CABLEONE, US 7155 3862 286 85 VIASAT-SP-BACKBONE, US 6327 3636 1320 81 SHAW, CA 174 3476 8745 877 COGENT-174, US 22773 3346 3032 169 ASN-CXA-ALL-CCI-22773-RDC, US 749 3229 54783 2480 DNIC-AS-00749, US 396982 3187 3854 427 GOOGLE-CLOUD-PLATFORM, US 16625 3004 1251 2218 AKAMAI-AS, US 36352 2816 230 857 AS-COLOCROSSING, 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 7696 1713 148 UNI2-AS, ES 39891 4798 293 63 ALJAWWALSTC-AS, SA 20940 3951 3395 127 AKAMAI-ASN1, NL 9009 3887 358 2083 M247, RO 12389 3121 2305 888 ROSTELECOM-AS PJSC Rostelecom. Technical 34984 2402 361 579 TELLCOM-AS, TR 212238 2272 166 1659 CDNEXT, GB 8452 1614 1852 14 TE-AS TE-AS, EG 13188 1606 100 34 TRIOLAN, UA 62240 1414 94 738 CLOUVIDER Clouvider - Global ASN, GB 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 12195 3254 578 UNINET, MX 10620 3502 481 1019 Telmex Colombia S.A., CO 13999 2493 541 357 Mega Cable, S.A. de C.V., MX 11830 1990 369 64 Instituto Costarricense de Electricidad y 28573 1374 2436 266 Claro NXT Telecomunicacoes Ltda, BR 3816 1340 787 207 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 11664 1204 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1200 371 22 Telefonica del Peru S.A.A., PE 22884 1061 67 374 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 6503 1041 373 162 Axtel, S.A.B. 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 24835 1820 644 27 RAYA-AS, EG 24863 1633 389 16 LINKdotNET-AS, EG 29571 1607 102 33 ORANGE-COTE-IVOIRE, CI 36992 1431 1519 280 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 37069 1107 1100 18 MOBINIL, EG 36935 1066 523 47 Vodafone-, EG 20011 981 185 286 INTERNET-SOLUTIONS, ZA 36914 564 82 3 KENET-AS, KE 15399 542 57 59 WANANCHI-, KE 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 16509 13689 40939 5231 AMAZON-02, US 8151 12195 3254 578 UNINET, MX 9808 11144 8759 105 CHINAMOBILE-CN China Mobile Communication 12479 7696 1713 148 UNI2-AS, ES 7545 6171 847 649 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4798 293 63 ALJAWWALSTC-AS, SA 4538 4779 4192 76 ERX-CERNET-BKB China Education and Resear 11492 4762 316 595 CABLEONE, US 9498 4411 534 308 BBIL-AP BHARTI Airtel Ltd., IN 20940 3951 3395 127 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 8151 12195 11617 UNINET, MX 9808 11144 11039 CHINAMOBILE-CN China Mobile Communications Grou 12479 7696 7548 UNI2-AS, ES 7545 6171 5522 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4798 4735 ALJAWWALSTC-AS, SA 4538 4779 4703 ERX-CERNET-BKB China Education and Research Net 11492 4762 4167 CABLEONE, US 9498 4411 4103 BBIL-AP BHARTI Airtel Ltd., IN 7552 3919 3893 VIETEL-AS-AP Viettel Group, VN 20940 3951 3824 AKAMAI-ASN1, NL 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 22542 UNALLOCATED 8.7.205.0/24 3356 LEVEL3, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 394804 UNALLOCATED 8.33.225.0/24 3356 LEVEL3, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.38.73.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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.147.240.0/24 Origin: 32302 RESERVED, ZZ 23.147.240.0/24 Transit: 32787 PROLEXIC-TECHNOLOGIES-DDOS-MITIGATION-NE 23.155.208.0/24 Origin: 396169 AS-GHCIL-01, US 23.155.208.0/24 Transit: 35985 ONERINGNET-ATL-1, US 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:14 /10:41 /11:92 /12:300 /13:582 /14:1211 /15:2140 /16:13919 /17:8329 /18:13756 /19:24798 /20:44789 /21:52198 /22:112503 /23:102842 /24:608991 /25:794 /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 12479 6616 7696 UNI2-AS, ES 8151 6413 12195 UNINET, MX 11492 3559 4762 CABLEONE, US 39891 3489 4798 ALJAWWALSTC-AS, SA 6327 3431 3636 SHAW, CA 7155 2821 3862 VIASAT-SP-BACKBONE, US 22773 2496 3346 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2377 13689 AMAZON-02, US 30036 2246 2587 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2189 3502 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1726 2:1491 3:819 4:10 5:4709 6:162 7:6 8:1596 9:1 11:172 12:1346 13:451 14:2559 15:360 16:285 17:379 18:920 20:545 21:4 22:188 23:7599 24:2820 25:2 27:2711 29:19 31:3297 32:39 33:1 34:80 35:257 36:3102 37:4591 38:9372 39:908 40:166 41:4202 42:953 43:2598 44:378 45:18624 46:5116 47:325 49:1954 50:1899 51:592 52:1567 54:328 55:1091 56:11 57:269 58:2148 59:1366 60:1171 61:2811 62:2936 63:1801 64:5452 65:2179 66:4661 67:3049 68:1132 69:3861 70:1075 71:639 72:2828 74:2793 75:1509 76:620 77:2717 78:1882 79:1718 80:2240 81:2063 82:3157 83:1450 84:1876 85:3460 86:1081 87:2392 88:1302 89:4421 90:770 91:8407 92:2721 93:2913 94:4028 95:4348 96:1425 97:312 98:981 99:698 100:73 101:1205 102:3818 103:32298 104:5149 105:765 106:1035 107:2668 108:1252 109:4094 110:2236 111:3336 112:2133 113:1539 114:1998 115:2120 116:2065 117:2529 118:2359 119:1946 120:2022 121:1432 122:2789 123:2195 124:1636 125:2909 126:91 128:1598 129:957 130:1302 131:2014 132:780 133:449 134:1521 135:350 136:1349 137:1174 138:2836 139:1582 140:1610 141:1510 142:1900 143:1842 144:1138 145:545 146:2185 147:2106 148:2711 149:2894 150:1253 151:1976 152:2095 153:512 154:7466 155:1745 156:3029 157:1908 158:1331 159:2497 160:3589 161:1850 162:3846 163:2200 164:1858 165:1983 166:1499 167:1961 168:4015 169:795 170:5125 171:1021 172:4466 173:3332 174:921 175:1297 176:3707 177:4739 178:3725 179:2310 180:2636 181:4072 182:3444 183:1861 184:2077 185:21605 186:5197 187:4522 188:4261 189:4297 190:9624 191:1488 192:11322 193:9486 194:7826 195:5565 196:3281 197:3668 198:6209 199:8533 200:8246 201:6379 202:10491 203:10585 204:4581 205:3643 206:4490 207:3629 208:4264 209:5181 210:4862 211:2639 212:4588 213:3744 214:1029 215:48 216:6767 217:3167 218:1412 219:553 220:2141 221:1138 222:857 223:2494 End of report

1 0

LDP interop with RSVP and SR
by Saku Ytti 13 Jun '25

13 Jun '25

I just want to double check that I'm not confused. Since day1 we have had excellent LDP/SR interop, that is, for your SR network, connecting LDP-only nodes or islands doesn't require soiling your entire SR network with LDP state. Do we really not have a similar solution for RSVP? Let's imagine an RSVP-only network, where we add a single LDP-only speaker. Instead of tLDP from every RSVPOnly to RSVPBorder and then LDP between RSVPBorder and LDPOnly, why can't RSVPBorder handle the interop? RSVP -> LDP - Every RSVPOnly would have 1 LSP to RSVPBorder and 1 LSP for each LDP nodes RSVPBorder meets, via RESV TunnelId or such discriminator you can of course have arbitrary amount of LSPs between two endpoints - RSVPBorder will advertise different labels for each of these LSPs, like it would for split LSPs or QoS based LSPs - the LSP terminating on RSVPBorder is popped, the LSPs intended for LDP speaker are swapped from RSVP label to the LDP label LDP -> RSVP - RSVPBorder synthesises for each RSVPOnly/32 LDP route to LDPOnly - As LDPOnly sends LDP label to RSVPBorder, RSVPBorder swaps it to the RSVP label Now in practice when this requirement exists, everyone is running full mesh tLDP, because that's easy to provision. Ending up having thousands of useless LDP sessions with state and fragility that comes with it. -- ++ytti

2 1

IP Transit provider with Flowspec and NetFlow(sFlow) of dropped - Utopian?
by Douglas Fischer 11 Jun '25

11 Jun '25

Today, from the point of view of coordinating DDoS attack mitigation, the biggest challenge is having a reference on whether the propagated external actions are having results or not. FlowSpec rules (or another method) are sent and we are left blind here, not knowing what is happening there and in what volume. It is no longer news that there are IP Transit Providers that support Flowspec. Some limit it to 100 rules, some reach 500... And I am not talking about mitigation, just Flowspec. Today this is a differential, but I believe it will soon be commonplace. I also remember hearing here at NANOG about some ITPs in which sending traffic flow is part of the transit product's feature set. My memory is not helping me remember whether the exported flow was of all traffic or if it was only of what was dropped. On the other hand, there are mitigation companies that claim to "do some magic", but provide zero visibility of what was actually received and mitigated. A complete black box. Looking at these positions in the market, I wonder if it is possible to expect any movement from the market, either from the demanders or from the suppliers of the product "IP Transit" that naturally involves Flowspec and also the export of NetSlow/sFlow that may have been dropped by the Flowspec rules sent. Does it make any sense to expect this? It is obvious that on the supplier side this involves CAPEX and OPEX and no one should expect this "for free". Costs related to this should be added to the price of the IP Transit product. P.S.: These statements certainly refer to the FlowSpecv2 draft. But it expired in October 2024, and I have not followed the discussions about it anymore. And even if FlowSpecv2 magically became an RFC overnight, it would still take 3-4 years for it to enter the boxes in production on the Internet. So although I think the idea of FlowSpecv2 is excellent, I don't have high expectations for the short term. -- Douglas Fernando Fischer Engº de Controle e Automação

2 1

AS18881 Telefonica Brazil contact
by Marco Moock 11 Jun '25

11 Jun '25

Hello! I tried to contact AS18881, because some of their IPv6 networks are not propagated to AS3320. I used the addresses in the whois, but got no reply and the issue persists. This affects 2804:1b1:c000::/35 and others. Can anybody give a hint how to contact them? -- kind regards Marco

2 4

Root Zone DNSSEC Operational Update
by Wessels, Duane 10 Jun '25

10 Jun '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Verisign, in its role as the root zone ZSK operator, is transitioning to a new Hardware Security Module (HSM) product for the root zone's Zone Signing Key (ZSK). The current HSM vendor, Ultra Intelligence & Communications, has announced their KeyperPLUS will no longer be supported by them. Verisign will use an HSM product from Thales for the root zone ZSK going forward. On July 1, 2025 we will begin using the Thales HSM to sign the root zone on a daily basis. Although we anticipate this will be a seamless change for end users and anticipate no problems, prudence dictates that we need a backout plan, should it become necessary. As part of our backout plan, we will be post-publishing the previous quarter's ZSK for a longer than normal period of time. Normally, following a quarterly ZSK rollover, the previous key is post-published for a period of 10 days. As part of our HSM transition, we will instead post-publish the previous ZSK for a period of 80 days. This provides ample time to remediate any issues that may arise as part of this transition, and should it become necessary, to revert to using the old HSM to sign the root zone. -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEvEG6oyZuoN5HQhnubJmkaajAmI0FAmhGex8ACgkQbJmkaajA mI1MEQgAo5/CB0GHYJq+4EqPCecevajsAhjcr4NXxViKyU5K3E//DwR82LIC9p6T HWLY1C0tiFk2Sg/3FbxF2arnUVC9yPJHOI5y2O+AE/BJibSVCyEEse+CbQkVljEd peaHNkkqp96AGgJiZv1On+B63Nog4CBrGMRxD14J0IAZShGbFqDZLRo6VhTHCCf+ isea/+1LbAbe/r2lTbm72q3a5lt/br6yRl37MZAbsJh8PyOAQE54jcnMlypL3qlx VribLjYduQAyKfUgMfVOXOionoY8i+4u1Rce9GXC130jklW7KXsp4un0SCGT5ByV gQWK5Hz73A4039CiUtjm3WqoIILIcg== =kLWP -----END PGP SIGNATURE-----

1 0

LACNOG 2025 – Call for Presentations
by Hernan Moguilevsky 09 Jun '25

09 Jun '25

LACNOG 2025 - Call for Presentations LACNOG, the Latin American and Caribbean Network Operators Group, will hold its LACNOG 2025 conference on 6 - 10 October 2025, together with the LACNIC 44 event to be held in San Salvador, El Salvador. Presentation formats include: ·Lightning talks: Brief, 10-minute presentations (including an additional 5-minute space for questions). ·Presentations: 20-minute presentations (including an additional 5-minute space for questions). LACNOG invites the submission of technical papers and case studies on the following topics: *1. Network Operation and Architecture*** * IP network design, implementation, and administration * Routing and switching protocols * Success stories, lessons learned, and operational experiences *2. Automation and Observability*** * Network automation, configuration, deployment, and monitoring * Telemetry, performance, traceability, and traffic analysis * Tool integrating (NetDevOps, APIs, CI/CD for networking) *3. Interconnection and the Internet Ecosystem*** * Peering, IXPs, interconnection policies, and regional experiences * Internet governance, regulation, and legal aspects *4. Security and Resilience*** * RPKI, route validation, and global routing system security * Threat prevention, detection, and mitigation * MANRS and best practices in security * Incident management and recovery *5. Services and Applications*** * DNS, email, web, CDNs, NFV, and cloud services * Universal Acceptance and technical challenges of internationalization *6. Emerging Technologies*** * Internet of Things (IoT), 5G, Edge/Cloud-native networking * Artificial Intelligence in networking *7. Infrastructure and Transport*** * Optical networks, DWDM, wireless networks, and access technologies. * Physical infrastructure and the evolution of transport. *8. Research and Training*** * Relevant academic projects, measurements, and case studies * Technical education, capacity building, and community networks Proposals for the event will be selected following the calendar below: * Reception of proposals: 9 May - 11 July 2025 at23:59 UTC -3 (Uruguay time) * Evaluation by the Program Committee: 21 - 30 July 2025 * Confirmation by selected presenters: 31 July - 5 August 2025 * Program to be published: 6 - 9 August 2025 * Deadline for submitting the final presentation: 10 August - 22 September 2025 at 23:59 UTC-3 (Uruguay time) * LACNOG2025: 6 - 10 October 2025 Applicants must submit a summary and a draft of the slides of their proposed presentations along with a brief biography, for which they must use the form available at https://eventos.nog.lat/event/29/ If your work is selected, you authorize LACNOG and LACNIC to publish your name, photograph, biography, and final presentation in the event program. Speakers presenting at the LACNOG 2025 conference will receive a certificate acknowledging their participation. Guidelines for Submitting a Presentation for LACNOG have been prepared containing a description of the criteria that will be considered when evaluating each proposal, presentation format details and other data. These Guidelines are available at https://tinyurl.com/lacnog-presentations <https://tinyurl.com/lacnog-presentations> Communications with the Program Committee will be handled through pc(a)lacnog.org <mailto:pc@lacnog.org>. We thank you in advance for your attention and look forward to receiving your proposals for LACNOG 2025.

1 0

Freedom fi / Mosolabs CBRS EnB rest ?
by Faisal Imtiaz 09 Jun '25

09 Jun '25

Hello Everyone, A bit of a long shot question, anyone knows how to reset a Freedomfi/Mosolabs Helium EnB so that they can be reused for private LTE ? Many thanks in advance ! Regards, Faisal Imtiaz

1 0

Spoofer Report for NANOG for May 2025
by CAIDA Spoofer Project 08 Jun '25

08 Jun '25

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during May 2025: ASN Name Fixed-By 20381 CABLELABS-LV 2025-05-02 40676 AS40676 2025-05-14 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during May 2025: ASN Name First-Spoofed Last-Spoofed 577 BACOM 2016-03-09 2025-05-04 40676 AS40676 2016-08-29 2025-05-27 27364 ACS-INTERNET 2016-09-27 2025-05-30 11427 TWC-11427-TEXAS 2016-10-21 2025-05-05 63296 AWBROADBAND 2017-09-01 2025-05-28 21804 ACCESS-SK 2019-06-09 2025-05-27 32035 CCDT 2021-06-09 2025-05-05 12183 TALKIE-COMMUNICATIONS 2022-12-10 2025-05-28 400282 2023-04-27 2025-05-28 393577 SCCNET 2023-05-03 2025-05-29 61461 Airtek Solutions C.A. 2023-05-13 2025-05-28 20119 ARROW 2023-10-19 2025-05-30 394684 WISPERNET 2024-01-17 2025-05-29 393530 TLU 2024-05-22 2025-05-31 19935 CRRS 2024-05-29 2025-05-20 398182 BLN 2024-06-17 2025-05-05 3801 MISNET 2024-09-09 2025-05-14 54334 ROYA 2025-03-13 2025-05-28 16739 MIDCO-NET-INV 2025-03-19 2025-05-20 273843 2025-04-02 2025-05-27 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

STOP SPAM! AS3292/tdc.dk/tdk.net/Tele Danmark
by Soha Jin 06 Jun '25

06 Jun '25

Hi! AS3292/tdc.dk/tdk.net/Tele Danmark, are you watching the list? Or is there anyone who knows people there? Your mail system keeps spamming 200+ recipients in the last 14 hours, all mails are sent from `peering(a)tdk.net`. On PeeringDB, the NOC address is also `peering(a)tdk.net`. I have tried contact you via email 10 hours ago. The ticket system tries to reply EVERY email starting with `Re:`, but your list, `peering(a)tdc.dk`, is also in the recipients list! You are bouncing your own mails! Each mail is sending to 200+ other recipients! Of course, your outgoing queue is overloaded. The latest mail has queued for 10 hours: > Received: from mailproxy10.eng.tdc.net <redacted>; > Fri, 6 Jun 2025 20:26:01 +0000 > Received: from rt.eng.tdc.net <redacted>; > Fri, 6 Jun 2025 12:11:54 +0200 (CEST) Please, clear your mail queue, stop spamming us anymore. THANK YOU! Regards, Soha

1 0