- NANOG - lists.nanog.org

Add communities on direct routes in Juniper
by Stanislav Datskevych 16 Oct '23

16 Oct '23

Dear all, Is there a way to add BGP communities on direct (interface) routes in Junipers? The task looks to be simple but the solution eludes me. In Cisco/Arista, for example, I could use "network 192.0.2.0/24 route-map <SOME_MAP_THAT_ADDS_COMMUNITIES>". In Juniper it seems to be impossible. I even tried putting interface-routes into rib-group with an import policy. But it seems the import policy only works on importing routes into Secondary routing tables (e.g. inet.50), and not into the Primary one (inet.0). I know it's possible to add communities on later stage while announcing networks to peers, in [protocols bgp group <name> export]. But I'd better slap the community on the routes right when they're imported into RIB, not when they announced to peers. Thanks in advance.

5 4

transit and peering costs projections
by Dave Taht 16 Oct '23

16 Oct '23

This set of trendlines was very interesting. Unfortunately the data stops in 2015. Does anyone have more recent data? https://drpeering.net/white-papers/Internet-Transit-Pricing-Historical-And-… I believe a gbit circuit that an ISP can resell still runs at about $900 - $1.4k (?) in the usa? How about elsewhere? ... I am under the impression that many IXPs remain very successful, states without them suffer, and I also find the concept of doing micro IXPs at the city level, appealing, and now achievable with cheap gear. Finer grained cross connects between telco and ISP and IXP would lower latencies across town quite hugely... PS I hear ARIN is planning on dropping the price for, and bundling 3 BGP AS numbers at a time, as of the end of this year, also. -- Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html Dave Täht CSO, LibreQos

12 19

FCC and CISA host roundtable on Alerting Security Oct 30 2023
by Sean Donelan 16 Oct '23

16 Oct '23

The Federal Communications Commission’s Public Safety and Homeland Security Bureau (PSHSB), together with the Cybersecurity and Infrastructure Security Agency (CISA)’s Emergency Communications Division, will host a public roundtable on the cybersecurity of the nation’s public alert and warning systems. The roundtable will start at 9:30 a.m. EDT on Monday, October 30, 2023. This event will focus on cybersecurity in alerting, risk management frameworks as well as the cost and benefits of implementing these in incident reporting for alerting. https://www.fcc.gov/document/fcc-and-cisa-host-alerting-security-roundtable…

1 0

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc
by tim＠pelican.org 15 Oct '23

15 Oct '23

On Friday, 13 October, 2023 16:04, "Laura Smith via NANOG" <nanog(a)nanog.org> said: > RIPE could do the same. And some might argue that it is easier for RIPE because > all we are asking is for a valid abuse contact, so its not like Nominet who have > to verify e.g. registrant company ID numbers. They do. In previous lives, I've regularly been on the receiving end of assorted audit requests from RIPE, some of which are to do with contact details in the DB (particularly when they find unreachable ones), and some of which are confirming that number resources are still in use by the organisation and for the purpose for which they were issued. I think the original complaint was that RIPE don't act (or less so than ARIN) to block or otherwise deal with people who are mining the DB for contacts, despite that being an incentive to put "real" data in the DB - not than that they don't push for accurate data in the DB. Thanks, Tim.

4 3

Re: maximum ipv4 bgp prefix length of /24 ?
by Geoff Huston 14 Oct '23

14 Oct '23

> On 6 Oct 2023, at 6:13 am, Owen DeLong <owen(a)delong.com> wrote: > > Ratio of FIB to RIB is only part of the equation. > > IPv6 is NOT under the disaggregation pressure that IPv4 is under because there is no pressure (other than perhaps scarcity mentality from those that don’t properly understand IPv6) to dense-pack IPv6 assignments or undersize IPv6 allocations. > > Look at the difference in prefixes per ASN across the two tables and that tells a much grimmer story for IPv4 in terms of RIB growth vs. IPv6. hmm - IPv4 is at [1], IPv6 is at [2] Now I’m trying to understand what your grimmer story for IPv4 might be here Owen. Since 2005 the number of IPv4 FIB entries per origin AS has increased fropm 8 to 12 in the past 20 years - or a 50% increase. Over ther same period the number of IPv6 prefix advertisements per origin AS has increased from 1.5 to 6, or a fourfold increase. If anything, the IPv6 story appears to me to be a far greater cause for concern, but you may have a different interpretation of this data. Geoff [1] https://bgp.potaroo.net/cgi-bin/plota?file=%2fvar%2fdata%2fbgp%2fas2%2e0%2f… [2] https://bgp.potaroo.net/cgi-bin/plota?file=%2fvar%2fdata%2fbgp%2fv6%2fas2%2…

7 15

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 13 Oct '23

13 Oct '23

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 Oct, 2023 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: 932715 Prefixes after maximum aggregation (per Origin AS): 354045 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 453796 Total ASes present in the Internet Routing Table: 74910 Prefixes per ASN: 12.45 Origin-only ASes present in the Internet Routing Table: 64286 Origin ASes announcing only one prefix: 26511 Transit ASes present in the Internet Routing Table: 10624 Transit-only ASes present in the Internet Routing Table: 457 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 991 Number of instances of unregistered ASNs: 994 Number of 32-bit ASNs allocated by the RIRs: 42829 Number of 32-bit ASNs visible in the Routing Table: 35227 Prefixes from 32-bit ASNs in the Routing Table: 176097 Number of bogon 32-bit ASNs visible in the Routing Table: 33 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 522 Number of addresses announced to Internet: 3052395776 Equivalent to 181 /8s, 239 /16s and 221 /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.5 Total number of prefixes smaller than registry allocations: 310528 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 247475 Total APNIC prefixes after maximum aggregation: 71042 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 240913 Unique aggregates announced from the APNIC address blocks: 98990 APNIC Region origin ASes present in the Internet Routing Table: 13684 APNIC Prefixes per ASN: 17.61 APNIC Region origin ASes announcing only one prefix: 4120 APNIC Region transit ASes present in the Internet Routing Table: 1815 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 24 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9008 Number of APNIC addresses announced to Internet: 771669632 Equivalent to 45 /8s, 254 /16s and 190 /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: 273641 Total ARIN prefixes after maximum aggregation: 123850 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 277405 Unique aggregates announced from the ARIN address blocks: 132133 ARIN Region origin ASes present in the Internet Routing Table: 19099 ARIN Prefixes per ASN: 14.52 ARIN Region origin ASes announcing only one prefix: 6960 ARIN Region transit ASes present in the Internet Routing Table: 1975 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4827 Number of ARIN addresses announced to Internet: 1277746944 Equivalent to 76 /8s, 40 /16s and 223 /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: 262125 Total RIPE prefixes after maximum aggregation: 123998 RIPE Deaggregation factor: 2.11 Prefixes being announced from the RIPE address blocks: 257257 Unique aggregates announced from the RIPE address blocks: 160279 RIPE Region origin ASes present in the Internet Routing Table: 28435 RIPE Prefixes per ASN: 9.05 RIPE Region origin ASes announcing only one prefix: 12092 RIPE Region transit ASes present in the Internet Routing Table: 3939 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11378 Number of RIPE addresses announced to Internet: 716376960 Equivalent to 42 /8s, 179 /16s and 11 /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: 118565 Total LACNIC prefixes after maximum aggregation: 28505 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 117504 Unique aggregates announced from the LACNIC address blocks: 49263 LACNIC Region origin ASes present in the Internet Routing Table: 11051 LACNIC Prefixes per ASN: 10.63 LACNIC Region origin ASes announcing only one prefix: 2712 LACNIC Region transit ASes present in the Internet Routing Table: 2344 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8876 Number of LACNIC addresses announced to Internet: 178466816 Equivalent to 10 /8s, 163 /16s and 48 /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: 29918 Total AfriNIC prefixes after maximum aggregation: 5954 AfriNIC Deaggregation factor: 5.02 Prefixes being announced from the AfriNIC address blocks: 39114 Unique aggregates announced from the AfriNIC address blocks: 12702 AfriNIC Region origin ASes present in the Internet Routing Table: 1795 AfriNIC Prefixes per ASN: 21.79 AfriNIC Region origin ASes announcing only one prefix: 627 AfriNIC Region transit ASes present in the Internet Routing Table: 342 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 31 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1138 Number of AfriNIC addresses announced to Internet: 107696384 Equivalent to 6 /8s, 107 /16s and 81 /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 9498 8730 43 CHINAMOBILE-CN China Mobile Communicati 7545 5714 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4941 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4210 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3596 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3327 1840 96 VNPT-AS-VN VNPT Corp, VN 9498 3211 495 249 BBIL-AP BHARTI Airtel Ltd., IN 7552 2944 1330 20 VIETEL-AS-AP Viettel Group, VN 24560 2545 850 381 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2540 11270 601 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 9188 11009 3251 AMAZON-02, US 11492 4538 301 671 CABLEONE, US 7155 4172 288 100 VIASAT-SP-BACKBONE, US 6327 3546 1319 66 SHAW, CA 22773 3525 3055 300 ASN-CXA-ALL-CCI-22773-RDC, US 749 3161 54958 2413 DNIC-AS-00749, US 367 3077 3857 1441 DNIC-ASBLK-00306-00371, US 16625 3007 1399 2296 AKAMAI-AS, US 396982 2701 3597 397 GOOGLE-CLOUD-PLATFORM, US 7018 2507 23615 1569 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 7397 1713 145 UNI2-AS, ES 39891 4897 290 61 ALJAWWALSTC-AS, SA 20940 4093 3398 153 AKAMAI-ASN1, NL 8551 3448 368 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 9009 3077 275 1502 M247, RO 12389 2970 2295 915 ROSTELECOM-AS, RU 34984 2334 362 594 TELLCOM-AS, TR 58224 1714 922 546 TCI, IR 13188 1606 100 27 TRIOLAN, UA 8452 1521 1852 15 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 11852 3378 601 UNINET, MX 10620 3538 504 860 Telmex Colombia S.A., CO 13999 2414 332 626 Mega Cable, S.A. de C.V., MX 11830 2004 369 64 Instituto Costarricense de Electricidad 28573 1333 2324 232 Claro NXT Telecomunicacoes Ltda, BR 3816 1297 770 196 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1295 344 508 Axtel, S.A.B. de C.V., MX 6147 1111 369 22 Telefonica del Peru S.A.A., PE 11664 1054 168 425 Techtel LMDS Comunicaciones Interactiva 26615 1039 2501 51 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 24863 1606 393 19 LINKdotNET-AS, EG 24835 1549 549 28 RAYA-AS, EG 36992 1358 1518 280 ETISALAT-MISR, EG 36903 1248 553 98 MT-MPLS, MA 29571 1044 67 45 ORANGE-COTE-IVOIRE, CI 36935 938 521 44 Vodafone-, EG 6713 551 1861 34 IAM-AS, MA 15399 535 55 51 WANANCHI-, KE 37342 489 32 1 MOVITEL, MZ 24757 479 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 11852 3378 601 UNINET, MX 9808 9498 8730 43 CHINAMOBILE-CN China Mobile Communicati 16509 9188 11009 3251 AMAZON-02, US 12479 7397 1713 145 UNI2-AS, ES 7545 5714 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4941 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4897 290 61 ALJAWWALSTC-AS, SA 11492 4538 301 671 CABLEONE, US 18403 4210 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4172 288 100 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 9498 9455 CHINAMOBILE-CN China Mobile Communications Grou 12479 7397 7252 UNI2-AS, ES 16509 9188 5937 AMAZON-02, US 7545 5714 5016 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4941 4866 ERX-CERNET-BKB China Education and Research Net 39891 4897 4836 ALJAWWALSTC-AS, SA 18403 4210 4185 FPT-AS-AP FPT Telecom Company, VN 7155 4172 4072 VIASAT-SP-BACKBONE, US 20940 4093 3940 AKAMAI-ASN1, NL 11492 4538 3867 CABLEONE, US 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 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, 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 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, 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:38 /11:101 /12:299 /13:581 /14:1193 /15:2060 /16:13486 /17:8319 /18:13869 /19:25191 /20:44498 /21:51626 /22:110461 /23:99321 /24:560903 /25:739 /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 6483 7397 UNI2-AS, ES 8151 5883 11852 UNINET, MX 39891 3632 4897 ALJAWWALSTC-AS, SA 11492 3451 4538 CABLEONE, US 6327 3356 3546 SHAW, CA 7155 3117 4172 VIASAT-SP-BACKBONE, US 8551 2925 3448 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2578 3525 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2157 2501 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2112 3538 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:2244 2:1441 3:266 4:5 5:4367 6:137 7:6 8:1536 9:1 11:172 12:1500 13:376 14:2317 15:303 16:200 17:367 18:661 20:305 21:4 22:188 23:6462 24:2526 25:2 27:2528 29:19 31:2545 32:78 34:26 35:117 36:1995 37:4544 38:5423 39:865 40:143 41:4006 42:2033 43:2307 44:324 45:16660 46:4306 47:371 49:1845 50:1891 51:583 52:1595 54:394 55:950 56:5 57:127 58:1858 59:1180 60:1005 61:2521 62:2681 63:1915 64:5656 65:2347 66:5005 67:3040 68:1346 69:4136 70:1188 71:639 72:2946 74:2627 75:1566 76:636 77:2299 78:1827 79:3002 80:2091 81:1829 82:1530 83:1311 84:1576 85:3072 86:757 87:2013 88:1209 89:3931 90:624 91:7858 92:2064 93:2633 94:3554 95:4076 96:1301 97:316 98:1084 99:735 100:91 101:1053 102:2871 103:32162 104:4744 105:578 106:918 107:2723 108:1143 109:4244 110:2140 111:3192 112:2061 113:1817 114:1701 115:1982 116:1919 117:2471 118:2698 119:1972 120:1808 121:1203 122:2620 123:2221 124:1624 125:2598 128:1458 129:925 130:1047 131:1970 132:824 133:408 134:1782 135:304 136:909 137:977 138:2662 139:1607 140:1304 141:1324 142:1524 143:1527 144:1013 145:348 146:1962 147:1615 148:2468 149:2336 150:879 151:1234 152:1847 153:524 154:5129 155:1394 156:2013 157:1346 158:1053 159:2200 160:2638 161:1595 162:3523 163:1621 164:1715 165:1837 166:1077 167:1741 168:3843 169:797 170:4614 171:947 172:3793 173:2982 174:987 175:1183 176:3790 177:4477 178:3563 179:2145 180:2462 181:3516 182:3416 183:1976 184:2278 185:20627 186:4674 187:4171 188:4163 189:3885 190:9308 191:1380 192:10970 193:8966 194:7299 195:5231 196:3116 197:2484 198:6023 199:6253 200:8018 201:6164 202:10575 203:10022 204:4547 205:3705 206:4391 207:3515 208:4131 209:4931 210:4496 211:2541 212:4277 213:3398 214:1114 215:70 216:6727 217:2774 218:1305 219:579 220:2033 221:984 222:843 223:2180 End of report

1 0

ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc
by Eric Kuhnke 13 Oct '23

13 Oct '23

Is anyone else receiving spam from this organization? Based on the contents of the cold solicitations they are sending us, and the addresses being sent to, they have scraped ARIN WHOIS data for noc and abuse POC contact info and recent ipv4 block transfers. It's trivially easy to block their entire domain at the mail server level, of course...

11 13

Re: maximum ipv4 bgp prefix length of /24 ?
by Mark Andrews 12 Oct '23

12 Oct '23

> On 13 Oct 2023, at 08:31, scott <surfer(a)mauigateway.com> wrote: > > > > > On 10/11/23 7:47 PM, Mark Andrews wrote: >> Virtually no home network on the planet has fully functional IPv4 available to it. > > > Hawaiian Telcom customers have it. No blocks at all. So they don’t use NAT? The internet is a peer-to-peer network. NAT breaks that. But I can’t reach IPv6 devices on the Internet from my IPv4 device without a transition box is no different to I can’t reach IPv4 devices on the Internet from my IPv4 device because PNAT *is* a transition device. It’s a bogus complaint and I’m calling it out. > scott -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

2 2

Re: maximum ipv4 bgp prefix length of /24 ?
by Willy Manga 12 Oct '23

12 Oct '23

Hi. On 06/10/2023 16:00, nanog-request(a)nanog.org wrote: > From: Matthew Petach<mpetach(a)netflight.com> >[...] >> The IPv6 FIB is under the same pressure from more specifics. Its taken 20 >> years to get there, but the IPv6 FIB is now looking stable at 60% opf the >> total FIB size [2]. For me, thats a very surprising outcome in an >> essentially unmanaged system. >> >> >> Were you expecting it to be lower than IPv4? >> >> Mark. >> > I've dug through the mailman mirror on nanog.org, and there's currently no > post by Geoff Huston saying that: > https://community.nanog.org/search?q=geoff%20huston%20order%3Alatest I read (and send) NANOG emails through the digest emails sent once a day. I noticed the same thing . I assumed it was sent directly to Mark (or the mail will enter my next digest...) > But I'll play along. > > There's significantly less pressure to deaggregate IPv6 space right now, > because we don't see many attacks on IPv6 number resources. > Once we start to see v6 prefix hijackings, /48s being announced over /32 > prefixes to pull traffic, then I think we'll see IPv6 deaggregation > completely swamp IPv4 deaggregation. How about we educate each other to not assume you must deaggregate your prefix especially with IPv6? I see 'some' (it's highly relative) networks on IPv4, they 'believe' they have to advertise every single /24 they have. And when they start with IPv6, they replicate the same mindset with a tons of /48 . You can imagine what will happen of course. A better alternative IMHO is to take advantage to the large prefix range and advertise a sub-aggregate when necessary. But absolutely not each end-node or customer prefix. -- Willy Manga @ongolaboy https://ongola.blogspot.com/

6 16

constraining RPKI Trust Anchors
by Job Snijders 12 Oct '23

12 Oct '23

Dear all, Two weeks ago AFRINIC was placed under receivership by the Supreme Court of Mauritius. This event prompted me to rethink the RPKI trust model and associated risk surface. The RPKI technology was designed to be versatile and flexible to accommodate a myriad of real-world deployment scenarios including multiple trust anchors existing, inter-registry transfers, multiple transports, and permissionless innovation for signed objects, for example. All good and well ... but ofcouse there is a fine print. :-) Over the years various people have expressed astonishment about each RIR having issued so-called 'all-resources' (0.0.0.0/0 + ::/0) trust anchor certificates, but this aspect often is misunderstood: the risk is not necessarily in the listing of 'all-resources' itself, it is in the RIR being able to issue an 'all-resources' certificate in the first place. RPKI trust anchor operators indeed can voluntarily reduce the scope of subordinate Internet Number Resources, but just as easily increase the scope of their authority. In other words, a trust anchor cannot truly constrain itself. Upon reconsideration on how exactly RPKI hooks into the real world; I concluded trust anchors do not require unbounded trust in order to provide constructive services in the realm of BGP routing security. Some examples: ARIN does not support inter-RIR IPv6 transfers, so it would not make any sense to see a ROA subordinate to ARIN's trust anchor covering RIPE-managed IPv6 space. Conversely, it wouldn't make sense to observe a ROA covering ARIN-managed IPv6 space under APNIC's, LACNIC's, or RIPE's trust anchor - even if a cryptographically valid certificate path existed. Along these lines AFRINIC doesn't support inter-RIR transfers of any kind; and none of the RIRs have authority over private resources like 10.0.0.0/8 or AS 65535. It seems feasible to paint constraints around RPKI trust anchors in broad strokes. Over the last two weeks I've diligently worked with Theo Buehler to research RIR transfer policies, untangle the history of the IANA->RIR and RIR->RIR allocation spaghetti, design & implement a maintainable constraints mechanism for rpki-client(8), and publicly document the concept of applying operator-defined policy to derived trust arcs. Please take a moment to read https://www.ietf.org/archive/id/draft-snijders-constraining-rpki-trust-anch… Your feedback is appreciated. Kind regards, Job

7 8