- NANOG - lists.nanog.org

Reminder to Submit Presentations for NANOG 85
by Cat Gurinsky 07 Mar '22

07 Mar '22

NANOG Community, The NANOG Program Committee (PC) would like to remind you that we are accepting proposals for in-person or remote presentations at all sessions of NANOG 85, a hybrid meeting, taking place in Montréal, QC, Canada on June 6th-8th, 2022. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at https://www.nanog.org/program/call-presentations/. Given by many of the industry’s top minds, presentations at NANOG meetings are meant to spark the imagination, encourage dialog, and drive new solutions to our greatest networking challenges. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional, or discuss proprietary solutions. Requested Topics: June 6th is the 10 year anniversary for World IPv6 Launch Day! As a result, for NANOG 85 we have chosen this for our theme and are actively seeking talks about IPv6. Additionally, based on feedback from our survey results, we have seen numerous requests for the following topics: - Network Automation - Tutorials (IPv6, BGP, Segment Routing, DNS) - Security (developments in, problems/solutions, various protocols of). Don’t wait! Presentation abstracts and draft slides should be submitted no later than Monday, April 25, 2022. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the form Timeline for submission and proposal review: - Submitter enters abstract (and draft slides if possible) in the Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — typically within 2 weeks. - Submitter develops draft slides of talk if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic. - FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (April 25, 2022). - PC evaluates submissions to determine presentations for the agenda (posted on May 23, 2022). - Agenda assembled and posted. - Submitters notified. - Final presentation slides must be submitted prior to the published deadline for slides (May 20, 2022 for Remote/Pre-recordings and May 31, 2022 for in-person presentations). If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nanogpc(a)nanog.org) and a representative will respond to you in a timely manner. Otherwise, submit your talk, keynote, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 85 Calendar of Events Date Event/Deadline March 7, 2021 CFP Announced April 25, 2022 Submission Deadline: Abstracts WITH Draft Presentation Slides Due May 9, 2022 Topics List + Highlights Posted May 23, 2022 NANOG 85 Agenda Published May 20, 2022 Pre-Record Presentation FINAL Slides Due May 20, 2022 Speaker Presentation Recordings Finalized May 31, 2022 In-Person Presentation FINAL Slides Due June 6-8, 2022 NANOG 85 Conference Final slides for pre-recorded presentations must be submitted by Friday, May 20, 2022. NO changes will be accepted between the recording date and the conference. Final slides for in-person presentations must be submitted by Tuesday, May 31, 2022. Materials received after that date may be updated on the website after the completion of the conference. We look forward to seeing you in June! Sincerely, Cat Gurinsky Program Committee Chair Sent on behalf of the NANOG PC

1 0

Re: Russia to disconnect from global Internet
by Hank Nussbacher 07 Mar '22

07 Mar '22

Bill Woodcock wrote: > This applies exclusively to Russian federal government networks, not ISPs or telecom operators. https://twitter.com/krisnova/status/1500590779047170048?s=12 says otherwise. -Hank

4 3

Vodafone-UA
by Lady Benjamin Cannon of Glencoe 07 Mar '22

07 Mar '22

Can someone (anyone) from Vodafone Ukraine contact me off-list about an urgent national security matter. Thanks. -LB Ms. Lady Benjamin PD Cannon of Glencoe, ASCE 6x7 Networks & 6x7 Telecom, LLC CEO ben(a)6by7.net "The only fully end-to-end encrypted global telecommunications company in the world.” ANNOUNCING: 6x7 GLOBAL MARITIME <https://alexmhoulton.wixsite.com/6x7networks> FCC License KJ6FJJ

2 1

Conflicts and fiber cuts
by Hank Nussbacher 07 Mar '22

07 Mar '22

As the discussion rages on NANOG, RIPE, CENTR and many other uber-technical forums, I would like to see whether we can focus on what we know best - networking. Perhaps a weekly report of fiber cuts throughout Europe (starting from Feb 15) and the RFO that the carrier provided. Of especial interest would be undersea/underocean cuts or strange outages that the carrier cannot explain. Perhaps we can then map where some nation/state is sabotaging fiber or tapping into such fiber. Anyone willing to run with this? -Hank

4 5

Re: Russia to disconnect from global Internet
by Jared Brown 07 Mar '22

07 Mar '22

Accidentally put the wrong link for the translation. Here is the correct link to the machine translation: https://twitter.com/JiriVysin/status/1500560017640067077 ---------------------------------- According to Nexta (Belorussian media outlet: https://nexta.tv , https://en.wikipedia.org/wiki/Nexta ) Russia has begun active preparations to disconnection from the global Internet. No later than March 11, all servers and domains must be transferred to the Russian zone. In addition, detailed data on the network infrastructure of the sites is being collected. Source: https://twitter.com/nexta_tv/status/1500553480548892679 Machine translation of decree: https://twitter.com/nexta_tv/status/1500553480548892679 Cogent exiting the Russian market is probably not related, but interesting nevertheless. - Jared

9 9

Transmission of tornado warnings delayed by major NWS tech issue
by Sean Donelan 07 Mar '22

07 Mar '22

Weather Service tornado warnings were delayed during deadly Iowa outbreak https://www.washingtonpost.com/weather/2022/03/06/nws-tornado-warning-disse… [...] Susan Buchanan, the Weather Service’s director of public affairs, wrote that “a technical issue caused a delay of between 2-7 minutes for some transmissions,” noting that “system engineers quickly took action as soon as the problem was detected.” She emphasized that warning lead times averaged approximately 20 minutes during the outbreak. “The National Weather Service is investigating this issued to determine the root cause and prevent it from happening in the future,” she wrote. [...] Weather radio was inaccessible in west-central Iowa as the transmitter tower in Denison, Iowa, suffered a “communications failure” Friday that knocked it “off the air.” There was no word of the transmitter being back online by Sunday. [...] Amazon Alexa and Microsoft Widgets now include severe weather alerts. Google Search and Maps also include severe weather alerts. Other streaming services do not have severe weather alerts.

1 0

Russia to disconnect from global Internet
by Jared Brown 06 Mar '22

06 Mar '22

According to Nexta (Belorussian media outlet: https://nexta.tv , https://en.wikipedia.org/wiki/Nexta ) Russia has begun active preparations to disconnection from the global Internet. No later than March 11, all servers and domains must be transferred to the Russian zone. In addition, detailed data on the network infrastructure of the sites is being collected. Source: https://twitter.com/nexta_tv/status/1500553480548892679 Machine translation of decree: https://twitter.com/nexta_tv/status/1500553480548892679 Cogent exiting the Russian market is probably not related, but interesting nevertheless. - Jared

1 0

identity.cisco.com certificate has expired
by Matthew Huff 06 Mar '22

06 Mar '22

Arghh... Just an FYI, id.cisco.com is fubar'ed. Hopefully cisco has already fixed it and the proxies/caches/cdns just need to timeout, but just in case anyone knows a contact at Cisco's ops group... [cid:image001.png@01D8309A.75491410] Matthew Huff | Director of Technical Operations | OTA Management LLC Office: 914-460-4039 mhuff(a)ox.com<mailto:mhuff@ox.com> | www.ox.com<http://www.ox.com> ...........................................................................................................................................

2 1

Washington–Moscow Direct Communications Link
by Sean Donelan 06 Mar '22

06 Mar '22

Since 2008, the Washington-Moscow Direct Communications Link (also known as "The Washington-Moscow Hotline") uses redundant circuits of two satellite links and a fiber-optic cable. They use commercial facilities for at least part of the circuits. Past accidents have interrupted previous hotline circuits. A Danish bulldozer operator once cut the line near Copenhagen. A Finnish farmer once plowed it up. A fire in a Baltimore Maryland manhole took it out of service temporarily. Yep, even the hotline experienced cable cuts.

4 3

Re: RU evidently hijacked UA netblock
by Scott Weeks 05 Mar '22

05 Mar '22

--- jay(a)west.net wrote: On 3/4/22 18:03, Scott Weeks wrote: > It looks like a 'too many' AS prepends, but it is only 250 prepends. In most reasonable scenarios I'd say that this qualifies as too many. --------------------------------------------- Yeah, technically, but it was not 256 or something where I'd expect an issue to happen. Just curious as to why only that ASN caused the buffer overflow messages as I got them from no other AS ever and wondered if anyone else has seen them. Other ASNs almost certainly have sent 250+ prepends to me before, but they did not cause the overflow. Like I said, I have a ticket open because I am curious: BGP-WARNING-tBgp4RouteInvalid-2007 <stuff> Route invalid reason - Cannot add/prepend AS-path. Buffer overflow\nNRLI - <prefix> where prefixes are several and different lengths. Probably nothing, but I always look into stuff I see in the syslog server's router.log. scott

2 1