July 2023 - Test - lists.nanog.org

SAFNOG-8: CfP Announcement
by Mark Tinka 17 Jul '23

17 Jul '23

Hello all. The CfP (Call for Papers) for the SAFNOG-8 conference, due to take place on the 29th - 30th August, 2023, in Lusaka, Zambia, is now open. Please find more details about the CfP at the link below: https://www.safnog.org/#1#call-for-papers-section We look forward to receiving your submissions, and to seeing you in Lusaka soon. Thanks. Mark.

1 1

My first ARIN Experience but probably not the last, unfortunately..
by Robert Webb 17 Jul '23

17 Jul '23

Sorry for the completely off topic rant here, but maybe it will garner some attention from the ARIN folks. So I am attempting a small startup business and and initially building out three sites and thought it would be good to register and upfront get my own IPv6 space instead of leasing from some other party or have to renumber as future things change Looking at the ARIN website and fee schedule, I see there is a blurb at the bottom of the RSP Categories and Fees about IPv6 fees being waived until December 31, 2026. My reaction was along the lines of this is great, it helps small companies and startups get IPv6 deployed and up and running in their environment. So I put in the request for a /44 initial request and provided all my justifications and within a couple of days I got word that my request was approved. Wonderful.. Then I proceed to get a $250 invoice for my /44 under a 3X-Small category! Huh?? So I call in and am told the waiver is only for those in a 2X-Service Category who want to obtain a 3X-Small Category subnet and that it really isn't a fee waiver, but that the 2X-Small Category organization will only be charged a 3X-Small fee of $250 and that the $500 fee. So ARIN, either quit the bait and switch, or fix the wording in the Fee Schedule AND provide a link to the full text of the waiver. As the blurb in the schedule mentions nothing about the 2X-Small Category and honestly, no fees are really waived. Again, apologies for the rant, but just needed to get it out there, the frustration of a small start up business owner..

13 16

1299 capacity constraints
by Drew Weaver 17 Jul '23

17 Jul '23

Has anyone else been having near constant issues with traffic transiting AS 1299 being lost due to their links being oversubscribed? Off-list is fine, I am just trying to get a sense of what is going on there. Thanks, -Drew

7 7

WEBCAST 17-20 July – Routing Security Summit 2023
by Joly MacFie 17 Jul '23

17 Jul '23

Welcome to Routing Security Summit 2023! The kick off tutorial is under way, and sessions proper start tomorrow. All session recordings are available immediately after on the livestream channels. [image: isoc live]On *17-20 July 2023 **MANRS* <https://www.manrs.org/> convenes the *Routing Security Summit 2023 <https://www.manrs.org/event/routing-security-summit-2023/>*. This online event will highlight the importance of routing security and encourage decision-makers and network operators to take real steps toward improving the security and resilience of the global routing infrastructure, bringing together partners from across the Internet routing ecosystem to answer your questions about routing security and the MANRS initiative, discuss successes with implementing routing security measures such as Resource Public Key Infrastructure (RPKI), and share ideas on how to build awareness about routing security among not just the technical community but the wider Internet community. *PROGRAMME https://www.manrs.org/event/routing-security-summit-2023/ <https://www.manrs.org/event/routing-security-summit-2023/>* *Mon 17 July 2023* *10:00-11:00 UTC Tutorial – Routing Security 101* *Massimiliano Stucchi* *Tue 18 July 2023* *7:00-8:00 UTC – Tutorial – How to deploy ROV* *Massimiliano Stucch*i *13:00-14:30 UTC Routing Security as Supply Chain Security: Threats and Opportunities* *Fredrik Korsbäck*, AWS *Matthew Davy*, Visa *Linda Bertz*, FS-ISAC *Antoin Verschuren*, Liberty Global *Joe Abley*, Cloudflare *Benjamin Broersma*, Bureau of the Netherlands Standardisation Forum MOD: *Andrei Robachevsky* *Wed 19 July 2023* *7:00-8:00 UTC – Tutorial – Making the MANRS Observatory Work for You* *Aftab Siddiqui* *11:30-12:30 UTC – It Takes a Community: Exchanging Routing Security Best Practices* *Anand Raje*, India Internet Foundation *Matthias Wichtlhuber*, DE-CIX *Peter Gitau*, Kenya IXP (BBIX) MOD: *Robbie Mitchell* *13:00-14:30 UTC The Role of CSIRTS in Routing Security* *Alain Aina*, Digital Intelligence Services *Barry Greene*, The Shadowserver Foundation MOD: *Jean-Robert Hountomey*, AfricaCERT *Thu 20 July 2023* *11:30-12:30 UTC – The Routing Security Research Roundup* *Romain Fontugne*, IIJ *Khwaja Zubair Sediqi*, Max Planck Institute for Informatics *Thomas Holterbach*, University of Strasbourg MOD: *Amreesh Phokeer* *13:00-14:30 UTC – ROV Research Review* *Cecilia Testart*, Georgia Institute of Technology *Haya Shulman*, Goethe University Frankfurt *Taejoong (Tijay) Chung*, Virginia Tech *13:00-14:30 UTC – Working with Governments to Progress Routing Security* *Gerben Klein Baltink*, Dutch Internet Standards Platform *Veronica Tan*, Cyber Security Agency of Singapore *Doug Montgomery*, National Institute of Standards and Technology (+ Special Guest) MOD: *Ryan Polk* *LIVESTREAM http://livestream.com/internetsociety/routing-security-summit-2023 <http://livestream.com/internetsociety/routing-security-summit-2023>* *REAL TIME TEXT* (See *ISOC.LIVE <https://isoc.live/16715>*) *TWITTER #RoutingSecuritySummit <https://bit.ly/RoutingSecuritySummit> #RPKI #ROV #SupplyChainSecurity #RoutingSecurity <https://bit.ly/RoutingSecurity> @RoutingMANRS @InternetSociety* *MASTODON #RoutingSecurity <https://mastodon.social/tags/RoutingSecurity>* *SIMULCAST CHANNELS* *https://twitter.com/ISOC_Live <https://twitter.com/ISOC_Live>* *https://www.twitch.tv/isoclive <https://www.twitch.tv/isoclive>* *https://www.facebook.com/liveisoc/* <https://www.facebook.com/liveisoc/> (AI Captions) *https://www.facebook.com/RoutingMANRS* <https://www.facebook.com/RoutingMANRS> (AI Captions) *ARCHIVE* *https://archive.org/details/routing-security-summit-2023 <https://archive.org/details/routing-security-summit-2023>* *https://www.youtube.com/@RoutingMANRS* <https://www.youtube.com/@RoutingMANRS> *Permalink - https://isoc.live/16715 <https://isoc.live/16715>* - -- -------------------------------------- Joly MacFie +12185659365 -------------------------------------- -

1 0

Request for assistance with Verizon FIOS connection
by Neil Hanlon 15 Jul '23

15 Jul '23

Hi all - I apoligize for the not-necessarily-on-topic post, but I've been struggling with this issue for the past two weeks and am about out of ideas and options other than ask here. The short version is I recently got FIOS at my (new) house, and plugged in my router (SFF PC running Vyos). Initially, all was fine, however, some time later, connectivity to the gateway given by the DHCP server is completely lost. If I force a renewal, the gateway (sometimes) comes back--sometimes not. When it doesn't work, the DHCPDISCOVER process has to start over again and I often recive a lease in a completely different subnet--which isn't really the problem, but seems to be symptomatic of whatever is happening upstream of me. The problem, from my perspective, is that the IPv4 gateway given to me in my DHCP lease goes away before my lease expires--leading to broken v4 connectivity until either 1. the system goes to renew the lease and fails, starting over; or 2. A watchdog notices and renews the lease (This is what I have attempted to implement, without much success). As a note, IPv6 connectivity (dhcpv6-pd, receiving a /56) is entirely unaffected when IPv4 connectivity breaks. For the past week, I have been monitoring to various IPv4 and IPv6 endpoints over ICMP and TCP, and have been able to chart the outages over that period. More or less, every two hours, shortly after a lease is renewed, the gateway disappears. I'm happy to share more details and graphs/logs with anyone who might be able to help. I have attempted to contact FIOS support several times and even had a trouble ticket opened at one point--though this has been closed as they cannot apparently find any issue with the ONT. I'm at my wit's end with this issue and would really appreciate any and all help. Please contact me off list if you need additional details--I can provide ticket numbers/conversation IDs/etc, as well as graphs/logs/etc. Best, Neil Hanlon

6 10

Re: Request for assistance with Verizon FIOS connection
by Mel Beckman 15 Jul '23

15 Jul '23

Neil, Sorry, I must have missed that branch of the thread. When you had a computer directly connected, did you happen to run a wire shark capture? That wouldn’t require an Ethernet tap. -mel > On Jul 15, 2023, at 7:44 AM, Neil Hanlon <neil(a)neilhanlon.com> wrote: > > On 15.07.2023 07:43, Mel Beckman wrote: >> Matt, >> >> I missed where the OP indicated they've tried both a direct laptop connection as well as another router. I think you may have seen my reply suggesting that and thought that was the OP stating he'd done it. > > I missed it in my initial post, but had responded to your first reply in the thread saying I tried both my laptop and > another (off the shelf) router. > > I didn't make any changes on my end here, but the connection has been (seemingly) stable for the past ~17 hours now. > > I will continue to monitor. > > Thanks all! > > -Neil > >> >> -mel >> ________________________________ >> From: Matt Corallo <nanog(a)as397444.net> >> Sent: Friday, July 14, 2023 9:44 PM >> To: Mel Beckman <mel(a)beckman.org>; Neil Hanlon <neil(a)shrug.pw>; nanog(a)nanog.org <nanog(a)nanog.org> >> Subject: Re: Request for assistance with Verizon FIOS connection >> >> OP indicated they've tried both a direct laptop connection as well as another router. That seems to >> meet the requirement for having ruled out his home-made router, though obviously I agree one should >> attempt to rule out any possible errors by doing transparent packet sniffing analyzing the problem >> carefully before escalating an issue. Hopefully everyone on this list knows the value of the tech on >> the other end of the line's time :) >> >> Matt >> >>> On 7/14/23 9:07 PM, Mel Beckman wrote: >>> Getting the FCC involved seems premature, since the OP hasn't yet ruled out a problem with his home >>> made router. Not that there's anything wrong with making your own router, but it seems there is a >>> burden of proof on the end user to demonstrate the problem isn't at with the CPE. Even a test as >>> simple as connecting a laptop up for a day and running pings would rule out the CPE. >>> >>> -mel >>> ---------------------------------------------------------------------------------------------------- >>> *From:* NANOG <nanog-bounces+mel=beckman.org(a)nanog.org> on behalf of Matt Corallo <nanog(a)as397444.net> >>> *Sent:* Friday, July 14, 2023 5:46 PM >>> *To:* Neil Hanlon <neil(a)shrug.pw>; nanog(a)nanog.org <nanog(a)nanog.org> >>> *Subject:* Re: Request for assistance with Verizon FIOS connection >>> I've always had good luck with https://consumercomplaints.fcc.gov/hc/en-us >>> <https://consumercomplaints.fcc.gov/hc/en-us>. This tends to result in >>> a higher-level tech getting assigned to your ticket at least at larger providers. Depending on where >>> you are, your local government may have a similar process (e.g. in NYC the city has a similar >>> process that tends to get very high priority tech attention as city council members will rake >>> providers over the coals on individual complaints come contract-renewal time). >>> >>> Matt >>> >>> On 7/14/23 8:01 AM, Neil Hanlon wrote: >>>> Hi all - I apoligize for the not-necessarily-on-topic post, but I've been struggling with this issue >>>> for the past two >>>> weeks and am about out of ideas and options other than ask here. >>>> >>>> The short version is I recently got FIOS at my (new) house, and plugged in my router (SFF PC running >>>> Vyos). Initially, >>>> all was fine, however, some time later, connectivity to the gateway given by the DHCP server is >>>> completely lost. If I >>>> force a renewal, the gateway (sometimes) comes back--sometimes not. When it doesn't work, the >>>> DHCPDISCOVER process has >>>> to start over again and I often recive a lease in a completely different subnet--which isn't really >>>> the problem, but >>>> seems to be symptomatic of whatever is happening upstream of me. >>>> >>>> The problem, from my perspective, is that the IPv4 gateway given to me in my DHCP lease goes away >>>> before my lease >>>> expires--leading to broken v4 connectivity until either 1. the system goes to renew the lease and >>>> fails, starting over; >>>> or 2. A watchdog notices and renews the lease (This is what I have attempted to implement, without >>>> much success). >>>> >>>> As a note, IPv6 connectivity (dhcpv6-pd, receiving a /56) is entirely unaffected when IPv4 >>>> connectivity breaks. >>>> >>>> For the past week, I have been monitoring to various IPv4 and IPv6 endpoints over ICMP and TCP, and >>>> have been able to >>>> chart the outages over that period. More or less, every two hours, shortly after a lease is renewed, >>>> the gateway >>>> disappears. I'm happy to share more details and graphs/logs with anyone who might be able to help. >>>> >>>> I have attempted to contact FIOS support several times and even had a trouble ticket opened at one >>>> point--though this >>>> has been closed as they cannot apparently find any issue with the ONT. >>>> >>>> I'm at my wit's end with this issue and would really appreciate any and all help. Please contact me >>>> off list if you need >>>> additional details--I can provide ticket numbers/conversation IDs/etc, as well as graphs/logs/etc. >>>> >>>> Best, >>>> Neil Hanlon

1 0

whois server
by Randy Bush 14 Jul '23

14 Jul '23

``` % host whois.geektools.com Host whois.geektools.com not found: 3(NXDOMAIN) ``` i guess i missed the memo :( randy

4 4

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 14 Jul '23

14 Jul '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 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 15 Jul, 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: 926979 Prefixes after maximum aggregation (per Origin AS): 351217 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 451896 Total ASes present in the Internet Routing Table: 74578 Prefixes per ASN: 12.43 Origin-only ASes present in the Internet Routing Table: 64040 Origin ASes announcing only one prefix: 26340 Transit ASes present in the Internet Routing Table: 10538 Transit-only ASes present in the Internet Routing Table: 439 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 68 Max AS path prepend of ASN (263725) 64 Prefixes from unregistered ASNs in the Routing Table: 1048 Number of instances of unregistered ASNs: 1052 Number of 32-bit ASNs allocated by the RIRs: 42267 Number of 32-bit ASNs visible in the Routing Table: 34804 Prefixes from 32-bit ASNs in the Routing Table: 173237 Number of bogon 32-bit ASNs visible in the Routing Table: 29 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 564 Number of addresses announced to Internet: 3054440448 Equivalent to 182 /8s, 15 /16s and 16 /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.6 Total number of prefixes smaller than registry allocations: 309081 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 245848 Total APNIC prefixes after maximum aggregation: 69865 APNIC Deaggregation factor: 3.52 Prefixes being announced from the APNIC address blocks: 239678 Unique aggregates announced from the APNIC address blocks: 98658 APNIC Region origin ASes present in the Internet Routing Table: 13507 APNIC Prefixes per ASN: 17.74 APNIC Region origin ASes announcing only one prefix: 3997 APNIC Region transit ASes present in the Internet Routing Table: 1797 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8830 Number of APNIC addresses announced to Internet: 773696640 Equivalent to 46 /8s, 29 /16s and 172 /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: 271645 Total ARIN prefixes after maximum aggregation: 123536 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 273939 Unique aggregates announced from the ARIN address blocks: 130821 ARIN Region origin ASes present in the Internet Routing Table: 19099 ARIN Prefixes per ASN: 14.34 ARIN Region origin ASes announcing only one prefix: 6971 ARIN Region transit ASes present in the Internet Routing Table: 1952 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: 4813 Number of ARIN addresses announced to Internet: 1277673984 Equivalent to 76 /8s, 39 /16s and 194 /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: 259956 Total RIPE prefixes after maximum aggregation: 122598 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 256601 Unique aggregates announced from the RIPE address blocks: 159771 RIPE Region origin ASes present in the Internet Routing Table: 28356 RIPE Prefixes per ASN: 9.05 RIPE Region origin ASes announcing only one prefix: 12063 RIPE Region transit ASes present in the Internet Routing Table: 3928 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11233 Number of RIPE addresses announced to Internet: 716735872 Equivalent to 42 /8s, 184 /16s and 133 /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-213403 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: 118894 Total LACNIC prefixes after maximum aggregation: 28611 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 118013 Unique aggregates announced from the LACNIC address blocks: 49519 LACNIC Region origin ASes present in the Internet Routing Table: 11026 LACNIC Prefixes per ASN: 10.70 LACNIC Region origin ASes announcing only one prefix: 2692 LACNIC Region transit ASes present in the Internet Routing Table: 2326 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 68 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8815 Number of LACNIC addresses announced to Internet: 178450432 Equivalent to 10 /8s, 162 /16s and 240 /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: 29588 Total AfriNIC prefixes after maximum aggregation: 5891 AfriNIC Deaggregation factor: 5.02 Prefixes being announced from the AfriNIC address blocks: 38184 Unique aggregates announced from the AfriNIC address blocks: 12662 AfriNIC Region origin ASes present in the Internet Routing Table: 1766 AfriNIC Prefixes per ASN: 21.62 AfriNIC Region origin ASes announcing only one prefix: 617 AfriNIC Region transit ASes present in the Internet Routing Table: 329 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1113 Number of AfriNIC addresses announced to Internet: 107549184 Equivalent to 6 /8s, 105 /16s and 18 /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 9530 8706 40 CHINAMOBILE-CN China Mobile Communicati 7545 5681 784 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4854 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4237 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3536 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3382 1872 93 VNPT-AS-VN VNPT Corp, VN 7552 3344 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 3047 497 247 BBIL-AP BHARTI Airtel Ltd., IN 4766 2538 11270 591 KIXS-AS-KR Korea Telecom, KR 24560 2444 834 445 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 8736 10892 3083 AMAZON-02, US 11492 4515 299 629 CABLEONE, US 7155 4172 288 88 VIASAT-SP-BACKBONE, US 22773 3544 3054 269 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3525 1319 66 SHAW, CA 16625 3153 1565 2366 AKAMAI-AS, US 749 3142 54962 2394 DNIC-AS-00749, US 367 2750 3750 1318 DNIC-ASBLK-00306-00371, US 396982 2676 3594 383 GOOGLE-CLOUD-PLATFORM, US 30036 2503 361 396 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 7298 1706 141 UNI2-AS, ES 39891 4897 290 61 ALJAWWALSTC-AS, SA 20940 4079 3398 161 AKAMAI-ASN1, NL 8551 3467 368 33 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2971 2294 913 ROSTELECOM-AS, RU 9009 2649 245 1376 M247, RO 34984 2307 361 609 TELLCOM-AS, TR 58224 1824 946 535 TCI, IR 6849 1800 307 17 UKRTELNET, UA 13188 1606 100 27 TRIOLAN, UA 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 11574 3376 592 UNINET, MX 10620 3529 507 840 Telmex Colombia S.A., CO 13999 2403 360 632 Mega Cable, S.A. de C.V., MX 11830 2225 369 64 Instituto Costarricense de Electricidad 28573 1316 2324 239 Claro NXT Telecomunicacoes Ltda, BR 3816 1306 774 170 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1303 344 511 Axtel, S.A.B. de C.V., MX 6147 1130 370 22 Telefonica del Peru S.A.A., PE 11664 1101 177 440 Techtel LMDS Comunicaciones Interactiva 26615 1037 2500 47 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 1627 393 19 LINKdotNET-AS, EG 24835 1548 533 27 RAYA-AS, EG 36992 1352 1518 282 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1052 67 45 ORANGE-COTE-IVOIRE, CI 36935 923 521 44 Vodafone-, EG 6713 551 1861 34 IAM-AS, MA 15399 534 54 50 WANANCHI-, KE 24757 485 73 5 EthioNet-AS, ET 37342 466 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 11574 3376 592 UNINET, MX 9808 9530 8706 40 CHINAMOBILE-CN China Mobile Communicati 16509 8736 10892 3083 AMAZON-02, US 12479 7298 1706 141 UNI2-AS, ES 7545 5681 784 691 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4897 290 61 ALJAWWALSTC-AS, SA 4538 4854 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4515 299 629 CABLEONE, US 18403 4237 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4172 288 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 9530 9490 CHINAMOBILE-CN China Mobile Communications Grou 12479 7298 7157 UNI2-AS, ES 16509 8736 5653 AMAZON-02, US 7545 5681 4990 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4897 4836 ALJAWWALSTC-AS, SA 4538 4854 4779 ERX-CERNET-BKB China Education and Research Net 18403 4237 4212 FPT-AS-AP FPT Telecom Company, VN 7155 4172 4084 VIASAT-SP-BACKBONE, US 20940 4079 3918 AKAMAI-ASN1, NL 11492 4515 3886 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 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 19695 UNALLOCATED 8.20.161.0/24 7015 COMCAST-7015, 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 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.176.160.0/24 Origin: 397327 UNASSIGNED 23.176.160.0/24 Transit: 19108 SUDDENLINK-COMMUNICATIONS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW 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:39 /11:103 /12:296 /13:577 /14:1200 /15:2073 /16:13473 /17:8273 /18:13877 /19:25230 /20:44407 /21:51589 /22:110169 /23:98735 /24:556159 /25:749 /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 6386 7298 UNI2-AS, ES 8151 5503 11574 UNINET, MX 39891 3632 4897 ALJAWWALSTC-AS, SA 11492 3426 4515 CABLEONE, US 6327 3335 3525 SHAW, CA 7155 3120 4172 VIASAT-SP-BACKBONE, US 8551 2936 3467 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2609 3544 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2158 2503 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2087 3529 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:2208 2:1350 3:227 4:5 5:4496 6:130 7:6 8:1552 9:1 11:172 12:1520 13:382 14:2321 15:299 16:193 17:373 18:524 20:268 21:4 22:188 23:6373 24:2610 25:4 27:2473 29:19 31:2529 32:80 34:26 35:114 36:1966 37:4690 38:5006 39:829 40:152 41:3905 42:2020 43:2326 44:304 45:16637 46:4364 47:377 49:1773 50:1858 51:586 52:1595 54:397 55:976 56:8 57:120 58:1887 59:1149 60:984 61:2494 62:2664 63:1909 64:5604 65:2321 66:4989 67:3061 68:1334 69:4106 70:1210 71:687 72:2987 74:2639 75:1568 76:617 77:2445 78:1825 79:2979 80:2101 81:1796 82:1501 83:1264 84:1544 85:3002 86:765 87:2005 88:1182 89:3834 90:614 91:7786 92:2041 93:2602 94:3571 95:4048 96:1311 97:337 98:1153 99:735 100:95 101:1082 102:2806 103:31670 104:4575 105:504 106:886 107:2556 108:1077 109:4244 110:2111 111:3184 112:2061 113:1813 114:1644 115:1975 116:1916 117:2530 118:2618 119:1989 120:1820 121:1136 122:2570 123:2181 124:1617 125:2495 128:1458 129:1059 130:1017 131:1991 132:812 133:422 134:1800 135:307 136:886 137:954 138:2540 139:1591 140:1258 141:1299 142:1476 143:1502 144:988 145:341 146:1964 147:1587 148:2430 149:2139 150:883 151:1166 152:1834 153:496 154:4649 155:1358 156:1833 157:1316 158:1088 159:2267 160:2582 161:1554 162:3508 163:1569 164:1623 165:1866 166:1066 167:1714 168:3878 169:950 170:4614 171:890 172:3645 173:2966 174:1090 175:1192 176:3744 177:4492 178:3607 179:2173 180:2446 181:3493 182:3438 183:1993 184:2324 185:20482 186:4745 187:4088 188:4122 189:3710 190:9253 191:1391 192:10933 193:8925 194:7327 195:5140 196:3112 197:2379 198:5999 199:6105 200:8083 201:5948 202:10600 203:10127 204:4563 205:3701 206:4339 207:3458 208:4144 209:4933 210:4474 211:2527 212:4253 213:3590 214:1091 215:59 216:6680 217:2737 218:1297 219:584 220:1985 221:965 222:855 223:2185 End of report

1 0

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN78
by Jacques Latour 14 Jul '23

14 Jul '23

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN7 Annual General Meeting In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN78 Annual General Meeting being held as a hybrid meeting from 21-26 October 2023 Hamburg, Germany in the Central European Summer Time Zone (UTC +2). This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN77 Policy Forum on Monday, 12 June 2023. The presentations and transcripts are available at: https://meetings.icann.org/en/icann77. The DNSSEC Workshop Program Committee is developing a program for the upcoming meeting. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN78 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? * Do you still submit/accept DS records with Digest Type 1? * What is the best practice around key roll-overs? * What about Algorithm roll-overs? * Do you use and support DNSKEY Algorithms 13-16? * How often do you review your disaster recovery procedures? * Is there operational familiarity within your customer support teams? * What operational statistics have been gathered about DNSSEC? * Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: * Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) * What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? * What do you expect DNSSEC to do for you and what doesn't it do? * What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS, DNSSEC, routing and other topics that could impact the security and/or stability of the Internet. We are looking for presentations that cover implementation issues, challenges, opportunities, and best practices for: * Emerging threats that could impact the security and/or stability of the Internet * DoH and DoT * RPKI (Resource Public Key Infrastructure) * BGP routing & secure implementations * MANRS ( Mutually Agreed Norms for Routing Security) * Browser security - DNS, DNSSEC, DoH * EMAIL & DNS related security - DMARC, DKIM, TLSA, etc... If you are interested in participating, please send a brief (1-3 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by COB Friday, 15 September 2023. Thank you, Kathy and Andrew On behalf of the DNSSEC Workshop Program Committee: Fred Baker, ISC Steve Crocker, Edgemoor Research Institute Mark Elkins, DNS/ZARC Jacques Latour, .CA Russ Mundy, Tislabs Yoshiro Yoneya, JPRS Dan York, Internet Society CLASSIFICATION:CONFIDENTIAL

1 0

Re: Request for assistance with Verizon FIOS connection
by Doug Barrett 14 Jul '23

14 Jul '23

If possible, put a network tap in-between the router and the ONT, and sniff the traffic. I've seen this recently where in a very specific circumstance (two hardware vendors, and only with CGNAT IPs), one side stopped responding to ARP requests. The tap capture showed the request going out, but the far end never processed it. Running a capture on the far end device wouldn't show the received ARP request - it just vanished somewhere between the wire and the pcap. Solution ended up being a software update on the router side, I'm assuming it updated a NIC driver as well. -----Original Message----- From: NANOG <nanog-bounces> On Behalf Of Neil Hanlon Sent: Friday, July 14, 2023 10:54 AM To: Mel Beckman <mel(a)beckman.org> Cc: nanog(a)nanog.org Subject: Re: Request for assistance with Verizon FIOS connection CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

1 0