- Test - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 27 Sep '24

27 Sep '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 28 Sep, 2024 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: 961178 Prefixes after maximum aggregation (per Origin AS): 366431 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 467022 Number of IPv4 prefixes with a valid ROA: 396805 Number of IPv4 prefixes with an invalid ROA: 1088 Number of IPv4 prefixes with no ROA: 563285 Total ASes present in the Internet Routing Table: 76228 Prefixes per ASN: 12.61 Origin-only ASes present in the Internet Routing Table: 65298 Origin ASes announcing only one prefix: 26824 Transit ASes present in the Internet Routing Table: 10930 Transit-only ASes present in the Internet Routing Table: 532 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 84 Max AS path prepend of ASN (152107) 80 Prefixes from unregistered ASNs in the Routing Table: 981 Number of instances of unregistered ASNs: 997 Number of 32-bit ASNs allocated by the RIRs: 45438 Number of 32-bit ASNs visible in the Routing Table: 37126 Prefixes from 32-bit ASNs in the Routing Table: 192951 Number of bogon 32-bit ASNs visible in the Routing Table: 61 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 527 Number of addresses announced to Internet: 3032001536 Equivalent to 180 /8s, 184 /16s and 172 /24s Percentage of available address space announced: 81.9 Percentage of allocated address space announced: 81.9 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: 314167 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 258180 Total APNIC prefixes after maximum aggregation: 75620 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 249801 Unique aggregates announced from the APNIC address blocks: 100822 APNIC Region origin ASes present in the Internet Routing Table: 14373 APNIC Prefixes per ASN: 17.38 APNIC Region origin ASes announcing only one prefix: 4382 APNIC Region transit ASes present in the Internet Routing Table: 1903 Average APNIC Region AS path length visible: 5.5 Max APNIC Region AS path length visible: 84 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9798 Number of APNIC addresses announced to Internet: 759507840 Equivalent to 45 /8s, 69 /16s and 43 /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: 279974 Total ARIN prefixes after maximum aggregation: 126294 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 283566 Unique aggregates announced from the ARIN address blocks: 135417 ARIN Region origin ASes present in the Internet Routing Table: 19145 ARIN Prefixes per ASN: 14.81 ARIN Region origin ASes announcing only one prefix: 6959 ARIN Region transit ASes present in the Internet Routing Table: 2005 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 33 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5002 Number of ARIN addresses announced to Internet: 1267117312 Equivalent to 75 /8s, 134 /16s and 173 /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, 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: 267205 Total RIPE prefixes after maximum aggregation: 128973 RIPE Deaggregation factor: 2.07 Prefixes being announced from the RIPE address blocks: 263983 Unique aggregates announced from the RIPE address blocks: 167489 RIPE Region origin ASes present in the Internet Routing Table: 28749 RIPE Prefixes per ASN: 9.18 RIPE Region origin ASes announcing only one prefix: 12137 RIPE Region transit ASes present in the Internet Routing Table: 3979 Average RIPE Region AS path length visible: 5.4 Max RIPE Region AS path length visible: 43 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12017 Number of RIPE addresses announced to Internet: 723344256 Equivalent to 43 /8s, 29 /16s and 91 /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: 122398 Total LACNIC prefixes after maximum aggregation: 28452 LACNIC Deaggregation factor: 4.30 Prefixes being announced from the LACNIC address blocks: 120179 Unique aggregates announced from the LACNIC address blocks: 48527 LACNIC Region origin ASes present in the Internet Routing Table: 11156 LACNIC Prefixes per ASN: 10.77 LACNIC Region origin ASes announcing only one prefix: 2664 LACNIC Region transit ASes present in the Internet Routing Table: 2479 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 61 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9059 Number of LACNIC addresses announced to Internet: 177508864 Equivalent to 10 /8s, 148 /16s and 146 /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: 32440 Total AfriNIC prefixes after maximum aggregation: 6451 AfriNIC Deaggregation factor: 5.03 Prefixes being announced from the AfriNIC address blocks: 43122 Unique aggregates announced from the AfriNIC address blocks: 14322 AfriNIC Region origin ASes present in the Internet Routing Table: 1885 AfriNIC Prefixes per ASN: 22.88 AfriNIC Region origin ASes announcing only one prefix: 682 AfriNIC Region transit ASes present in the Internet Routing Table: 365 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1250 Number of AfriNIC addresses announced to Internet: 104239616 Equivalent to 6 /8s, 54 /16s and 146 /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 10059 8751 74 CHINAMOBILE-CN China Mobile Communication 7545 5831 840 658 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4951 4192 74 ERX-CERNET-BKB China Education and Resear 18403 4391 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3990 1331 25 VIETEL-AS-AP Viettel Group, VN 9498 3808 509 263 BBIL-AP BHARTI Airtel Ltd., IN 7713 3651 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3261 1841 105 VNPT-AS-VN VNPT Corp, VN 24560 2828 851 470 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2273 11520 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 10812 11830 3806 AMAZON-02, US 11492 4629 308 555 CABLEONE, US 7155 4168 287 88 VIASAT-SP-BACKBONE, US 174 3872 8772 906 COGENT-174, US 6327 3602 1320 79 SHAW, CA 749 3483 55081 2706 DNIC-AS-00749, US 22773 3426 3035 188 ASN-CXA-ALL-CCI-22773-RDC, US 7018 3161 23692 1962 ATT-INTERNET4, US 16625 2847 1259 2128 AKAMAI-AS, US 396982 2832 3603 417 GOOGLE-CLOUD-PLATFORM, 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 7628 1708 145 UNI2-AS, ES 39891 4602 278 58 ALJAWWALSTC-AS, SA 20940 3821 3395 129 AKAMAI-ASN1, NL 9009 3684 315 1870 M247, RO 12389 2945 2295 890 ROSTELECOM-AS, RU 34984 2330 357 581 TELLCOM-AS, TR 212238 1804 130 1336 CDNEXT, GB 13188 1606 100 30 TRIOLAN, UA 8452 1521 1852 14 TE-AS TE-AS, EG 8551 1471 368 35 BEZEQ-INTERNATIONAL-AS Bezeqint Internet 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 11506 3227 506 UNINET, MX 10620 3546 494 937 Telmex Colombia S.A., CO 13999 2550 534 365 Mega Cable, S.A. de C.V., MX 11830 2010 369 64 Instituto Costarricense de Electricidad y 28573 1337 2309 261 Claro NXT Telecomunicacoes Ltda, BR 3816 1318 778 199 COLOMBIA TELECOMUNICACIONES S.A. ESP, CO 11664 1147 278 33 Techtel LMDS Comunicaciones Interactivas 6503 1116 374 163 Axtel, S.A.B. de C.V., MX 6147 1107 369 22 Telefonica del Peru S.A.A., PE 22884 1072 98 369 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 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 1601 593 29 RAYA-AS, EG 24863 1601 389 18 LINKdotNET-AS, EG 36992 1412 1519 283 ETISALAT-MISR, EG 29571 1341 85 63 ORANGE-COTE-IVOIRE, CI 36903 1249 554 96 MT-MPLS, MA 36935 974 523 47 Vodafone-, EG 6713 555 1861 35 IAM-AS, MA 36914 520 82 3 KENET-AS, KE 15399 512 57 58 WANANCHI-, KE 24757 435 73 5 EthioNet-AS, ET 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 11506 3227 506 UNINET, MX 16509 10812 11830 3806 AMAZON-02, US 9808 10059 8751 74 CHINAMOBILE-CN China Mobile Communication 12479 7628 1708 145 UNI2-AS, ES 7545 5831 840 658 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4951 4192 74 ERX-CERNET-BKB China Education and Resear 11492 4629 308 555 CABLEONE, US 39891 4602 278 58 ALJAWWALSTC-AS, SA 18403 4391 347 23 FPT-AS-AP FPT Telecom Company, VN 7155 4168 287 88 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 10059 9985 CHINAMOBILE-CN China Mobile Communications Grou 12479 7628 7483 UNI2-AS, ES 16509 10812 7006 AMAZON-02, US 7545 5831 5173 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4951 4877 ERX-CERNET-BKB China Education and Research Net 39891 4602 4544 ALJAWWALSTC-AS, SA 18403 4391 4368 FPT-AS-AP FPT Telecom Company, VN 7155 4168 4080 VIASAT-SP-BACKBONE, US 11492 4629 4074 CABLEONE, US 7552 3990 3965 VIETEL-AS-AP Viettel Group, VN 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 203727 UNALLOCATED 5.42.92.0/24 215826 PARTNER-HOSTING-LTD, GB 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, 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 54338 UNALLOCATED 8.33.241.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.137.192.0/24 Origin: 31798 DATACITY, CA 23.137.192.0/24 Transit: 21949 BEANFIELD, CA 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.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, 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:16 /10:36 /11:92 /12:295 /13:577 /14:1171 /15:2063 /16:13225 /17:8275 /18:13772 /19:24636 /20:44744 /21:52116 /22:111842 /23:100518 /24:587061 /25:723 /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 6675 7628 UNI2-AS, ES 8151 5708 11506 UNINET, MX 11492 3543 4629 CABLEONE, US 6327 3397 3602 SHAW, CA 39891 3364 4602 ALJAWWALSTC-AS, SA 7155 3112 4168 VIASAT-SP-BACKBONE, US 22773 2560 3426 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2222 10812 AMAZON-02, US 10620 2175 3546 Telmex Colombia S.A., CO 30036 2142 2477 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:1530 3:481 4:8 5:4503 6:163 7:6 8:1513 9:1 11:172 12:1422 13:372 14:2427 15:328 16:264 17:363 18:891 20:409 21:4 22:188 23:6887 24:2646 25:2 27:2577 29:19 31:2784 32:47 34:66 35:140 36:2365 37:4527 38:8612 39:918 40:150 41:4120 42:2069 43:2448 44:332 45:17554 46:4633 47:299 49:2015 50:1861 51:579 52:1577 54:318 55:950 56:8 57:221 58:2255 59:1266 60:1082 61:2742 62:2775 63:1825 64:5445 65:2269 66:4665 67:3011 68:1292 69:3985 70:1141 71:567 72:2835 74:2785 75:1621 76:616 77:2556 78:1865 79:1642 80:2208 81:2022 82:1702 83:1375 84:1759 85:3090 86:1010 87:2367 88:1256 89:4311 90:669 91:8247 92:2589 93:2804 94:3798 95:4281 96:1268 97:316 98:1061 99:737 100:74 101:1172 102:3370 103:32298 104:4460 105:704 106:995 107:2396 108:1169 109:3973 110:2175 111:3323 112:2061 113:1777 114:1906 115:2107 116:1985 117:2679 118:2872 119:1989 120:1902 121:1411 122:2710 123:2175 124:1635 125:2865 126:64 128:1392 129:943 130:1225 131:1841 132:820 133:444 134:1515 135:306 136:1203 137:1109 138:2831 139:1511 140:1456 141:1441 142:1755 143:1605 144:1031 145:372 146:2084 147:2036 148:2541 149:2816 150:1060 151:1367 152:2104 153:500 154:6549 155:1501 156:2470 157:1823 158:1197 159:2457 160:3130 161:1729 162:3565 163:1757 164:1937 165:2140 166:1318 167:1833 168:4044 169:783 170:4919 171:1053 172:3917 173:3086 174:905 175:1246 176:3458 177:4804 178:3597 179:2200 180:2443 181:3901 182:3321 183:2055 184:2252 185:21104 186:5013 187:4254 188:4189 189:4056 190:9618 191:1533 192:11079 193:9259 194:7586 195:5417 196:3229 197:2987 198:6044 199:8069 200:8109 201:6339 202:10523 203:10388 204:4582 205:3691 206:4478 207:3667 208:4134 209:5139 210:4777 211:2673 212:4461 213:3674 214:1070 215:62 216:6592 217:2930 218:1398 219:561 220:2052 221:1047 222:876 223:2265 End of report

1 0

is it common to proxy register route objects for the purpose of grouping them for use in an as-set
by Steven Wallace 27 Sep '24

27 Sep '24

Greeting, One of the DDoS mitigation providers we work with creates proxy route objects for its customers’ prefixes. These route objects specify a common origin ASN rather than the actual origin ASN that would be seen in routing tables. Their rationale is to bind the prefixes to a single ASN, allowing the entire set of customer routes to be announced via an as-set. Is this a common approach? Just curious. thanks, steve Steven Wallace Director - Routing Integrity Internet2 ssw(a)internet2.edu

4 3

Question about the use of NO_EXPORT in BGP route announcements
by Sriram, Kotikalapudi (Fed) 25 Sep '24

25 Sep '24

For some IETF work in progress related to Source Address Validation (SAV), it is useful to know the purposes for which NO_EXPORT may be attached to routes announced in BGP, especially towards transit providers? I know it makes sense for an AS to announce an aggregate less-specific prefix to transit providers and peers without NO_EXPORT while announcing some more-specific prefixes (subsumed under the aggregate) with NO_EXPORT towards customer ASes. But are there good reasons when an AS might announce a prefix (route) to a transit provider with NO_EXPORT attached? The IP address space in consideration here is meant to have global reachability. Sriram

12 13

virtual nanog 92?
by michael brooks - ESC 25 Sep '24

25 Sep '24

Hello NANOG- Am I just missing the virtual option for attending NANOG 92? or is this simply not an option this time around? michael brooks Sr. Network Engineer Adams 12 Five Star Schools michael.brooks(a)adams12.org :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: "flying is learning how to throw yourself at the ground and miss" -- <https://www.adams12.org/> -- This is a staff email account managed by Adams 12 Five Star Schools. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender.

2 2

Lumen Contact
by Livingood, Jason 25 Sep '24

25 Sep '24

Trying to find a Lumen network ops contact – trying to run an operational incident to ground. If you are from Lumen and reading this • please ping Kari Collins (Kari_Collins(a)cable.comcast.com<mailto:Kari_Collins@cable.comcast.com>). Thx!

1 0

NANOG 92 Agenda is LIVE! + More
by Nanog News 24 Sep '24

24 Sep '24

*** NANOG 92 Agenda is LIVE!* ------------------------------------------------------------ *Sync Your Calendars Now!* 💚 Download saved talks to your calendar. All saved talks will also show on your appointment calendar. *VIEW NOW* https://nanog.org/events/nanog-92/agenda/ *** Game On! Register Now for NANOG 92 Hackathon* ------------------------------------------------------------ *Hack Your Way into Friends, Fun, + Level Up Your Skills!* Friday, 11 October - Intro/Infrastructure Tutorial/Team Formation Monday, 21 October + Tuesday, 22 October - Competition *MORE INFO* https://nanog.org/events/nanog-92-hackathon/ *** NANOG 92 Standard Registration Prices End Oct. 7* ------------------------------------------------------------ *Register Now + Save* *Join us for our 92nd community-wide gathering, happening October 21-23 in Toronto!* While the main hotel block is currently full, we're working on securing additional accommodations nearby. *Got questions?* Feel free to reach out at . Don't forget to check out our Keynote Speakers, things to do and see in Toronto, socials, conference kit, t-shirts, and more! *MORE INFO* https://nanog.org/events/nanog-92/

1 0

Call for participation in an online academic survey
by KANEMATSU Hiroaki 24 Sep '24

24 Sep '24

Hello NANOG community, My name is Hiroaki Kanematsu, a Ph.D. student at the Graduate School of Informatics, Nagoya University (Japan). I am conducting an online academic survey on professionalism and ethics among IT professionals. I have already conducted this survey in Japan among the IT engineers' community including JANOG, and would like to invite members of the NANOG community to participate and make comparisons. The survey URL is here: https://questant.jp/q/Y2LMFXGV The survey has a maximum of 55 questions. It will take 10-20 minutes to complete. And it will be open until the end of next month, September 30th (Monday) JST. I plan to publish the results of the survey in an academic paper and will provide some form of feedback to the NANOG community. Your cooperation will be greatly appreciated. Thank you, -- 兼松宏明 (Hiroaki Kanematsu) 名古屋大学大学院情報学研究科社会情報学専攻

1 1

Re: Hurricane Electric now supports ASPA for route filtering
by Lancheng 23 Sep '24

23 Sep '24

Hi Mike,>Hurricane Electric now uses ASPA to do hop by hop checking of AS paths >when deciding which routes to accept when building prefix filters. >Here is an example of a route failing the ASPA check. >44.31.69.0/24,rejected,AS path 4635 9002 945 7480 38254 38254 38254 >38254 38254 ASPA record exists for 7480 and 945 is not listed as a provider. >44.31.73.0/24,rejected,AS path 4635 9002 945 7480 ASPA record exists for >7480 and 945 is not listed as a provider. Thank you for doing and sharing this work. I am interested in this ASPA-invalid example and have a few questions. Q1: Has this example been sent to the network operator of AS 7480? A confirmation from 7480 would help us understand the reasons behind, e.g., a route leak or forgetting list 945 as a provider in the ASPA.Q2: I would like to do some ASPA-based verification analysis as well. I do not operate a network or a router, so I need to download ASPA data from public sources by myself. Do you know where I can download ASPA objects and the payload?>I'm sure Job will be able to give much better or more accurate guidance regarding ASPA software, protocols, and terminology.I copies this email to Job as well :-)Best,Lancheng

4 3

Re: RFC 9234 route leak prevention in the wild!
by Marinho Barcellos 21 Sep '24

21 Sep '24

Might have been this one? Light, Camera, Actions: characterizing the usage of IXPs’ action BGP communities https://researchcommons.waikato.ac.nz/server/api/core/bitstreams/4ed80bc4-c… Cheers, Marinho. > Message: 1 > Date: Wed, 18 Sep 2024 09:00:50 -0300 > From: Douglas Fischer <fischerdouglas(a)gmail.com> > To: Jon Lewis <jlewis(a)lewis.org> > Cc: Job Snijders <job(a)fastly.com>, nanog(a)nanog.org > Subject: Re: RFC 9234 route leak prevention in the wild! > Message-ID: > <CAKEr4RQE+DrsGGLEK6eFOVMo4xaJhKGcvRvn9EzNRBrJ+Dw3RA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Em qui., 5 de set. de 2024 ?s 14:35, Jon Lewis <jlewis(a)lewis.org> escreveu: > >> >> This may well be intentional >> > In addition to their own intention, they should ask if the other side > agrees with that. > > I don't remember which research paper compiled this. > But the top 5 ASNs targeted by the no_export_to<asn> BGP communities at IXP > Route-Servers say a lot about who mostly causes this type of problem. > > -- > Douglas Fernando Fischer > Eng? de Controle e Automa??o >

1 0

Retirement of FTP protocol support at ARIN? (was: [ARIN-consult] Consultation for the Retirement of FTP Protocol Use at ARIN)
by John Curran 21 Sep '24

21 Sep '24

NANOGers - ARIN has opened a consultation on removing support for FTP as an access method (in preference to HTTP/HTTPS) for our data archive – please see the attached consultation and provide feedback to the arin-consult mailing list if you have strong opinions on such a change. Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net> Subject: [ARIN-consult] Consultation for the Retirement of FTP Protocol Use at ARIN Date: September 20, 2024 at 3:16:23 PM EDT To: <arin-consult(a)arin.net> ARIN is seeking feedback from the community (https://arin.net/participate/community/acsp/consultations/2024/2024-5/) on retiring FTP protocol support, which serves data from ftp.arin.net. ARIN has operated an FTP protocol service for various reports and templates since its inception. All the data that is currently provided via FTP is also available over HTTP and HTTPS. ARIN is working to remove redundant and seldom-used services to allow future efforts to focus on the improvement of core services, reduce residual technical debt, and increase our security posture. Removing the FTP protocol aligns with these objectives. ARIN will not remove the data or change the existing directory structure. HTTP/HTTPS transport will continue to reference the data as it does today. ARIN intends to remove FTP protocol support on or after 31 March 2025. We are interested in knowing: - If there are ARIN customers who have a reliance on FTP that cannot be satisfied by obtaining data from ARIN via HTTP/HTTPS? - Does setting the date for 31 March 2025 provide sufficient time for customers who use FTP to move to HTTP/HTTPS? Please provide comments to arin-consult(a)arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult. This consultation will remain open until 5:00 PM ET on 4 October. ARIN seeks clear direction through community input, so your feedback is important. This information will help with our planning and decision making. Thank you for your continued support to improve ARIN’s services. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-Consult

1 0