- NANOG - lists.nanog.org

Keep Ukraine Connected
by Markus 14 Apr '22

14 Apr '22

Hi NANOG, for those wanting to help - please see below and https://keepukraineconnected.org for an up-to-date list of needed equipment. Also: "Our contacts in Ukraine are desperately seeking professional grade fiber splicers. If you think you can help, either by donating equipment or financing a splicer, we’d appreciate an email." Forwarded with permission. ----- Forwarded message from Jan Zorz - Go6 <jan(a)go6.si> ----- Dear community, Sorry for another rather long email, but there are more and more requests from Ukraine operators coming in and we have no other way of getting specific equipment other than ask you - the community! Lately we got specific requests for fiber optics welding/splicing kits, specially from Kharkiv region that is/was under brutal attacks and lots of infrastructure is damaged. Let me copy/paste parts of messages that keep coming in so you get the feeling what people that are trying to keep the lights on in the fibers in Ukraine are dealing with: "In Kharkiv we provide continuous network access to other Ukrainian operators and providers. Our network suffers critical loads now because of shelling, and our co-workers repair it, sometimes, under the shots. We lack necessary equipment and tools and are not able to order. There is an urgent need for an optical fiber welding machine (as we have to work in difficult conditions). The amount of work is growing, but the maintenance is missing. We want to ask you, if it's possible, to give us at least one machine fujikura or fitel. We'll be glad to receive even a used one, the most important is it should work." "I also wanted to ask - Do you have, maybe some power backup systems? Also there are our partners in the city - internet provider, who have de-energized nodes for 2-3 thousand active subscribers, in which there is simply no electricity ..." "is there any possibility to send some more of the same optical fiber machines? and if it is possible two or three of the simplest optical reflectometers." We are getting more and more similar requests, so our question to community would be if anyone has any new/used/spare FO welding/splicing kit to donate to Ukraine friends to keep the Internet up&running and people connected? Same goes for UPS systems... We at GNA have secured one Fujikura 41S+ Fusion Splicer Kit with CT50 Cleaver - partially donated by one of their distributors, partially covered by money donations to GNA "Keep Ukraine Connected" initiative that many of you sent in last couple of weeks and we are very grateful for!!! First delivery of requested hardware to Ukraine is now being coordinated with with our colleagues from the Ukrainian Association of Rights Holders and Content Providers, the Ukrainian Internet Association (UAI) and Ukraine Ministry of Digital Transformation and will take place next week. We would like to secure more fiber optics repair equipment and UPS systems before next delivery, so please - if you are willing and can help - contact us at ukraine(a)nogalliance.org for hardware donation or donate some funds at below web page so we are able to purchase needed equipment and send it to Ukraine with next delivery. https://keepukraineconnected.org/ Thank you again, Jan Zorz on behalf of GNA/KUC initiative

1 0

ping across infomart ix, please
by Randy Bush 14 Apr '22

14 Apr '22

could someone who sees 198.180.152.0/24 (as 4128) over equinix infomart please ping 198.189.152.132 (and trace) and respond to me privately? thanks. rand

1 2

Hulu Contact?
by Jason Lamb 13 Apr '22

13 Apr '22

Hi all, We are having some issues with customers logging into Hulu on some recent IPv4 ranges we have added to our network. I think it is likely an IPv4 geolocation issue since the issue only appears on our newer IPv4 ranges. If anyone from Hulu NetOps is monitoring this, or if anyone has a Hulu NetOps contact they would share, please reach out to me. Thanks! Jason [PRTC] <http://www.prtcnet.org> Jason Lamb, Software Engineering/IT Supervisor Peoples Rural Telephone Cooperative <http://www.prtcnet.org> 259 Main St. S. | P.O. Box 159 | McKee, KY 40447 Main: (606) 287-7101 | Direct: (606) 287-5488 | Email: jason.lamb(a)prtc.org<mailto:jason.lamb@prtc.org> CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please notify the sender by return e-mail and delete it immediately. Do not print or disseminate its contents. The information in this message is intended for the listed recipients only. This message may contain information that is privileged, confidential or otherwise protected from disclosure to parties other than the listed recipients. If you are not one of the listed recipients, any disclosure, copying, distribution, or the taking of any action based on the contents of this message is prohibited.

2 1

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN74 Policy Forum
by Jacques Latour 13 Apr '22

13 Apr '22

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN74 Policy Forum In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN74 Public Forum being held as a hybrid meeting from 13-16 June 2022 in the Central European Time Zone (UTC +1). 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 ICANN73 Community Forum on Wednesday 09 March 2022. The presentations and transcripts are available at https://73.schedule.icann.org/meetings/qGWqRxCjbWHqdGLxN, https://73.schedule.icann.org/meetings/pm4Zz3yN3CgjoTXp2 and https://73.schedule.icann.org/meetings/qiGweLr2MS7zJwy8o. 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 ICANN74 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 rollovers? * What about Algorithm rollovers? * 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, 29 April 2022. Thank you, Kathy and Andrew On behalf of the DNSSEC Workshop Program Committee: Steve Crocker, Shinkuro Mark Elkins, DNS/ZACR Jacques Latour, .CA Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Fred Baker, ISC Dan York, Internet Society

1 0

Oahu HI undersea cable attack disrupted by federal agents
by Sean Donelan 13 Apr '22

13 Apr '22

https://www.hawaiinewsnow.com/2022/04/13/hsi-agents-honolulu-disrupted-cybe… Homeland Security Investigations says it was able to disrupt a cyberattack of a critical undersea cable, adding the hackers sought to target “infrastructure on Oahu.” The cable links Hawaii and Pacific to critical telecommunications, including internet and cell phones. HSI said its agents, based on a tip from their counterparts on the mainland, were able to disrupt last week a “significant breach involving a private company’s services” associated with the undersea cable.

1 0

IMPORTANT NOTICE - Retirement of ARIN Non-Authenticated IRR rescheduled for 4 April 2022
by John Curran 13 Apr '22

13 Apr '22

NANOGers - An important reminder – On 4 April 2022, ARIN's non-authenticated Internet Routing Registry (IRR) will be retired. Please review the attached notice for details, and do not hesitate to contact ARIN if you have any questions about this transition or need assistance. I ask that you do not hesitate to forward this notice to any others you know that are potentially unaware & impacted by this important transition. Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] UPDATE: Retirement of ARIN Non-Authenticated IRR rescheduled for 4 April 2022 Date: 28 January 2022 at 9:01:07 PM GMT+4 To: "arin-announce(a)arin.net<mailto:arin-announce@arin.net>" <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> This announcement is to inform you that the retirement of the ARIN non-authenticated Internet Routing Registry (IRR) has been rescheduled to 4 April 2022 at 12:00 PM EST. After this time, users will no longer be able to create, update, or delete records in the ARIN-NONAUTH database, and the ARIN-NONAUTH data stream will no longer be available in Near Real Time Mirroring (NRTM) or via FTP or Whois Port 43. This date change is being made in order to ensure that the first day after retirement does not fall on a Friday. The following information is from the initial announcement: ARIN has been engaged in a multi-year project to create and deploy a new and improved Internet Routing Registry (IRR). As a result of these efforts, ARIN now provides users with the ability to create, update, and delete objects in ARIN’s authenticated IRR database using ARIN Online or ARIN’s RESTful API. Unfortunately, use of ARIN’s previous non-authenticated email-based IRR service actually increased after ARIN released its authenticated IRR, in opposition to the outcome ARIN anticipated when improving its IRR. On 8 February 2021, ARIN held a consultation to solicit input on the retirement of ARIN’s non-authenticated email-based IRR service. This retirement was originally scheduled for 30 September 2021. Based on community input, the proposed date for the ARIN-NONAUTH retirement was delayed to 31 March 2022 to allow more transition time for users. We also notified by email Points of Contact (POCs) of organizations who have objects in the ARIN-NONAUTH database of the retirement date and offered them our assistance with the transition. If you have questions about this transition or need assistance, you can contact us by: • submitting an Ask ARIN ticket or chat with us using your ARIN Online account • emailing the Routing Security Team at routing.security(a)arin.net<mailto:routing.security@arin.net> • contacting the Registration Services Help Desk by phone Monday through Friday, 7:00 AM to 7:00 PM ET at +1.703.227.0660 Regards, Brad Gorman Senior Product Owner, Routing Security American Registry for Internet Numbers (ARIN)

21 62

Fwd: Fw: HOST IRR Retirement
by Ross Tajvar 12 Apr '22

12 Apr '22

I tried sending the below message from my work account, but it's not a nanog subscriber, so the email was rejected. If anyone doubts the authenticity, feel free to reach out to me at rtajvar(a)365datacenters.com. ------------------------------ *From:* Ross Tajvar *Sent:* Monday, April 11, 2022 3:53 PM *To:* nanog(a)nanog.org <nanog(a)nanog.org> *Subject:* HOST IRR Retirement Hi all, We (365 Datacenters) inherited the HOST IRR. We have removed all stale objects from it, and moved all valid objects to other IRRs. We will eventually (hopefully soon) turn it off altogether. Please, if you are mirroring it, stop doing that. If you maintain documentation that lists IRRs, please update it to reflect that HOST is no longer in use. Thanks! P.S. If anyone thinks I should also announce this somewhere else, please let me know. *Ross Tajvar* Network Engineer Office: (571)-341-8899 Support: (866)-365-6246

3 2

Something observed while doing IRR cleanup (generic name collisions)
by Dan Mahoney (Gushi) 11 Apr '22

11 Apr '22

All, The dayjob has a LOT of ASes (we peer with a unique AS per-site), so our IRR entries are kind of a lot. When "email templates" was the only way to do things, this was really annoying to update and maintain. I will say that having RPKI roas for the correct ASes for all of our entries has given my stale-object-deletion-requests more "authoritah" than those requests would have had a few years ago. Job's excellent IRRexplorer tool has been wonderful in helping figure this out and display it all at a glance, and also in finding cases where "we no longer peer with this group, but we're still in the as-set", and a few where "they peer with us, but not with this AS". I don't know how many people use irrd or rtconfig or whatever to generate your filter-lists. But even with all the work we (the operator community) is doing to widely deploy RPKI and authenicated IRRs, we still have stuff like this: $ whois -h whois.radb.net AS-PEERS | grep 'as-set\|descr\|source\|members\|^\s*$' as-set: AS-PEERS descr: autonomous systems that OpenDNS peers with members: [like 30 of them, one per line, snipped for brevity] source: RADB as-set: AS-PEERS descr: 4b42 Peering Autonomous System Numbers [no members: line!] source: RIPE as-set: AS-PEERS descr: Peer AS Numbers members: AS132251,AS132561,AS132516 source: APNIC as-set: AS-PEERS descr: swell.network Peers members: AS-HE,AS-NTT source: ARIN ..four separate organizations felt it would be clever to create a vaguely-named AS-PEERS object, each in a different IRR, because the various IRR's all allow this, and don't check for the existence of objects in another. No IRR's require any special names, nor do they block on any generic names. No IRR sends a member warnings when their objects exist in more than one registry with different data. I haven't tried to query the peeringdb API to see if any of these are used as advertised AS-Sets for public use, or if people just created public objects for their own internal tools. I'm sure this is not the only case of this. This might be why we can't have nice things. -Dan --

2 1

Puerto Rico (island-wide) power outage
by Sean Donelan 10 Apr '22

10 Apr '22

The island-wide electrical grid has failed on Puerto Rico. >From the utility company: Fault in the output breaker of Unit #5 of Costa Sur at 230kv caused the output of units 5 and 6 of the Central. The electrical system protection system took the rest of the units that were generating out of service.

1 7

People trying to sell "ARIN Leads"
by Jon Sands 09 Apr '22

09 Apr '22

Does anyone else get email offers like the below? I get them at least once a week from various companies I've never heard of, I'm sure they pop up under different names constantly for obvious reasons. Crap like this I imagine is why a few of my POC emails listed on my ARIN assets get constant spam, I can't imagine how many places there are like this scraping then selling ARIN data to marketing outlets. name and email in the below *not* scrubbed for anonymity because they need to cut this shit out -------- Forwarded Message -------- Subject: Re: American Registry for Internet Numbers (ARIN) Leads 2022 2 Date: Thu, 7 Apr 2022 12:16:02 +0000 From: Julie Levay <julie.levay(a)hoversamerica.com> To: jon(a)fohdeesha.com <jon(a)fohdeesha.com> Hi, Good Day! Would you be interested in acquiring contacts of *below?* *_Lists Contains:_**Operator/Carrier/Service Provider, VAR / Systems Integrator, Device Manufacturerr, Infrastructure Provider, Consultant, Software / Application Development, Telecom Software Provider, Gov't/ Utility / Enterprise, Telecom Equipment Manufacturer, Business and Technology Leaders, CTOs, Channel & Partner Managers, Business Development Managers, Analysts & Infrastructure Teams from Cloud Service Providers, Telecommunications, ISPs, ISVs and the IT Channel and Industry serving the cloud community *and more. *_We provide information like-_*Name, Email, Title, Phone Number and Company Details Please let me know you’re below requirements in detail so that I can provide Counts and test file for your review. *Target Industry: ____________________??* *Target Geography: ________________??* *Waiting for your response.* *Regards,* *Julie Levay* *Demand Generation Specialists.* * * -- Jon Sands MFI Labs https://fohdeesha.com/

8 10