October 2023 - NANOG - lists.nanog.org

APRICOT 2024: Call for Presentations
by Mark Tinka 11 Oct '23

11 Oct '23

APRICOT 2024 21st February - 1st March, Bangkok, Thailand https://2024.apricot.net CALL FOR PRESENTATIONS ================= The APRICOT 2024 Programme Committee is now seeking contributions for Presentations and Tutorials for the APRICOT 2024 Conference. We are looking for presenters who would: - Offer a technical tutorial on an appropriate topic; - Participate in the technical conference sessions as a speaker; - Convene and chair panel sessions of relevant topics; - Lead informal Birds of Feather break out sessions. Please submit on-line at: https://papers.apricot.net/user/login.php?event=186 CONFERENCE MILESTONES ---------------------------------- Call for Papers Opens: Now Outline Programme Published: As Papers Confirmed Final Deadline for Submissions: 29th January 2024 Final Program Published: 5th February 2024 Final Slides Received: 19th February 2024 *SLOTS ARE FILLED ON A FIRST COME, FIRST SERVED BASIS, REGARDLESS OF PUBLISHED DEADLINES* PROGRAMME CONTENT ----------------------------- The APRICOT Conference Programme consists of three parts, these being Tutorials, the Peering Forum, and Conference Sessions. Topics proposed must be relevant to Internet Operations and Technologies, for example: - IPv4 / IPv6 Routing and Operations - Routing Security, including RPKI and MANRS - Internet backbone operations - Peering, Interconnects and IXPs - Content Distribution Network technology & operations - Research on Internet Operations and Deployment - Network Virtualisation - Network Automation/Programming - Network Infrastructure security - IPv6 deployment on fixed and Wireless/Cellular networks - DNS / DNSSEC and KINDNS - Access and Transport Technologies - Technical application of Web 3.0, public blockchains and cryptocurrency - Content & Service Delivery and "Cloud Computing" - 400G ZR, ZR+ & Open ROADM - Submarine cables - ChatGPT CfP SUBMISSION --------------------- Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the submission will be rejected immediately. For work in progress, the most current information available at the time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Slides must be of original work, with all company confidential marks removed. Any marketing, sales and vendor proprietary content in a presentation is against the spirit of APRICOT and it is strictly prohibited. Note that proper credit must be given for all content taken from other sources. Evidence of plagiarism is grounds for rejection. Final slides are to be provided by the specified deadline for publication on the APRICOT website. Prospective presenters should note that the majority of speaking slots will be filled well before the final submission deadline. The PC may, at their discretion, retain a limited number of slots up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Every year we turn away submissions, due to filling up all available programme slots before the deadline. Presenters should endeavour to get material to the PC sooner rather than later. Any questions or concerns should be addressed to the Programme Committee Chairs by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mark Tinka, Achie Atienza & Mark Duffell APRICOT 2024 Programme Committee Chairs --

1 0

AT&T Business Center completely broken for months - is it the norm?
by Mirai Azayaka 10 Oct '23

10 Oct '23

Hi NANOG, Maybe this topic is better suited for the complaint department of AT&T but I just want to confirm if it's just me or it's just AT&T... So I'm a new customer of AT&T's DIA network and I haven't been able to make a payment since day one. (And it has been several months.) Just wondering if a completely broken internal billing system is normal... I only have limited experience with Hurricane Electric and Equinix before. Wondering if Verizon or Comcast is also broken like AT&T. Here are the issues I had with their system: - Clicking random links around the portal will give you HTTP 400 errors, sometimes. - I'm unable to add payment methods even after following the payment tutorial exactly. The portal consistently gives HTTP 413 errors. - Live chat doesn't work at all. Clicking the button returns HTTP 404 in my debugging console. - Extremely slow for some tasks which may result in a HTTP 408. The system feels like a collection of HTTP error codes... How can it be so broken? Are other ISP's internal billing systems broken like this? Looking for anecdotes / experiences. Azayaka

4 4

Re: Low to Mid Range DWDM Platforms
by Thomas Croghan 09 Oct '23

09 Oct '23

I did some work with their passive DWDM equipment. Everything was within spec and seemed to work fine for the year I was there after we deployed it. Actually being honest, we did all our light loss math based on FS's specs and we ended up having to use attenuators in one instance. So be certain to check the certification sheets when you get your product. On Oct 9, 2023 09:13, michael brooks - ESC <michael.brooks(a)adams12.org> wrote: >On the same topic, anyone have experience with the stuff from fs.com<https://urldefense.com/v3/__http://fs.com__;!!IR39LLzvxw!PGJ97ToHx5NZWWby4L…>? We use their patch cables, both SM and MM. Solid product, and good to work with (we have had them build custom-length cables). michael brooks Sr. Network Engineer Adams 12 Five Star Schools michael.brooks(a)adams12.org<mailto:michael.brooks@adams12.org> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: "flying is learning how to throw yourself at the ground and miss" On Fri, Oct 6, 2023 at 8:04 AM David Bass <davidbass570(a)gmail.com<mailto:davidbass570@gmail.com>> wrote: On the same topic, anyone have experience with the stuff from fs.com<https://urldefense.com/v3/__http://fs.com__;!!IR39LLzvxw!PGJ97ToHx5NZWWby4L…>? 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.

1 0

Spoofer Report for NANOG for Sep 2023
by CAIDA Spoofer Project 08 Oct '23

08 Oct '23

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Sep 2023: none inferred Source Address Validation issues inferred during Sep 2023: ASN Name First-Spoofed Last-Spoofed 3356 LEVEL3 2016-03-06 2023-09-11 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2023-09-24 20412 CLARITY-TELECOM 2016-09-30 2023-09-30 25787 ROWE-NETWORKS 2016-10-21 2023-09-30 11427 TWC-11427-TEXAS 2016-10-21 2023-09-26 10796 TWC-10796-MIDWEST 2016-10-24 2023-09-27 271 BCNET 2016-10-24 2023-09-23 852 ASN852 2017-04-16 2023-09-01 701 UUNET 2017-06-14 2023-09-29 18798 ENCORE-ASN 2017-10-09 2023-09-19 55016 IMPER-AS-1 2021-05-18 2023-09-26 46997 2021-12-22 2023-09-28 394414 E2WS 2022-05-08 2023-09-28 400517 2022-10-03 2023-09-27 12183 TALKIE-COMMUNICATIONS 2022-12-10 2023-09-27 41378 KirinoNET 2023-03-23 2023-09-29 3701 NERONET 2023-04-18 2023-09-27 400282 2023-04-27 2023-09-29 13693 NTS-ONLINE 2023-05-05 2023-09-02 46690 SNET-FCC 2023-05-20 2023-09-30 36687 WILINE 2023-08-02 2023-09-04 16557 COLOSOLUTIONS 2023-09-09 2023-09-12 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

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

06 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 07 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: 932315 Prefixes after maximum aggregation (per Origin AS): 353915 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 453446 Total ASes present in the Internet Routing Table: 74914 Prefixes per ASN: 12.45 Origin-only ASes present in the Internet Routing Table: 64301 Origin ASes announcing only one prefix: 26472 Transit ASes present in the Internet Routing Table: 10613 Transit-only ASes present in the Internet Routing Table: 456 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: 995 Number of instances of unregistered ASNs: 997 Number of 32-bit ASNs allocated by the RIRs: 42780 Number of 32-bit ASNs visible in the Routing Table: 35222 Prefixes from 32-bit ASNs in the Routing Table: 176100 Number of bogon 32-bit ASNs visible in the Routing Table: 34 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 526 Number of addresses announced to Internet: 3053552128 Equivalent to 182 /8s, 1 /16s and 130 /24s Percentage of available address space announced: 82.5 Percentage of allocated address space announced: 82.5 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: 310516 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 247120 Total APNIC prefixes after maximum aggregation: 71004 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 240693 Unique aggregates announced from the APNIC address blocks: 98970 APNIC Region origin ASes present in the Internet Routing Table: 13692 APNIC Prefixes per ASN: 17.58 APNIC Region origin ASes announcing only one prefix: 4112 APNIC Region transit ASes present in the Internet Routing Table: 1816 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9019 Number of APNIC addresses announced to Internet: 772799872 Equivalent to 46 /8s, 15 /16s and 253 /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: 273510 Total ARIN prefixes after maximum aggregation: 123860 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 277244 Unique aggregates announced from the ARIN address blocks: 131906 ARIN Region origin ASes present in the Internet Routing Table: 19090 ARIN Prefixes per ASN: 14.52 ARIN Region origin ASes announcing only one prefix: 6954 ARIN Region transit ASes present in the Internet Routing Table: 1963 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: 1277857536 Equivalent to 76 /8s, 42 /16s and 143 /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: 261988 Total RIPE prefixes after maximum aggregation: 123876 RIPE Deaggregation factor: 2.11 Prefixes being announced from the RIPE address blocks: 257012 Unique aggregates announced from the RIPE address blocks: 160127 RIPE Region origin ASes present in the Internet Routing Table: 28445 RIPE Prefixes per ASN: 9.04 RIPE Region origin ASes announcing only one prefix: 12074 RIPE Region transit ASes present in the Internet Routing Table: 3953 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: 11370 Number of RIPE addresses announced to Internet: 716284544 Equivalent to 42 /8s, 177 /16s and 162 /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: 118788 Total LACNIC prefixes after maximum aggregation: 28527 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 117763 Unique aggregates announced from the LACNIC address blocks: 49325 LACNIC Region origin ASes present in the Internet Routing Table: 11046 LACNIC Prefixes per ASN: 10.66 LACNIC Region origin ASes announcing only one prefix: 2709 LACNIC Region transit ASes present in the Internet Routing Table: 2332 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: 8869 Number of LACNIC addresses announced to Internet: 178476544 Equivalent to 10 /8s, 163 /16s and 86 /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: 29914 Total AfriNIC prefixes after maximum aggregation: 5957 AfriNIC Deaggregation factor: 5.02 Prefixes being announced from the AfriNIC address blocks: 39077 Unique aggregates announced from the AfriNIC address blocks: 12679 AfriNIC Region origin ASes present in the Internet Routing Table: 1795 AfriNIC Prefixes per ASN: 21.77 AfriNIC Region origin ASes announcing only one prefix: 623 AfriNIC Region transit ASes present in the Internet Routing Table: 340 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: 1137 Number of AfriNIC addresses announced to Internet: 107707648 Equivalent to 6 /8s, 107 /16s and 125 /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 9493 8730 44 CHINAMOBILE-CN China Mobile Communicati 7545 5733 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4936 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4223 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3594 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3336 1840 96 VNPT-AS-VN VNPT Corp, VN 9498 3195 498 252 BBIL-AP BHARTI Airtel Ltd., IN 7552 2940 1330 20 VIETEL-AS-AP Viettel Group, VN 4766 2540 11270 601 KIXS-AS-KR Korea Telecom, KR 24560 2531 850 381 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 9080 10987 3283 AMAZON-02, US 11492 4537 301 671 CABLEONE, US 7155 4177 288 100 VIASAT-SP-BACKBONE, US 6327 3546 1319 66 SHAW, CA 22773 3520 3054 297 ASN-CXA-ALL-CCI-22773-RDC, US 749 3163 54958 2415 DNIC-AS-00749, US 367 3022 3847 1419 DNIC-ASBLK-00306-00371, US 16625 3015 1418 2307 AKAMAI-AS, US 396982 2700 3597 396 GOOGLE-CLOUD-PLATFORM, US 30036 2498 359 372 MEDIACOM-ENTERPRISE-BUSINESS, 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 7386 1713 145 UNI2-AS, ES 39891 4897 290 61 ALJAWWALSTC-AS, SA 20940 4082 3398 153 AKAMAI-ASN1, NL 8551 3446 368 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 9009 3028 272 1501 M247, RO 12389 2971 2295 915 ROSTELECOM-AS, RU 34984 2334 362 594 TELLCOM-AS, TR 58224 1720 923 530 TCI, IR 13188 1606 100 27 TRIOLAN, UA 8452 1520 1852 16 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 11814 3378 601 UNINET, MX 10620 3534 504 858 Telmex Colombia S.A., CO 13999 2395 331 628 Mega Cable, S.A. de C.V., MX 11830 2006 369 64 Instituto Costarricense de Electricidad 28573 1331 2324 233 Claro NXT Telecomunicacoes Ltda, BR 3816 1297 766 191 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1293 344 507 Axtel, S.A.B. de C.V., MX 6147 1111 369 22 Telefonica del Peru S.A.A., PE 11664 1077 169 428 Techtel LMDS Comunicaciones Interactiva 26615 1035 2501 49 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 1535 549 28 RAYA-AS, EG 36992 1326 1516 283 ETISALAT-MISR, EG 36903 1248 553 98 MT-MPLS, MA 29571 1045 67 45 ORANGE-COTE-IVOIRE, CI 36935 938 521 44 Vodafone-, EG 6713 550 1861 34 IAM-AS, MA 15399 540 55 53 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 11814 3378 601 UNINET, MX 9808 9493 8730 44 CHINAMOBILE-CN China Mobile Communicati 16509 9080 10987 3283 AMAZON-02, US 12479 7386 1713 145 UNI2-AS, ES 7545 5733 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4936 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4897 290 61 ALJAWWALSTC-AS, SA 11492 4537 301 671 CABLEONE, US 18403 4223 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4177 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 9493 9449 CHINAMOBILE-CN China Mobile Communications Grou 12479 7386 7241 UNI2-AS, ES 16509 9080 5797 AMAZON-02, US 7545 5733 5035 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4936 4861 ERX-CERNET-BKB China Education and Research Net 39891 4897 4836 ALJAWWALSTC-AS, SA 18403 4223 4198 FPT-AS-AP FPT Telecom Company, VN 7155 4177 4077 VIASAT-SP-BACKBONE, US 20940 4082 3929 AKAMAI-ASN1, NL 11492 4537 3866 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:1196 /15:2064 /16:13502 /17:8315 /18:13881 /19:25207 /20:44503 /21:51603 /22:110347 /23:99093 /24:560815 /25:740 /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 6472 7386 UNI2-AS, ES 8151 5850 11814 UNINET, MX 39891 3632 4897 ALJAWWALSTC-AS, SA 11492 3450 4537 CABLEONE, US 6327 3356 3546 SHAW, CA 7155 3122 4177 VIASAT-SP-BACKBONE, US 8551 2923 3446 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2574 3520 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2155 2498 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2108 3534 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:2229 2:1431 3:265 4:5 5:4424 6:137 7:6 8:1538 9:1 11:172 12:1503 13:367 14:2330 15:304 16:197 17:368 18:658 20:296 21:4 22:188 23:6446 24:2520 25:2 27:2534 29:19 31:2546 32:78 34:25 35:117 36:2009 37:4540 38:5369 39:871 40:143 41:4018 42:2062 43:2297 44:324 45:16634 46:4300 47:371 49:1838 50:1889 51:584 52:1594 54:389 55:933 56:5 57:126 58:1854 59:1181 60:1003 61:2517 62:2689 63:1916 64:5673 65:2358 66:5004 67:3041 68:1344 69:4159 70:1192 71:666 72:2939 74:2631 75:1563 76:634 77:2303 78:1830 79:2992 80:2092 81:1829 82:1520 83:1311 84:1564 85:3111 86:764 87:2001 88:1203 89:3926 90:623 91:7843 92:2062 93:2623 94:3540 95:4069 96:1302 97:315 98:1084 99:732 100:90 101:1047 102:2884 103:32181 104:4744 105:577 106:915 107:2726 108:1138 109:4235 110:2138 111:3196 112:2065 113:1819 114:1694 115:1985 116:1904 117:2457 118:2689 119:1967 120:1806 121:1190 122:2615 123:2219 124:1621 125:2579 128:1455 129:925 130:1048 131:1982 132:818 133:408 134:1785 135:306 136:971 137:973 138:2633 139:1610 140:1294 141:1330 142:1522 143:1559 144:1009 145:349 146:1960 147:1596 148:2488 149:2321 150:877 151:1229 152:1861 153:523 154:5105 155:1391 156:2009 157:1346 158:1056 159:2199 160:2644 161:1593 162:3520 163:1617 164:1709 165:1853 166:1084 167:1747 168:3849 169:808 170:4662 171:922 172:3802 173:2971 174:984 175:1195 176:3776 177:4486 178:3547 179:2154 180:2455 181:3532 182:3405 183:1979 184:2273 185:20622 186:4720 187:4138 188:4162 189:3877 190:9324 191:1410 192:10984 193:8967 194:7315 195:5227 196:3116 197:2476 198:6033 199:6186 200:7995 201:6156 202:10548 203:10030 204:4553 205:3714 206:4401 207:3513 208:4151 209:4916 210:4500 211:2539 212:4276 213:3377 214:1112 215:71 216:6727 217:2773 218:1302 219:577 220:2033 221:981 222:840 223:2178 End of report

1 0

Using RFC1918 on Global table as Loopbacks
by Javier Gutierrez 06 Oct '23

06 Oct '23

Hi, I have recently encountered some operational differences at my new organization that are not what I have been exposed to before, where the loopback of the core network devices is being set from RFC1918 while on the global routing table. I'm sure this is not a major issue but I have mostly seen that ISPs use global IPs for loopbacks on devices that would and hold global routing. My question is, what is the most used or recommended way to do this, if I continue to use RFC1918 I will save some very much desired public address space, but would this come back to bite me in the future? Kind regards, Javier Gutierrez,

7 6

APRICOT 2024: Call for Programme Committee Volunteers
by Mark Tinka 06 Oct '23

06 Oct '23

Hi everyone. The APRICOT 2024 Organising Committee would like to welcome everyone to join us in Bangkok, Thailand, from 21st February to 1st March 2024. The APRICOT 2024 Programme Committee is responsible for the solicitation and selection of suitable presentation and tutorial content for the APRICOT 2024 conference (https://2024.apricot.net/) We are now seeking nominations from the community to join the APRICOT 2024 PC to assist with the development of the programme for APRICOT 2024. Eligible PC candidates must have attended recent APRICOT events, have broad technical knowledge of Internet operations, and have good familiarity with the format of APRICOT. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work actively to solicit content and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. If you are interested in joining the PC and meet the above eligibility criteria, please send a brief note to "pc-chairs at apricot.net". The note must include affiliation (if any) and a brief description about why you would make a good addition to the PC. The PC Chairs will accept nominations received by 17:00 UTC+8 on Friday 20th October 2023, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka & Mark Duffell For the APRICOT 2024 Organising Committee --

1 0

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

06 Oct '23

On 10/5/23 08:24, Geoff Huston wrote: > 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.

3 2

Re: maximum ipv4 bgp prefix length of /24 ?
by Jakob Heitz (jheitz) 05 Oct '23

05 Oct '23

Each unit of mask length increase doubles the size of the table theoretically. About 60% of the table is /24 routes. Just going to /25 will probably double the table size. Not sure I'd like to extrapolate the estimate out to /27. Kind Regards, Jakob ----------------------------------------------------------------------------- Date: Fri, 29 Sep 2023 00:25:55 +0300 From: VOLKAN SAL?H <volkan.salih.06(a)gmail.com> To: nanog(a)nanog.org hello, I believe, ISPs should also allow ipv4 prefixes with length between /25-/27 instead of limiting maximum length to /24.. I also believe that RIRs and LIRs should allocate /27s which has 32 IPv4 address. considering IPv4 world is now mostly NAT'ed, 32 IPv4s are sufficient for most of the small and medium sized organizations and also home office workers like youtubers, and professional gamers and webmasters! It is because BGP research and experiment networks can not get /24 due to high IPv4 prices, but they have to get an IPv4 prefix to learn BGP in IPv4 world. What do you think about this? What could be done here? Is it unacceptable; considering most big networks that do full-table-routing also use multi-core routers with lots of RAM? those would probably handle /27s and while small networks mostly use default routing, it should be reasonable to allow /25-/27? Thanks for reading, regards..

9 14

Autoresponders gone wild - edg.io (or Meta), make it stop
by Jon Lewis 05 Oct '23

05 Oct '23

I'm on my last full day at StackPath, and a couple of autoresponders are making my work email even less usable than usual. It would seem G-Core Labs S.A. (ASN 199524) sent a peering request cc'd to every address they could find relevant to @INEX LAN1 Dublin, and the various autoresponders have been duking it out since about 5:49am Eastern. The only one still emailing everyone several times/minute is support(a)edg.io. If anyone knows someone at edg.io who can make this stop, please suggest they do so asap. It would appear noc(a)meta.com is also involved, but at least Meta's autoresponder has the good sense/programming to not spam the entire recipient list...but it likely playing ping pong with support(a)edg.io. Date: Thu, 5 Oct 2023 11:41:41 -0700 (PDT) From: Edgio Support <support(a)edg.io> Reply-To: support(a)edg.io To: [long list removed] Message-ID: <10724763.48851.1696531301960(a)app137049.phx101.service-now.com> Subject: Incident INC1751177 -- You are on the watchlist for ticket PTKT3218420 -- comments added ... Comments: 2023-10-05 11:45:29 PDT - Guest (Additional comments (client notes)) Reply from: noc(a)meta.com ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

1 0