- NANOG - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 17 May '24

17 May '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 18 May, 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: 951216 Prefixes after maximum aggregation (per Origin AS): 361636 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 462147 Total ASes present in the Internet Routing Table: 75834 Prefixes per ASN: 12.54 Origin-only ASes present in the Internet Routing Table: 64987 Origin ASes announcing only one prefix: 26714 Transit ASes present in the Internet Routing Table: 10847 Transit-only ASes present in the Internet Routing Table: 524 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 60 Max AS path prepend of ASN ( 53153) 57 Prefixes from unregistered ASNs in the Routing Table: 987 Number of instances of unregistered ASNs: 989 Number of 32-bit ASNs allocated by the RIRs: 44485 Number of 32-bit ASNs visible in the Routing Table: 36440 Prefixes from 32-bit ASNs in the Routing Table: 186418 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 606 Number of addresses announced to Internet: 3027540096 Equivalent to 180 /8s, 116 /16s and 152 /24s Percentage of available address space announced: 81.8 Percentage of allocated address space announced: 81.8 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: 312849 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 254867 Total APNIC prefixes after maximum aggregation: 73891 APNIC Deaggregation factor: 3.45 Prefixes being announced from the APNIC address blocks: 247091 Unique aggregates announced from the APNIC address blocks: 101153 APNIC Region origin ASes present in the Internet Routing Table: 14165 APNIC Prefixes per ASN: 17.44 APNIC Region origin ASes announcing only one prefix: 4314 APNIC Region transit ASes present in the Internet Routing Table: 1905 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 32 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9555 Number of APNIC addresses announced to Internet: 761418368 Equivalent to 45 /8s, 98 /16s and 82 /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: 276396 Total ARIN prefixes after maximum aggregation: 124938 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 281065 Unique aggregates announced from the ARIN address blocks: 133839 ARIN Region origin ASes present in the Internet Routing Table: 19163 ARIN Prefixes per ASN: 14.67 ARIN Region origin ASes announcing only one prefix: 6971 ARIN Region transit ASes present in the Internet Routing Table: 1995 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 27 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4903 Number of ARIN addresses announced to Internet: 1267620352 Equivalent to 75 /8s, 142 /16s and 90 /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: 266514 Total RIPE prefixes after maximum aggregation: 126908 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 261332 Unique aggregates announced from the RIPE address blocks: 163916 RIPE Region origin ASes present in the Internet Routing Table: 28657 RIPE Prefixes per ASN: 9.12 RIPE Region origin ASes announcing only one prefix: 12135 RIPE Region transit ASes present in the Internet Routing Table: 3970 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 46 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11806 Number of RIPE addresses announced to Internet: 713922560 Equivalent to 42 /8s, 141 /16s and 152 /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: 121268 Total LACNIC prefixes after maximum aggregation: 29058 LACNIC Deaggregation factor: 4.17 Prefixes being announced from the LACNIC address blocks: 119506 Unique aggregates announced from the LACNIC address blocks: 49581 LACNIC Region origin ASes present in the Internet Routing Table: 11086 LACNIC Prefixes per ASN: 10.78 LACNIC Region origin ASes announcing only one prefix: 2641 LACNIC Region transit ASes present in the Internet Routing Table: 2415 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 60 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8971 Number of LACNIC addresses announced to Internet: 176910336 Equivalent to 10 /8s, 139 /16s and 112 /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: 31184 Total AfriNIC prefixes after maximum aggregation: 6175 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 41616 Unique aggregates announced from the AfriNIC address blocks: 13188 AfriNIC Region origin ASes present in the Internet Routing Table: 1842 AfriNIC Prefixes per ASN: 22.59 AfriNIC Region origin ASes announcing only one prefix: 653 AfriNIC Region transit ASes present in the Internet Routing Table: 356 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 31 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1205 Number of AfriNIC addresses announced to Internet: 107281664 Equivalent to 6 /8s, 100 /16s and 253 /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 9841 8743 67 CHINAMOBILE-CN China Mobile Communicati 7545 5638 777 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4933 4192 74 ERX-CERNET-BKB China Education and Rese 18403 4407 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3909 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 3731 507 261 BBIL-AP BHARTI Airtel Ltd., IN 7713 3583 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3289 1872 100 VNPT-AS-VN VNPT Corp, VN 24560 2795 864 379 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2291 11522 577 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 9916 11376 3544 AMAZON-02, US 11492 4616 306 604 CABLEONE, US 7155 4167 287 89 VIASAT-SP-BACKBONE, US 6327 3597 1320 79 SHAW, CA 174 3531 8774 869 COGENT-174, US 22773 3488 3041 233 ASN-CXA-ALL-CCI-22773-RDC, US 749 3224 54904 2476 DNIC-AS-00749, US 16625 3101 1318 2218 AKAMAI-AS, US 7018 2819 23659 1777 ATT-INTERNET4, US 367 2789 3442 1313 DNIC-ASBLK-00306-00371, 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 7766 1708 145 UNI2-AS, ES 39891 4758 286 60 ALJAWWALSTC-AS, SA 20940 3823 3396 133 AKAMAI-ASN1, NL 9009 3350 292 1657 M247, RO 12389 2989 2305 902 ROSTELECOM-AS, RU 8551 2638 368 35 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2345 362 581 TELLCOM-AS, TR 13188 1607 100 26 TRIOLAN, UA 212238 1587 114 1155 CDNEXT, GB 8452 1580 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 12199 3321 487 UNINET, MX 10620 3511 492 939 Telmex Colombia S.A., CO 13999 2540 353 663 Mega Cable, S.A. de C.V., MX 11830 2004 369 64 Instituto Costarricense de Electricidad 28573 1350 2314 252 Claro NXT Telecomunicacoes Ltda, BR 3816 1321 789 190 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 1183 176 443 Techtel LMDS Comunicaciones Interactiva 6503 1125 314 478 Axtel, S.A.B. de C.V., MX 6147 1085 369 22 Telefonica del Peru S.A.A., PE 26615 1074 2503 53 TIM SA, BR 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 1549 545 28 RAYA-AS, EG 24863 1502 389 20 LINKdotNET-AS, EG 36992 1373 1519 282 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 29571 1200 77 60 ORANGE-COTE-IVOIRE, CI 36935 935 521 42 Vodafone-, EG 6713 557 1861 35 IAM-AS, MA 15399 532 56 56 WANANCHI-, KE 37342 508 32 1 MOVITEL, MZ 36914 489 82 3 KENET-AS, 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 8151 12199 3321 487 UNINET, MX 16509 9916 11376 3544 AMAZON-02, US 9808 9841 8743 67 CHINAMOBILE-CN China Mobile Communicati 12479 7766 1708 145 UNI2-AS, ES 7545 5638 777 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4933 4192 74 ERX-CERNET-BKB China Education and Rese 39891 4758 286 60 ALJAWWALSTC-AS, SA 11492 4616 306 604 CABLEONE, US 18403 4407 347 23 FPT-AS-AP FPT Telecom Company, VN 7155 4167 287 89 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 9841 9774 CHINAMOBILE-CN China Mobile Communications Grou 12479 7766 7621 UNI2-AS, ES 16509 9916 6372 AMAZON-02, US 7545 5638 4964 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4933 4859 ERX-CERNET-BKB China Education and Research Net 39891 4758 4698 ALJAWWALSTC-AS, SA 18403 4407 4384 FPT-AS-AP FPT Telecom Company, VN 7155 4167 4078 VIASAT-SP-BACKBONE, US 11492 4616 4012 CABLEONE, US 7552 3909 3888 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 65536 DOCUMENT 5.102.30.0/24 65512 -Private Use AS-, ZZ 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 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, 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 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 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: 398208 RESERVED, ZZ 23.147.240.0/24 Transit: 19930 EQUINIX-EC-CH, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, 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:37 /11:94 /12:297 /13:577 /14:1169 /15:2050 /16:13271 /17:8260 /18:13761 /19:24738 /20:44279 /21:51773 /22:111560 /23:99295 /24:579294 /25:731 /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 6862 7766 UNI2-AS, ES 8151 6233 12199 UNINET, MX 11492 3525 4616 CABLEONE, US 39891 3440 4758 ALJAWWALSTC-AS, SA 6327 3393 3597 SHAW, CA 7155 3111 4167 VIASAT-SP-BACKBONE, US 22773 2585 3488 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2159 2504 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2137 3511 Telmex Colombia S.A., CO 16509 2122 9916 AMAZON-02, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2304 2:1515 3:348 4:6 5:4566 6:164 7:6 8:1515 9:1 11:172 12:1454 13:360 14:2410 15:318 16:211 17:366 18:766 20:375 21:4 22:188 23:6751 24:2719 25:2 27:2543 29:19 31:2589 32:48 34:60 35:134 36:2295 37:4486 38:7476 39:896 40:122 41:4083 42:2172 43:2374 44:314 45:17059 46:4488 47:307 49:1959 50:1902 51:576 52:1577 54:313 55:999 56:5 57:178 58:2093 59:1252 60:1027 61:2612 62:2681 63:1893 64:5518 65:2343 66:4690 67:2990 68:1321 69:4095 70:1186 71:583 72:2859 74:2595 75:1558 76:618 77:2486 78:1859 79:2518 80:2195 81:2016 82:1608 83:1335 84:1659 85:3153 86:859 87:2288 88:1251 89:4086 90:679 91:8129 92:2308 93:2702 94:3732 95:4191 96:1283 97:316 98:1034 99:742 100:72 101:1177 102:3284 103:32619 104:4795 105:677 106:957 107:2752 108:1151 109:4139 110:2137 111:3301 112:2071 113:1838 114:1795 115:2072 116:1903 117:2646 118:2812 119:1975 120:1793 121:1331 122:2698 123:2235 124:1629 125:2883 126:32 128:1476 129:937 130:1143 131:1836 132:802 133:412 134:1736 135:322 136:1010 137:1069 138:2817 139:1542 140:1392 141:1345 142:1574 143:1512 144:1015 145:365 146:2056 147:1927 148:2503 149:2758 150:1036 151:1329 152:2153 153:525 154:6494 155:1451 156:2284 157:1777 158:1152 159:2337 160:2655 161:1684 162:3558 163:1708 164:1653 165:2148 166:1173 167:1800 168:3924 169:800 170:4867 171:1040 172:3850 173:3043 174:893 175:1199 176:3682 177:4717 178:3715 179:2191 180:2361 181:3745 182:3429 183:1996 184:2263 185:20817 186:4952 187:4502 188:4075 189:4133 190:9418 191:1479 192:11006 193:9133 194:7512 195:5300 196:3164 197:2558 198:6050 199:7726 200:7980 201:6232 202:10497 203:10210 204:4595 205:3761 206:4483 207:3596 208:4159 209:5062 210:4664 211:2623 212:4325 213:3429 214:1070 215:49 216:6834 217:2989 218:1341 219:581 220:2044 221:1033 222:872 223:2247 End of report

1 0

Mailing list SPF Failure
by Scott Q. 17 May '24

17 May '24

Anyone else getting SPF failures on all messages sent to the list ? I see them all originating from 50.31.151.76 but nanog.org's SPF record doesn't list that as allowed.

11 20

FCC proposes Internet Routing Security Reporting Requirements
by Job Snijders 16 May '24

16 May '24

Dear all, FYI: https://docs.fcc.gov/public/attachments/DOC-402579A1.pdf Kind regards, Job

1 1

Meet NANOG's New Executive Director! N91 Agenda is LIVE! + More
by Nanog News 16 May '24

16 May '24

*Meet NANOG's New Executive Director!* *VIDEO - Interview with Jonathan Black * *Jonathan Black has been appointed NANOG Executive Director* In his new role, Jonathan will be responsible for the organization's operational management and will collaborate with the NANOG Board to refine, articulate, and implement NANOG's mission and strategic plan. Find out more about Jonathan's background + vision in a video interview with NANOG's content producer Elizabeth Drolet. *VIEW NOW * <https://nanog.org/stories/nanog-tv/meet-nanogs-new-executive-director/> *NANOG 91 Agenda is LIVE! * *Sync Your Calendars Now! * *All NANOG 91 programming is now available on the NANOG website. * 💚 Download saved talks to your calendar. All saved talks will also show on your appointment calendar. *VIEW NOW <https://nanog.org/events/nanog-91/agenda/>* *New NANOG 91 Conference Kit Available* *Share on your Social, Newsletter, Website, + More! * Help us spread the word about NANOG 91! All N91 materials, including messaging, logos, and graphics, needed to promote our next meeting are accessible on our website. Download and share with your community today! <https://nanog.org/events/nanog-91/conference-kit/> *VIEW NOW <https://nanog.org/events/nanog-91/conference-kit/>*

2 1

Q: is RFC3531 still applicable?
by Adam Thompson 16 May '24

16 May '24

Not an IPv6 newbie by any stretch, but we still aren't doing it "at scale" and some of you are, so... For a very small & dense (on 128-bit scales, anyway) network, is RFC3531 still the last word in IPv6 allocation strategies? Right now, we're just approaching it as "pick the next /64 in the range", as it all gets aggregated at the BGP border anyway, and internally if I really try hard, I might get to 200 subnets someday. Is there any justification for the labour in doing something more complex like center-allocation in my situation? Worrying about allocation strategies seems appropriate to me if you have 100,000 subnets, not 100. Opinions wanted, please. -Adam Adam Thompson Consultant, Infrastructure Services MERLIN 100 - 135 Innovation Drive Winnipeg, MB R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) https://www.merlin.mb.ca<https://www.merlin.mb.ca/> Chat with me on Teams<https://teams.microsoft.com/l/chat/0/0?users=athompson@merlin.mb.ca>

7 12

Re: Q: is RFC3531 still applicable?
by Willy Manga 15 May '24

15 May '24

. On 15/05/2024 16:00, nanog-request(a)nanog.org wrote: > Message: 11 > Date: Tue, 14 May 2024 20:12:31 +0000 > From: Mel Beckman<mel(a)beckman.org> > To: Adam Thompson<athompson(a)merlin.mb.ca> > Cc: nanog<nanog(a)nanog.org> > Subject: Re: Q: is RFC3531 still applicable? > Message-ID:<813ADB68-4F73-49CC-AB3F-9BE18707497D(a)beckman.org> > Content-Type: text/plain; charset="utf-8" > > I never could understand the motivation behind RFC3531. Just assign > /64s. A single /64 subnet has 18,446,744,073,709,551,616 host > addresses. It is enough. Period. With IPv6 when you think of assignment to end-user, it's better to think in terms of 'use case' rather than number of hosts within a single network. As a residential user I might have wifi, voip, TV, CCTV,,... each of them can use its own prefix. As a bare metal user in a datacenter , I might have different needs when I build any internal networks. As a corporate user, I think this one is the more obvious. The only end-user who might stick with a single /64 is - 1 smartphone - 1 VM -- Willy Manga

1 0

Re: Q: is RFC3531 still applicable?
by Willy Manga 15 May '24

15 May '24

Hi, On 15/05/2024 16:00, nanog-request(a)nanog.org wrote: > Message: 10 > Date: Tue, 14 May 2024 19:52:43 +0000 > From: Adam Thompson<athompson(a)merlin.mb.ca> > To: nanog<nanog(a)nanog.org> > Subject: Q: is RFC3531 still applicable? > Message-ID: > <YT3PR01MB10768B5A9FEFE157A78096F509BE32(a)YT3PR01MB10768.CANPRD01.PROD.OUTLOOK.COM> > > Content-Type: text/plain; charset="iso-8859-1" > > Not an IPv6 newbie by any stretch, but we still aren't doing it "at > scale" and some of you are, so... > > For a very small & dense (on 128-bit scales, anyway) network, is > RFC3531 still the last word in IPv6 allocation strategies? You can read this article [1] . It's a more 'contemporary' approach. 1. https://www.daryllswer.com/ipv6-architecture-and-subnetting-guide-for-netwo… -- Willy Manga

1 0

Small Internet border router options?
by Tom Samplonius 15 May '24

15 May '24

What are using for small campus border routers? So four to eight 10G ports with a FIB for full scale L3? Tom

11 10

NANOG 91: Keynote & Conference Kit Announcement 📢 + More
by Nanog News 14 May '24

14 May '24

*Announcing NANOG 91 Keynote! * *Juniper Networks' Kireeti Kompella Will Present "Network Digital Twin"* *SVP and Chief Engineer for the AWAN BU in Juniper Networks, Kompella, will discuss "digital twins" and how they are used in many contexts.* As networks ramp up on automation, this is a logical next step. This talk will describe what a network digital twin is, what form it could take, how it can be instantiated, what one can do with an NDT, and in what use cases an NDT becomes vital. *VIEW MORE * <https://nanog.org/events/nanog-91/> *Guest Blog: RPKI ROV Deployment Reaches Major Milestone!* *BGP Experts Kentik's Doug Madory + Fastly's Job Snijders Review the Latest RPKI ROV Deployment Metrics * *Why it's Worth Your Time:* For the first time in the history of RPKI (Resource Public Key Infrastructure), the majority of IPv4 routes in the global routing table, are covered by ROAs (Route Origin Authorizations) according to the NIST RPKI Monitor. IPv6 crossed this milestone late last year. *R <https://nanog.org/stories/articles/rpki-rov-deployment-reaches-major-milest…>EAD MORE <https://nanog.org/stories/articles/rpki-rov-deployment-reaches-major-milest…>* *NANOG 91 Conference Kit Available! * *Share on your Social, Newsletter, Website, + More! * *Help us spread the word about NANOG 91! *Our new NANOG 91 Conference Kit is available. Our website contains all N91 materials, including messaging, logos, and graphics, needed to promote our next meeting. Download and share with your community today! *VIEW NOW * <https://nanog.org/events/nanog-91/conference-kit/> *Don't Miss out on Hackathon! * *Sponsored by [Your Company Here - Email Us for Info]* Your opportunity to build relationships with global industry peers in a casual setting, boost your resume, + have fun at our upcoming meeting, NANOG 91! *GAME ON! * <https://nanog.org/events/nanog-91-hackathon/>

1 0

Re: On consistency and 192.0.0.0/24
by Jakob Heitz (jheitz) 14 May '24

14 May '24

RFC 5736 was obsoleted by RFC 6890. It says in part: 2.2.1. Information Requirements The IPv4 and IPv6 Special-Purpose Address Registries maintain the following information regarding each entry: … o Forwardable - A boolean value indicating whether a router may forward an IP datagram whose destination address is drawn from the allocated special-purpose address block between external interfaces. … That means that some IP addresses in the block 192.0.0.0/24 may be routable. So, I would not make this a bogon. A better way to filter IP routes is by policy, for example based upon IRR and RPKI records. Kind Regards, Jakob ---------- Original message ---------- Date: Tue, 14 May 2024 12:00:15 +0200 (CEST) From: borg(a)uu3.net [10] 192.0.0.0/24 reserved for IANA IPv4 Special Purpose Address Registry [RFC5736]. Complete registration details for 192.0.0.0/24 are found in [IANA registry iana-ipv4-special-registry]. Was RFC5736 obsoleted? I think not, so I would treat it as bogon. Its a nice tiny subnet for special purposes. I personaly use it as my Internal VM Net on my desktop for example. ---------- Original message ---------- From: John Kristoff <jtk(a)dataplane.org> To: NANOG <nanog(a)nanog.org> Subject: On consistency and 192.0.0.0/24 Date: Mon, 13 May 2024 16:18:47 -0500 As one to never let a good academic question go unasked... what is it about 192.0.0.0/24 that is or isn't a bogon. This doesn't seem so straightforward an answer to me, at least in theory. Although in practice it may already be decided whether one likes the answer or not. 192.0.0.0/24 was originally assigned to IANA for "protocol assignments" in IETF RFC 5736, and later added to the list of reserved / special use addresses in IETF RFC 6890 (aka BCP 153). There is a corresponding IPv6 block (2001::/23), but it has a significantly different history. Team Cymru's bogon list includes the v4 prefix. NLNOG's bogon filtering guide does not. When I asked Job about NLNOG's position he said: "I was unsure what this prefix??s future plans would be and erred on the side of caution and didn??t include this prefix in the NLNOG bogon list recommendations." The /24 as specified is not for "global" use, but some of the more specific assignments are or can be. See: <https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-speci…>. >From my cursory examination I can't find cases where the v4 prefix or more specifics have been publicly announced to any significant degree. This however is not the case for the IPv6 prefix (e.g., the AS112 project, Teredo). Maybe you'd say the /24 should be filtered, but not the more specifics that are deemed available for global use. That might be reasonable, except many reasonable people will filter small prefixes. IANA's language may have put any "do not filter" camp in a relatively weak position: "Address prefixes listed in the Special-Purpose Address Registry are not guaranteed routability in any particular local or global context." I can't remember hearing anyone complaining about bogon-related reachability problems with the aggregate IANA prefixes generally. Is there a strong case to make that ops should not bogon filter any addresses in these prefixes? At least with IPv4? What about for IPv6? John

4 3