- NANOG - lists.nanog.org

Spoofer Report for NANOG for Dec 2023
by CAIDA Spoofer Project 08 Jan '24

08 Jan '24

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 Dec 2023: none inferred Source Address Validation issues inferred during Dec 2023: ASN Name First-Spoofed Last-Spoofed 3356 LEVEL3 2016-03-06 2023-12-21 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2023-12-29 20412 CLARITY-TELECOM 2016-09-30 2023-12-30 6181 FUSE-NET 2016-10-10 2023-12-13 25787 ROWE-NETWORKS 2016-10-21 2023-12-30 271 BCNET 2016-10-24 2023-12-10 701 UUNET 2017-06-14 2023-12-04 46997 2021-12-22 2023-12-29 12183 TALKIE-COMMUNICATIONS 2022-12-10 2023-12-26 3701 NERONET 2023-04-18 2023-12-28 400282 2023-04-27 2023-12-30 46690 SNET-FCC 2023-05-20 2023-12-26 20119 ARROW 2023-10-19 2023-12-04 26721 INYO 2023-12-17 2023-12-17 393577 SCCNET 2023-12-19 2023-12-28 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

Fellowships for ARIN 53
by John Sweeting 06 Jan '24

06 Jan '24

NANOGers – For those folks (e.g., yourself, friends, coworkers, ...) who are looking for an in-depth mentored introduction to ARIN, please consider applying to participate in the ARIN 53 Fellowship Program! Details attached below, and more online at https://www.arin.net/fellowships. Thanks, John S.

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 05 Jan '24

05 Jan '24

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 06 Jan, 2024 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: 937592 Prefixes after maximum aggregation (per Origin AS): 357849 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 456342 Total ASes present in the Internet Routing Table: 75212 Prefixes per ASN: 12.47 Origin-only ASes present in the Internet Routing Table: 64521 Origin ASes announcing only one prefix: 26564 Transit ASes present in the Internet Routing Table: 10691 Transit-only ASes present in the Internet Routing Table: 493 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 66 Max AS path prepend of ASN (272886) 61 Prefixes from unregistered ASNs in the Routing Table: 1112 Number of instances of unregistered ASNs: 1114 Number of 32-bit ASNs allocated by the RIRs: 43316 Number of 32-bit ASNs visible in the Routing Table: 35614 Prefixes from 32-bit ASNs in the Routing Table: 179632 Number of bogon 32-bit ASNs visible in the Routing Table: 32 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 482 Number of addresses announced to Internet: 3048811264 Equivalent to 181 /8s, 185 /16s and 43 /24s Percentage of available address space announced: 82.4 Percentage of allocated address space announced: 82.4 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: 309431 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 251118 Total APNIC prefixes after maximum aggregation: 72502 APNIC Deaggregation factor: 3.46 Prefixes being announced from the APNIC address blocks: 244085 Unique aggregates announced from the APNIC address blocks: 99680 APNIC Region origin ASes present in the Internet Routing Table: 13870 APNIC Prefixes per ASN: 17.60 APNIC Region origin ASes announcing only one prefix: 4166 APNIC Region transit ASes present in the Internet Routing Table: 1873 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 34 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9220 Number of APNIC addresses announced to Internet: 774693504 Equivalent to 46 /8s, 44 /16s and 226 /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-153913 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: 274378 Total ARIN prefixes after maximum aggregation: 124616 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 279300 Unique aggregates announced from the ARIN address blocks: 133020 ARIN Region origin ASes present in the Internet Routing Table: 19084 ARIN Prefixes per ASN: 14.64 ARIN Region origin ASes announcing only one prefix: 6955 ARIN Region transit ASes present in the Internet Routing Table: 1950 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4828 Number of ARIN addresses announced to Internet: 1273895424 Equivalent to 75 /8s, 238 /16s and 26 /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: 260529 Total RIPE prefixes after maximum aggregation: 125124 RIPE Deaggregation factor: 2.08 Prefixes being announced from the RIPE address blocks: 254988 Unique aggregates announced from the RIPE address blocks: 160949 RIPE Region origin ASes present in the Internet Routing Table: 28498 RIPE Prefixes per ASN: 8.95 RIPE Region origin ASes announcing only one prefix: 12125 RIPE Region transit ASes present in the Internet Routing Table: 3933 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 37 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11503 Number of RIPE addresses announced to Internet: 714299776 Equivalent to 42 /8s, 147 /16s and 89 /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, 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: 119919 Total LACNIC prefixes after maximum aggregation: 28844 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 118690 Unique aggregates announced from the LACNIC address blocks: 49478 LACNIC Region origin ASes present in the Internet Routing Table: 11055 LACNIC Prefixes per ASN: 10.74 LACNIC Region origin ASes announcing only one prefix: 2672 LACNIC Region transit ASes present in the Internet Routing Table: 2368 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 66 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8905 Number of LACNIC addresses announced to Internet: 177768960 Equivalent to 10 /8s, 152 /16s and 138 /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: 30536 Total AfriNIC prefixes after maximum aggregation: 6047 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 40047 Unique aggregates announced from the AfriNIC address blocks: 12817 AfriNIC Region origin ASes present in the Internet Routing Table: 1818 AfriNIC Prefixes per ASN: 22.03 AfriNIC Region origin ASes announcing only one prefix: 646 AfriNIC Region transit ASes present in the Internet Routing Table: 352 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 27 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1158 Number of AfriNIC addresses announced to Internet: 107835136 Equivalent to 6 /8s, 109 /16s and 111 /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 9818 8740 56 CHINAMOBILE-CN China Mobile Communicati 7545 5677 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4548 347 25 FPT-AS-AP FPT Telecom Company, VN 7552 3825 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3605 1043 64 TELKOMNET-AS-AP PT Telekomunikasi Indon 9498 3417 498 254 BBIL-AP BHARTI Airtel Ltd., IN 45899 3269 1872 99 VNPT-AS-VN VNPT Corp, VN 24560 2665 857 379 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2324 11258 578 KIXS-AS-KR Korea Telecom, KR 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 9437 11194 3356 AMAZON-02, US 11492 4563 303 680 CABLEONE, US 7155 4177 288 96 VIASAT-SP-BACKBONE, US 6327 3568 1320 70 SHAW, CA 22773 3516 3059 303 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3217 1426 2336 AKAMAI-AS, US 749 3161 54929 2413 DNIC-AS-00749, US 367 2955 3836 1416 DNIC-ASBLK-00306-00371, US 396982 2744 3639 389 GOOGLE-CLOUD-PLATFORM, US 7018 2503 23622 1573 ATT-INTERNET4, 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 5755 1714 146 UNI2-AS, ES 39891 4641 279 54 ALJAWWALSTC-AS, SA 20940 4011 3397 142 AKAMAI-ASN1, NL 9009 3464 298 1626 M247, RO 8551 3145 368 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2993 2301 912 ROSTELECOM-AS, RU 34984 2324 359 598 TELLCOM-AS, TR 13188 1607 100 26 TRIOLAN, UA 58224 1511 872 577 TCI, IR 8452 1471 1852 14 TE-AS TE-AS, EG 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 12175 3384 590 UNINET, MX 10620 3523 497 888 Telmex Colombia S.A., CO 13999 2496 340 638 Mega Cable, S.A. de C.V., MX 11830 2006 369 64 Instituto Costarricense de Electricidad 28573 1345 2318 237 Claro NXT Telecomunicacoes Ltda, BR 3816 1306 787 197 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1245 341 503 Axtel, S.A.B. de C.V., MX 11664 1109 178 419 Techtel LMDS Comunicaciones Interactiva 6147 1088 369 22 Telefonica del Peru S.A.A., PE 22884 1074 116 375 TOTAL PLAY TELECOMUNICACIONES SA DE CV, 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 1543 545 28 RAYA-AS, EG 24863 1531 389 16 LINKdotNET-AS, EG 36992 1361 1518 280 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 29571 1072 69 53 ORANGE-COTE-IVOIRE, CI 36935 936 521 43 Vodafone-, EG 6713 551 1861 34 IAM-AS, MA 15399 543 56 55 WANANCHI-, KE 36914 506 82 3 KENET-AS, KE 37342 481 32 1 MOVITEL, MZ 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 12175 3384 590 UNINET, MX 9808 9818 8740 56 CHINAMOBILE-CN China Mobile Communicati 16509 9437 11194 3356 AMAZON-02, US 12479 5755 1714 146 UNI2-AS, ES 7545 5677 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4641 279 54 ALJAWWALSTC-AS, SA 11492 4563 303 680 CABLEONE, US 18403 4548 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4177 288 96 VIASAT-SP-BACKBONE, 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 9818 9762 CHINAMOBILE-CN China Mobile Communications Grou 16509 9437 6081 AMAZON-02, US 12479 5755 5609 UNI2-AS, ES 7545 5677 4990 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4850 ERX-CERNET-BKB China Education and Research Net 39891 4641 4587 ALJAWWALSTC-AS, SA 18403 4548 4523 FPT-AS-AP FPT Telecom Company, VN 7155 4177 4081 VIASAT-SP-BACKBONE, US 11492 4563 3883 CABLEONE, US 20940 4011 3869 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 65536 DOCUMENT 5.102.30.0/24 65512 -Private Use AS-, ZZ 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 396894 UNALLOCATED 8.28.201.0/24 46887 LIGHTOWER, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, 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.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.176.160.0/24 Origin: 397327 RESERVED, ZZ 23.176.160.0/24 Transit: 19108 SUDDENLINK-COMMUNICATIONS, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, US 36.255.139.0/24 Origin: 56050 NEW-SHINE-INTERNET-TH 134 Yenchit Road, 36.255.139.0/24 Transit: 58913 HCL-TH 4819 Supapong 3 Alley, Srinakarin 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:37 /11:99 /12:301 /13:581 /14:1194 /15:2065 /16:13440 /17:8264 /18:13817 /19:25082 /20:44416 /21:51742 /22:109855 /23:99801 /24:566141 /25:727 /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 8151 6182 12175 UNINET, MX 12479 5057 5755 UNI2-AS, ES 11492 3477 4563 CABLEONE, US 6327 3372 3568 SHAW, CA 39891 3324 4641 ALJAWWALSTC-AS, SA 7155 3121 4177 VIASAT-SP-BACKBONE, US 8551 2622 3145 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2555 3516 ASN-CXA-ALL-CCI-22773-RDC, US 10620 2126 3523 Telmex Colombia S.A., CO 30036 2121 2465 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2312 2:1414 3:281 4:5 5:4421 6:165 7:6 8:1531 9:1 11:172 12:1487 13:375 14:2339 15:309 16:206 17:363 18:711 20:344 21:4 22:188 23:6590 24:2678 25:2 27:2503 29:19 31:2537 32:56 34:35 35:121 36:2141 37:4483 38:5836 39:884 40:147 41:4138 42:2212 43:2327 44:325 45:16687 46:4294 47:286 49:1910 50:1892 51:574 52:1590 54:368 55:893 56:5 57:129 58:1924 59:1172 60:1012 61:2567 62:2753 63:1905 64:5494 65:2338 66:5005 67:3043 68:1337 69:4085 70:1179 71:573 72:2922 74:2647 75:1559 76:626 77:2341 78:1829 79:2891 80:2114 81:1860 82:1522 83:1323 84:1624 85:2857 86:780 87:1971 88:1230 89:3950 90:399 91:7905 92:2177 93:2632 94:3593 95:3997 96:1288 97:315 98:1015 99:744 100:94 101:1158 102:3019 103:32556 104:4775 105:601 106:983 107:2740 108:1123 109:4072 110:2140 111:3215 112:2087 113:1793 114:1753 115:1997 116:1984 117:2630 118:2773 119:1943 120:1806 121:1312 122:2646 123:2220 124:1598 125:2803 128:1460 129:919 130:1069 131:1961 132:820 133:411 134:1710 135:304 136:914 137:997 138:2696 139:1570 140:1350 141:1339 142:1546 143:1518 144:1003 145:337 146:2000 147:1641 148:2495 149:2416 150:1020 151:1313 152:1970 153:530 154:5539 155:1378 156:2107 157:1381 158:1081 159:2208 160:2618 161:1621 162:3601 163:1671 164:1628 165:2098 166:1075 167:1696 168:3839 169:796 170:4709 171:993 172:3782 173:3008 174:896 175:1216 176:3590 177:4620 178:3531 179:2242 180:2350 181:3648 182:3459 183:2023 184:2271 185:20493 186:4789 187:4312 188:4012 189:3965 190:9342 191:1494 192:11042 193:8962 194:7367 195:5230 196:3167 197:2632 198:5995 199:6888 200:8096 201:6257 202:10496 203:10081 204:4598 205:3678 206:4465 207:3500 208:4106 209:4962 210:4626 211:2590 212:4224 213:3387 214:1117 215:50 216:6778 217:2753 218:1347 219:587 220:2047 221:1021 222:868 223:2218 End of report

1 0

New Year, New Sponsorship Opportunities + More
by Nanog News 04 Jan '24

04 Jan '24

*Happy New Year!* *The Best is Yet to Come...* Thank you for joining us for another exciting year at NANOG! Our first meeting of the New Year will kick off Feb. 12 - 14 in Charlotte, NC. Find out more details and register now. *REGISTER NOW * <https://nanog.org/events/nanog-90/register/> *N90 Hotel Venue Confirmed!* *NANOG 90 will Occur at the Le Méridien Charlotte* Registered NANOG attendees, *when logged in with their NANOG profile, *can begin booking now. The room block will be available to all attendees starting Tuesday, 09-January-2024. *BOOK NOW * <https://nanog.org/login/?next=/events/nanog-90/hotel/> *New NANOG 90 Sponsorships Available* *Don't Miss Exciting New Sponsorship Opportunities!* *+ Hotel Keycard Sponsor* *Co-branded hotel key card, available to all NANOG guests registered under the NANOG hotel room block, designed & produced by NANOG.Sign-on deadline Friday Jan 5* *+ Meeting Lanyard Sponsor* *Co-branded meeting badge and lanyard for attendees, designed & produced by NANOG.Sign-on deadline Thursday Jan 11* *+ Meeting T-Shirt Sponsor* *Co-branded meeting t-shirt for attendees, designed & produced by NANOG.Sign-on deadline Friday Jan 19* *Please reach out to Shawn Winstead at swinstead(a)nanog.org <swinstead(a)nanog.org> for more details.* *Video of the Week* *Streaming with Open Caching on the ISP Edge w/ Jeff Budney* Learn about how Verizon has traditionally received streaming traffic, the efforts within industry organizations to improve the streaming video experience through Open Caching and the results seen at Verizon nationwide. *WATCH NOW * <https://www.youtube.com/watch?v=7OAa0s-FDeY>

1 0

Issue with Geolocation in Virginia US
by Raja Sekhar Gullapalli 04 Jan '24

04 Jan '24

Team, We are having issues in our Virginia US office & it shows geolocation in all browsers as Canada instead of US region when we access news.google.com in our PC. Our public ip is 129.46.232.65. This issue is being observed for more than 2 month. Can you help to whom we can contact to resolve the issue. Regards, Raja

8 13

RPKI's 2023 Year in Review - growth, governments, and innovation
by Job Snijders 03 Jan '24

03 Jan '24

Dear all, Happy new year everyone! Having just closed chapter 2023 - let's look back at the previous year. In this memo I'll share some RPKI statistics, summarize highlights from the IETF Standards Development process, and reflect on emerging trends. Year to Year Growth of the distributed RPKI database =============================================================== A straight-forward method to compare to last year is to look at the RPKI's absolute numbers. The below table was constructed by comparing two December 31st RPKIviews.org snapshots [1] of validated RPKI caches, primed with the ARIN, AFRINIC, APNIC, LACNIC, and RIPE NCC Trust Anchors. 2022-12-31 2023-12-31 Total cache size (KiB): 1,240,572 1,546,728 (+25%) Total number of files (objects): 242,969 309,802 (+27%) Publication servers (FQDNs): 52 63 (+21%) Certification authorities: 34,901 40,511 (+16%) Route origin authorizations: 138,323 188,345 (+36%) Unique VRPs: 390,752 497,341 (+27%) IPv4 addresses covered: 1,354,270,410 2,502,293,068 (+85%) IPv6 addresses covered: 9,447 * 10^30 17,263 * 10^30 (+83%) Unique origin ASNs in ROAs: 34,455 40,656 (+18%) The number of IP addresses covered by ROAs almost doubled compared to last year. More than half the ASes in the global Internet routing system are listed as Origin AS in at least one ROA. EOY'23 more unique IPv6 prefix-origin pairs in the DFZ are covered by ROAs than not, with IPv4 likely to follow crossing this threshold in Q1 2024. Kentik [2] estimates that more than half of IP traffic is destined towards ROA covered destinations. APNIC Labs [3] estimates the global "I-Rov Filtering Rate" to be at 22.69% now. These numbers mean it will be worth your while to create and use ROAs for BGP Origin Validation. In short: it's all up and to the right. :-) Increased Government Interest in Internet Routing Security =============================================================== Following the FCC's launch of an inquiry into Internet Routing Vulnerabilities in 2022, in 2023 the agency followed up with a BGP Security Workshop hosted by the Public Safety and Homeland Security Bureau [4], the industry seemed well represented with key players participating. While the USG is still sizing up the industry's posture and contemplating whether regulation is warranted, in the Netherlands the government itself aspires to lead by example: in 2023 the Dutch government committed to use RPKI by the end of 2024 on all new and existing IT systems it operates [5]. Note that this ambition includes both signing ROAs and validating BGP messages! I hope they succeed. Will more governments follow the Dutch lead in 2024? The Rise Of Initiatives Re-evaluating The RPKI Trust Model =============================================================== As the industry saw unprecedented turmoil in the realm of governance of Regional Internet Registries in 2023, two interesting initiatives arose, both aiming to reduce the risk surface associated with blindly trusting 'the RPKI Roots'. In the RPKI hierarchical structure, a Trust Anchor (a root) is an authority for which trust is assumed and not derived. The phrase "assumed trust" means that violation of that trust is out-of-scope for the threat model. On the other hand, the phrase "derived trust" refers to trust automatically and securely computed with subjective logic. In the context of the RPKI, trust is derived according to the rules for validation of RPKI Certificates and Signed Objects. One initiative is to impose 'locally configured constraints' which limit the effective signing authority of an RIR. The other initiative is to instantiate a sixth RPKI trust anchor - which chains up to the existing RIR-operated infrastructure - and impose inter-RIR consensus-driven constraints on that arc. Initiative #1 - operator imposed constraints: Cover letter & discussion: https://mailman.nanog.org/pipermail/nanog/2023-September/223354.html Running code - rpki-client 8.7 & higher https://cdn.openbsd.org/pub/OpenBSD/rpki-client/rpki-client-8.7.txt An internet-draft detailing the implementation: https://datatracker.ietf.org/doc/html/draft-snijders-constraining-rpki-trus… Initiative #2 - externally imposed constraints: Cover letter: https://labs.apnic.net/index.php/2023/12/13/models-of-trust-in-the-rpki/ Running code: https://labs.apnic.net/nro-ta/ A proposal for the validation algorithm to be less rigid & more robust: https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-validati… I personally don't care much *who* imposes constraints, but at the end of the day - someone's gotta do it. Keep watching this space! SIDROPS - Working Group developments =============================================================== Some quick updates from the IETF working group responsible for development and maintenance of the RPKI technology stack! Running code - now a requirement -------------------------------- The SIDROPS working group set a new rule: Standards Track internet-drafts can only progress towards RFC publication - after - interoperability was demonstrated between at least two independent implementations of the specification: https://mailarchive.ietf.org/arch/msg/sidrops/54iqtt-Ug2lzMbr9KpQOnWsh2JM/ My expectation is that - because of this new rule - we'll see higher quality documents: the proposals more thoroughly tested, increased readability of the internet-draft texts, and less ambiguity in the specifications. Basing Standards Track documents on real implementation experiences (as opposed to gaining real experiences only after publication of as RFC) seems to be the right way to do things. ASPA - where we at? ------------------- In early 2023 a Canadian IXP, YYCIX, became the first to deploy ASPA validation on its IX Route Servers [6] - while this may seem a leap forward towards wider deployment, things are not all said and done. The IETF SIDROPS working group continues to expostulate over things like the ASPA RPKI-To-Router PDU layout. Still, my hope and expectation is that all ASPA-related documents can be finalized in the next few months. I continue to stand by this timeline: https://www.manrs.org/2023/05/estimating-the-timeline-for-aspa-deployment/ Optimizing RSYNC ---------------- RPKI data can be transported in two ways — an HTTPS-based distribution protocol called RRDP, and via RSYNC. Some argue that RSYNC is not the best fit for transport of RPKI files, but unfortunately RRDP isn't without its own issues either. With neither transport protocol being flawless, turns out RSYNC is perfect as a backup option for RRDP! As long as RSYNC is around, we should care for it and continue maintenance & innovation. Rpki-client as validator, and RIPE NCC & APNIC as publishers implemented a mechanism to smoothen switching from RRDP to RSYNC: https://blog.apnic.net/2023/12/04/using-timestamps-inside-rpki-objects-to-o… https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-cms-signing-time My hope is that more validator projects and RIR repositories adopt this mechanism! Final words =============================================================== As more and more networks adopt RPKI, perhaps motivated by government pressure, our collective dependency on RPKI functioning properly and safely increases too. It is awesome to see so many volunteers contribute their valueable time to study, tinker & propose improvements to this wonderful global system. See you next year! - Job Sources: [1]: RPKI Views - http://rpkiviews.org/ http://josephine.sobornost.net/josephine.sobornost.net/rpkidata/2022/12/31/… http://dango.attn.jp/rpkidata/2023/12/31/rpki-20231231T235150Z.tgz [2]: https://www.kentik.com/blog/exploring-the-latest-rpki-rov-adoption-numbers/ [3]: https://stats.labs.apnic.net/rpki [4]: https://www.fcc.gov/news-events/events/2023/07/bgp-security-workshop [5]: https://www.forumstandaardisatie.nl/nieuws/secured-internet-routing-dutch-g… [6]: https://mailman.nanog.org/pipermail/nanog/2023-February/221471.html

1 0

Sufficient Buffer Sizes
by Mike Hammett 03 Jan '24

03 Jan '24

While attempting to ascertain how big of switch buffers I needed in a 100G switch, I rediscovered this article where I first learned about switch buffers. https://fasterdata.es.net/network-tuning/router-switch-buffer-size-issues/#…. It suggests that 60 meg is what you need at 10G. Is that per interface? Would it be linear in that I would need 600 meg at 100G? Some 100G switches I was looking at only had 36 megs, so that's insufficient either way you look at it. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

6 6

Rackspace contact
by Nathan Book 03 Jan '24

03 Jan '24

Can someone at Rackspace contact me off list? We have issues reaching a Rackspace customer's site. Thanks, *Nathan Book* | IT/Broadband Specialist | GMN Broadband

1 0

Hiring: Machine Learning Engineer ICANN Office CTO
by Samaneh Tajalizadehkhoob 02 Jan '24

02 Jan '24

Greetings and happy new year! I lead the Security Stability and Resiliency (SSR) Research team within ICANN’s office of CTO (OCTO). We are now hiring a machine learning engineer who is also familiar with the DNS and routing industry. The position is remote and we rather hire in Europe. But US is an option too. Please take a look and share with whoever would be interested. https://www.linkedin.com/jobs/view/3672913207 Cheers, Samaneh Tajalizadeh Director, Security Stability Resiliency Research ICANN

1 0

Password Reset
by Luiz Rosas 02 Jan '24

02 Jan '24

Hello, I'm trying to reset a password for username "guga0071", but the email address that is attached to this account I no longer have access to. Can you please update my account with the new email address " lrosas0071(a)gmail.com" and provide me with a link to reset my password. Regards Luiz Rosas

5 6