- Test - lists.nanog.org

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 20 Sep '24

20 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

The Votes Are In! NANOG 92 T-Shirt Color Will Be... + More
by Nanog News 20 Sep '24

20 Sep '24

*Video — "Why NANOG?" Hear from a Newcomer * *We asked Newcomer ISOC's João Aguiar About His Experience* Newcomers bring fresh ideas and energy to the conversation, while seasoned members provide expertise and mentorship, fostering a dynamic exchange of knowledge. See what Internet Society's Aguiar had to say about his first experience at a NANOG meeting! *WATCH NOW <https://nanog.org/stories/nanog-tv/why-nanog-newcomer/>* *Revolutionizing Network Operations: It’s Time to Refresh How We Run Our Networks* *Guest Columnist Scott Robohn — TNOps: A Fresh Take on Community-Driven Network Operations and Beyond* *READ MORE <https://nanog.org/stories/articles/revolutionizing-network-operations-its-t…>* *Exciting News: We Have a Winner!* *We Can’t Wait to See You Rocking the New NANOG Gear at our Upcoming Meeting!* After tallying up all your votes, we’re thrilled to announce the winning color for the official NANOG t-shirt! Drumroll, please… *The winning color is NAVY.* Thank you to everyone who participated in the vote and helped us choose the t-shirt color for NANOG 92. *NANOG Board of Directors Election: Submit Your Support!* *Let Your Voice be Heard!* We’re excited to announce that six outstanding candidates are running for two open positions on the NANOG Board of Directors! As a valued NANOG member, your voice matters, and now is the time to get involved. You can submit Statements of Support <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…> for the candidates of your choice and help shape the future of NANOG. *VIEW MORE <https://nanog.org/members/elections/2024-board-candidates/>*

1 0

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

20 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 21 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: 961244 Prefixes after maximum aggregation (per Origin AS): 366028 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 466491 Number of IPv4 prefixes with a valid ROA: 403245 Number of IPv4 prefixes with an invalid ROA: 1218 Number of IPv4 prefixes with no ROA: 556781 Total ASes present in the Internet Routing Table: 76209 Prefixes per ASN: 12.61 Origin-only ASes present in the Internet Routing Table: 65292 Origin ASes announcing only one prefix: 26806 Transit ASes present in the Internet Routing Table: 10917 Transit-only ASes present in the Internet Routing Table: 525 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: 984 Number of instances of unregistered ASNs: 994 Number of 32-bit ASNs allocated by the RIRs: 45401 Number of 32-bit ASNs visible in the Routing Table: 37091 Prefixes from 32-bit ASNs in the Routing Table: 192402 Number of bogon 32-bit ASNs visible in the Routing Table: 49 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 544 Number of addresses announced to Internet: 3034385664 Equivalent to 180 /8s, 221 /16s and 13 /24s Percentage of available address space announced: 82.0 Percentage of allocated address space announced: 82.0 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 314420 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 257897 Total APNIC prefixes after maximum aggregation: 75592 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 249504 Unique aggregates announced from the APNIC address blocks: 100701 APNIC Region origin ASes present in the Internet Routing Table: 14355 APNIC Prefixes per ASN: 17.38 APNIC Region origin ASes announcing only one prefix: 4374 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: 9772 Number of APNIC addresses announced to Internet: 762308736 Equivalent to 45 /8s, 111 /16s and 232 /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: 280527 Total ARIN prefixes after maximum aggregation: 126097 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 284174 Unique aggregates announced from the ARIN address blocks: 135262 ARIN Region origin ASes present in the Internet Routing Table: 19155 ARIN Prefixes per ASN: 14.84 ARIN Region origin ASes announcing only one prefix: 6955 ARIN Region transit ASes present in the Internet Routing Table: 2009 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 28 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5005 Number of ARIN addresses announced to Internet: 1266822912 Equivalent to 75 /8s, 130 /16s and 47 /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: 267087 Total RIPE prefixes after maximum aggregation: 128847 RIPE Deaggregation factor: 2.07 Prefixes being announced from the RIPE address blocks: 263753 Unique aggregates announced from the RIPE address blocks: 167217 RIPE Region origin ASes present in the Internet Routing Table: 28741 RIPE Prefixes per ASN: 9.18 RIPE Region origin ASes announcing only one prefix: 12116 RIPE Region transit ASes present in the Internet Routing Table: 3970 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: 11999 Number of RIPE addresses announced to Internet: 723332480 Equivalent to 43 /8s, 29 /16s and 45 /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: 122407 Total LACNIC prefixes after maximum aggregation: 28416 LACNIC Deaggregation factor: 4.31 Prefixes being announced from the LACNIC address blocks: 120210 Unique aggregates announced from the LACNIC address blocks: 48510 LACNIC Region origin ASes present in the Internet Routing Table: 11159 LACNIC Prefixes per ASN: 10.77 LACNIC Region origin ASes announcing only one prefix: 2677 LACNIC Region transit ASes present in the Internet Routing Table: 2470 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: 9066 Number of LACNIC addresses announced to Internet: 177670656 Equivalent to 10 /8s, 151 /16s and 10 /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: 32342 Total AfriNIC prefixes after maximum aggregation: 6434 AfriNIC Deaggregation factor: 5.03 Prefixes being announced from the AfriNIC address blocks: 43059 Unique aggregates announced from the AfriNIC address blocks: 14337 AfriNIC Region origin ASes present in the Internet Routing Table: 1884 AfriNIC Prefixes per ASN: 22.86 AfriNIC Region origin ASes announcing only one prefix: 684 AfriNIC Region transit ASes present in the Internet Routing Table: 366 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 39 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1249 Number of AfriNIC addresses announced to Internet: 103953152 Equivalent to 6 /8s, 50 /16s and 51 /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 10053 8751 74 CHINAMOBILE-CN China Mobile Communication 7545 5766 840 660 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4950 4192 74 ERX-CERNET-BKB China Education and Resear 18403 4356 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3987 1331 25 VIETEL-AS-AP Viettel Group, VN 9498 3793 508 262 BBIL-AP BHARTI Airtel Ltd., IN 7713 3644 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3261 1841 105 VNPT-AS-VN VNPT Corp, VN 24560 2817 848 466 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 10736 11812 3762 AMAZON-02, US 11492 4643 309 546 CABLEONE, US 7155 4168 287 88 VIASAT-SP-BACKBONE, US 174 3939 8779 911 COGENT-174, US 6327 3602 1320 79 SHAW, CA 749 3483 55081 2706 DNIC-AS-00749, US 22773 3409 3035 188 ASN-CXA-ALL-CCI-22773-RDC, US 7018 3093 23685 1940 ATT-INTERNET4, US 16625 2842 1255 2121 AKAMAI-AS, US 396982 2827 3603 428 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 7636 1708 145 UNI2-AS, ES 39891 4602 278 58 ALJAWWALSTC-AS, SA 20940 3823 3395 129 AKAMAI-ASN1, NL 9009 3671 313 1876 M247, RO 12389 2937 2295 889 ROSTELECOM-AS, RU 34984 2332 357 583 TELLCOM-AS, TR 212238 1789 129 1325 CDNEXT, GB 13188 1607 100 26 TRIOLAN, UA 8452 1581 1852 14 TE-AS TE-AS, EG 8551 1449 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 11707 3255 494 UNINET, MX 10620 3543 494 935 Telmex Colombia S.A., CO 13999 2554 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 1322 782 194 COLOMBIA TELECOMUNICACIONES S.A. ESP, CO 11664 1176 278 33 Techtel LMDS Comunicaciones Interactivas 6503 1145 374 163 Axtel, S.A.B. de C.V., MX 6147 1102 369 22 Telefonica del Peru S.A.A., PE 22884 1068 98 372 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 24863 1609 389 16 LINKdotNET-AS, EG 24835 1606 593 29 RAYA-AS, EG 36992 1411 1519 282 ETISALAT-MISR, EG 29571 1341 85 63 ORANGE-COTE-IVOIRE, CI 36903 1249 554 96 MT-MPLS, MA 36935 975 523 48 Vodafone-, EG 6713 558 1861 35 IAM-AS, MA 36914 524 82 3 KENET-AS, KE 15399 510 57 58 WANANCHI-, KE 37342 425 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 11707 3255 494 UNINET, MX 16509 10736 11812 3762 AMAZON-02, US 9808 10053 8751 74 CHINAMOBILE-CN China Mobile Communication 12479 7636 1708 145 UNI2-AS, ES 7545 5766 840 660 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4950 4192 74 ERX-CERNET-BKB China Education and Resear 11492 4643 309 546 CABLEONE, US 39891 4602 278 58 ALJAWWALSTC-AS, SA 18403 4356 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 10053 9979 CHINAMOBILE-CN China Mobile Communications Grou 12479 7636 7491 UNI2-AS, ES 16509 10736 6974 AMAZON-02, US 7545 5766 5106 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4950 4876 ERX-CERNET-BKB China Education and Research Net 39891 4602 4544 ALJAWWALSTC-AS, SA 18403 4356 4333 FPT-AS-AP FPT Telecom Company, VN 11492 4643 4097 CABLEONE, US 7155 4168 4080 VIASAT-SP-BACKBONE, US 7552 3987 3962 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 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 46639 UNALLOCATED 8.38.73.0/24 3356 LEVEL3, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.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:37 /11:92 /12:295 /13:575 /14:1169 /15:2069 /16:13226 /17:8269 /18:13763 /19:24644 /20:44799 /21:52104 /22:111948 /23:100461 /24:587040 /25:721 /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 6680 7636 UNI2-AS, ES 8151 5873 11707 UNINET, MX 11492 3553 4643 CABLEONE, US 6327 3397 3602 SHAW, CA 39891 3364 4602 ALJAWWALSTC-AS, SA 7155 3112 4168 VIASAT-SP-BACKBONE, US 22773 2542 3409 ASN-CXA-ALL-CCI-22773-RDC, US 10620 2172 3543 Telmex Colombia S.A., CO 16509 2170 10736 AMAZON-02, US 30036 2169 2508 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2309 2:1528 3:475 4:8 5:4482 6:161 7:6 8:1514 9:1 11:172 12:1426 13:371 14:2424 15:328 16:259 17:362 18:888 20:408 21:4 22:188 23:6887 24:2682 25:2 27:2578 29:19 31:2737 32:47 34:66 35:140 36:2368 37:4526 38:8600 39:916 40:150 41:4143 42:2043 43:2447 44:329 45:17522 46:4646 47:298 49:1991 50:1877 51:579 52:1581 54:317 55:964 56:8 57:218 58:2252 59:1265 60:1076 61:2737 62:2773 63:1849 64:5434 65:2277 66:4663 67:3023 68:1335 69:3989 70:1134 71:568 72:2859 74:2787 75:1633 76:622 77:2557 78:1861 79:1625 80:2209 81:2015 82:1692 83:1380 84:1759 85:3105 86:999 87:2346 88:1257 89:4316 90:679 91:8259 92:2496 93:2764 94:3795 95:4286 96:1276 97:316 98:1070 99:737 100:73 101:1172 102:3393 103:32273 104:4451 105:705 106:993 107:2384 108:1169 109:3972 110:2148 111:3317 112:2059 113:1791 114:1900 115:2093 116:1987 117:2675 118:2868 119:1989 120:1899 121:1420 122:2709 123:2170 124:1635 125:2864 126:64 128:1375 129:942 130:1234 131:1840 132:819 133:444 134:1509 135:310 136:1207 137:1105 138:2841 139:1512 140:1454 141:1444 142:1756 143:1608 144:1030 145:372 146:2094 147:2043 148:2541 149:2807 150:1066 151:1364 152:2106 153:502 154:6543 155:1499 156:2464 157:1818 158:1194 159:2456 160:3089 161:1721 162:3567 163:1754 164:1943 165:2140 166:1311 167:1840 168:4066 169:786 170:4931 171:1053 172:3911 173:3101 174:903 175:1229 176:3455 177:4781 178:3608 179:2171 180:2443 181:3894 182:3321 183:2060 184:2251 185:21098 186:5000 187:4297 188:4186 189:4143 190:9615 191:1508 192:11078 193:9255 194:7565 195:5407 196:3201 197:2970 198:6047 199:8125 200:8165 201:6330 202:10537 203:10371 204:4608 205:3697 206:4493 207:3671 208:4186 209:5149 210:4773 211:2666 212:4459 213:3661 214:1067 215:62 216:6642 217:2942 218:1413 219:557 220:2042 221:1046 222:878 223:2259 End of report

1 0

Survey on Internet Traffic Engineering practices.
by Kévin Vermeulen 20 Sep '24

20 Sep '24

Hey Nanog, We are a group of researchers from LAAS-CNRS and UCLouvain. We are currently conducting a research study on inter-domain traffic engineering practices and their impact on the internet. We are reaching out to network operators to gather insights on practical implementations of inter-domain traffic engineering. Specifically, we are interested in understanding the timeframes and prefixes involved in traffic engineering efforts. If you have conducted inter-domain traffic engineering, could you kindly provide information about your traffic engineering practices. You can do so via our survey form https://forms.gle/2B6hW5Rs98rjiLLN7. Your participation would greatly contribute to our understanding of current practices and trends in network traffic engineering. We assure you that any information shared will be treated with strict confidentiality and used solely for research purposes. Any findings that will be published will be anonymized. For any questions please let us know. Best regards, Omar Darwich, Kevin Vermeulen, Cristel Pelsser

1 1

duke.edu DNS IPv6 does not work
by Seth Mattinen 19 Sep '24

19 Sep '24

Is there anyone from duke.edu on this list? I am having problems with IPv6 on one of their sub-delegations causing mail delays. Trying to go through the front door writes me off with "not our problem". dm.duke.edu. 21600 IN NS nameserver1.mc.duke.edu. dm.duke.edu. 21600 IN NS nameserver2.mc.duke.edu. ;; Received 135 bytes from 152.3.105.232#53(dns-auth-02.oit.duke.edu) in 76 ms nameserver1.mc.duke.edu has address 152.16.1.4 nameserver1.mc.duke.edu has IPv6 address 2620:0:691:dc50::4 nameserver2.mc.duke.edu has address 152.16.1.12 nameserver2.mc.duke.edu has IPv6 address 2620:0:691:dc57::12 Works on IPv4: ; <<>> DiG 9.10.3-P4-Debian <<>> MX dm.duke.edu @152.16.1.4 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4622 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; OPT=15: 00 12 ("..") ;; QUESTION SECTION: ;dm.duke.edu. IN MX ;; ANSWER SECTION: dm.duke.edu. 3600 IN MX 10 mx.oit.duke.edu. ;; AUTHORITY SECTION: dm.duke.edu. 86400 IN NS nameserver1.mc.duke.edu. dm.duke.edu. 86400 IN NS nameserver2.mc.duke.edu. ;; Query time: 77 msec ;; SERVER: 152.16.1.4#53(152.16.1.4) ;; WHEN: Thu Sep 19 06:37:13 PDT 2024 ;; MSG SIZE rcvd: 140 ; <<>> DiG 9.10.3-P4-Debian <<>> MX dm.duke.edu @152.16.1.12 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7136 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; OPT=15: 00 12 ("..") ;; QUESTION SECTION: ;dm.duke.edu. IN MX ;; ANSWER SECTION: dm.duke.edu. 3600 IN MX 10 mx.oit.duke.edu. ;; AUTHORITY SECTION: dm.duke.edu. 86400 IN NS nameserver2.mc.duke.edu. dm.duke.edu. 86400 IN NS nameserver1.mc.duke.edu. ;; Query time: 76 msec ;; SERVER: 152.16.1.12#53(152.16.1.12) ;; WHEN: Thu Sep 19 09:57:48 PDT 2024 ;; MSG SIZE rcvd: 140 Fails on IPv6: ; <<>> DiG 9.10.3-P4-Debian <<>> MX dm.duke.edu @2620:0:691:dc50::4 ;; global options: +cmd ;; connection timed out; no servers could be reached ; <<>> DiG 9.10.3-P4-Debian <<>> MX dm.duke.edu @2620:0:691:dc57::12 ;; global options: +cmd ;; connection timed out; no servers could be reached ~Seth

2 1

Looking for X's contact
by Jorge Lobo 19 Sep '24

19 Sep '24

Hi folks I'm looking for X's (former twitter) technical contact, we haven't no luck with mailing they noc. Their funny war in Brasil has some colateral issues in their users outside this country. Jorge Lobo AS6057

2 1

Cloudflare's rpki.json file is missing IPv4 ROAs longer than /24
by Steven Wallace 18 Sep '24

18 Sep '24

Greeting, Internet2 uses Cloudflare’s https://rpki.cloudflare.com/rpki.json as an alternate source for RPKI-ROA information. We recently discovered that this file omits IPv4 ROAs longer than /24. It would be helpful if it included all ROAs. Interestingly, Cloudflare’s web-based validator does include longer ROAs: https://rpki.cloudflare.com/?view=validator&validateRoute=1351_209.198.99.6… Cloudflare, any chance you could include all ROAs in this file? thanks, steve Steven Wallace Director - Routing Integrity Internet2 ssw(a)internet2.edu

5 4

RFC 9234 route leak prevention in the wild!
by Job Snijders 18 Sep '24

18 Sep '24

Dear all, I'd like to share an update on RFC 9234 deployment. RFC 9234 titled "BGP Open Policy" aka the "Only-To-Customer" (OTC) BGP Path Attribute is an anti-route-leak mechanism which is *NOT* based on RPKI! (yes ... routing security is more than just RPKI! :-) The basic idea of 9234 is that BGP routers (based on their role in the Gao-Rexford inter-domain routing model) attach a special BGP Path attribute, or take action based on the presence and contents of this BGP Path attribute - with the intention to constrain a route's propagation radius to just the downstream customer cone of the neighboring ASN. Most operators will intuitively understand that any route propagating through multiple IX route servers operated by different IXPs is a route leak: ``` IXP_1 IXP_2 / \ / \ / \ / \ ISP_A ISP_B ISP_C (receives) (leaker) (originates) ``` (figure 1. propagation from right to left; leak scenario) In the above example, ISP_A originates a route towards IXP_1's route servers, IXP_1 propagates the route to ISP_B (so far so good); but for one reason or another ISP_B subsequently continues propagation of the route towards IXP_2's route servers, who in turn propagate it to ISP_C. ISP_B is forwarding IP traffic between ISP_A and ISP_C for zero revenue. ISP_A and ISP_C are probably not expecting ISP_B to be in the middle. This situation can happen as a result of a misconfiguration in ISP_B's equipment, even when all participants use IRR & RPKI ROV to attempt to mitigate the worst routing incidents. What does it matter / impact ============================ Calgary-based YYCIX deployed RFC9234 support in late 2022/early 2023 using OpenBGPD; and FranceIX deployed support using BIRD in Q2 2024. Both IXPs configured their route servers to reject BGP routes that have an OTC attribute attached, and to attach an OTC attribute when propagating routes to the Route Server's peers. As it happens to be, currently (Mon Sep 2 12:26:50 UTC 2024) a small route leak is happening involving both YYCIX and FranceIX Route Servers via an ISP connected to both IXP's Route Servers; with the leak being stopped at YYCIX thanks to RFC 9234! Appendix A contains a table of leaked IPv4 routes. Let's zoom in on 1 entry: ``` $ bgpctl show rib 157.185.154.0/24 detail BGP routing table entry for 157.185.154.0/24 6939 38040 54994 Nexthop 206.126.225.20 (via 206.126.225.20) Neighbor 206.126.225.20 (216.218.252.194) Origin IGP, metric 1911, localpref 100, weight 0, ovs not-found, avs unknown, external, otc leak Last update: 11:58:08 ago Communities: 0:2906 0:16265 0:16276 0:18638 0:41690 0:48641 0:49029 Ext. Communities: ovs not-found Large Communities: 53339:11:1 53339:11:3 Aggregator: 54994 [163.171.131.254] OTC: 51706 ``` (figure 2. inspecting an leaked route using OpenBGPD's CLI) In figure 2. one can see the route is marked as 'otc leak', this was made possible because FranceIX's route server's attached the OTC attribute with the ASN value set to their Route Server's ASN (51706). ``` YYCIX FranceIX . x <adds OTC> \ . \ / \ ISP_A 6939_38040 54994 ``` (figure 3. right to left: real world example of blocked leak) In figure 3 AS 54994 originates 157.185.154.0/24 and propagates a route towards the FranceIX route servers. FranceIX accepts this route (probably because an IRR route object exists) and propagates it onward with the "Only-To-Customer" attribute set to 51706. The route is received by AS 38040, who appear to propagate the route to their upstream 6939. << An AS 38040 router is likely misconfigured! >> Then 6939 sends its customer's routes to the YYCIX route server, but the YYCIX route server recognizes that the route already passed through a 'valley' and thus considers this a leak; and blocks further propagation towards ISP_A. Impact with partial deployment ============================== RFC 9234 is an easy mechanism to configure and debug for both small & large network operators and IXP route server operators. In the above scenario YYCIX and FranceIX are likely the only 2 entities in the entire AS path which support RFC 9234; but we're already seeing leaks being blocked despite partial deployment! It's not hard to imagine that many IX-to-IX route leaks can be blocked with only the IXP operators themselves enabling RFC 9234 support. The world's most populair RS implementations (BIRD and OpenBGPD) already support RFC 9234! Tens of thousands of IX customers would enjoy the benefits of a few hundred IXPs taking action. RFC 9234 has no dependency on the RPKI, this means tha What can you do? ================ Just ask your vendors (your hardware routers and IXPs) to implement and deploy RFC 9234! :-) The more people ask, the more it'll bubble to the top of the priority list. The cost of implementing & deploying RFC 9234 is excellent bang for buck. Closing words ============= Shout out to our friends at FranceIX and MSK-IX for being amongst the first IXPs to deploy RFC 9234! Your effort helped reduce the potential impact of today's route leak! Kind regards, Job (YYCIX volunteer) Appendix A: ----------- Vantage point: YYCIX Route Server 1 (rs1.yycix.ca) Timestamp: Mon Sep 2 12:31:50 UTC 2024 Destination Prefix AS_PATH 102.164.129.0/24 6939 37613 6758 37649 i 102.164.139.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 102.164.140.0/24 6939 37613 6758 37649 i 102.164.141.0/24 6939 37613 6758 37649 i 102.164.182.0/24 6939 37613 6758 37649 i 154.65.33.0/24 6939 37613 6758 37649 i 154.65.34.0/24 6939 37613 6758 37649 i 154.65.35.0/24 6939 37613 6758 37649 i 154.65.36.0/24 6939 37613 6758 37649 i 154.65.37.0/24 6939 37613 6758 37649 i 154.65.38.0/24 6939 37613 6758 37649 i 154.65.39.0/24 6939 37613 6758 37649 i 154.72.35.0/24 6939 37613 37100 37027 37063 327721 i 157.185.151.0/24 6939 38040 54994 i 157.185.154.0/24 6939 38040 54994 i 163.171.164.0/24 6939 38040 54994 i 192.150.250.0/23 6939 4651 4618 4618 63529 4621 3836 i 196.50.8.0/24 6939 37613 6758 37649 i 196.50.9.0/24 6939 37613 6758 37649 i 196.50.11.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 196.50.13.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 196.50.14.0/24 6939 37613 6758 37649 i 2001:67c:15f4::/48 6939 41103 i 2401:c500:fd08::/48 6939 4637 38040 54994 i 2a01:53c0:ff03::/48 6939 4637 38040 54994 i 2a01:53c0:ff0f::/48 6939 4637 38040 54994 i 2a01:58c0::/32 6939 16347 42487 i 2a03:8920::/32 6939 41103 i 2a03:d602::/31 6939 16347 42487 i 2a03:d606::/31 6939 16347 42487 i 2a0d:ee00::/32 6939 16347 42487 i 2a0e:5b80::/29 6939 16347 42487 i 2a0e:e080::/32 6939 16347 42487 i 2a0f:c540::/29 6939 16347 42487 i

5 4

Layer 2 VPLS - Amsterdam - Singapore - LA (P2P) Multi Point to Point
by James Braunegg 17 Sep '24

17 Sep '24

Dear All I am looking for additional capacity as a Layer 2 VPLS service (Or similar) between AMS-01 EvoSwitch, SG1 Equinix Singapore and Core Site One Wilshire on a 10G port Latency between sites is important If you require any more information please just email me Please contact me off list Kindest Regards James Braunegg [cid:image001.png@01DB090F.F70AA130] 1300 769 972<tel:1300%20769%20972> / 0488 997 207<tel:1300%20769%20972> james.braunegg(a)micron21.com<mailto:james.braunegg@micron21.com> www.micron21.com/virtual-datacentre-tour <https://www.micron21.com/virtual-datacentre-tour> [cid:image002.png@01DB090F.F70AA130]<http://www.micron21.com/> [cid:image003.png@01DB090F.F70AA130]<https://www.facebook.com/micron21/> [cid:image004.png@01DB090F.F70AA130]<https://twitter.com/micron21> Follow us on m21status.com<https://m21status.com/> for important service and system updates. This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than the addressee. If you have received this message in error please return the message to the sender by replying to it and then delete the message from your computer.

1 0