- Test - lists.nanog.org

OARC 35 Workshop, May 6th & 7th, Registration and Call for Contributions now open
by Jake Zack 26 Feb '21

26 Feb '21

OARC 35 will be an online meeting on May 6th & 7th starting at 01:00 UTC. The Programme Committee is seeking contributions from the community. All DNS-related subjects and suggestions for discussion topics are welcome. For inspiration, we provide a non-exhaustive list of ideas: - Stories of DNS Migrations: Reasoning for DNS software migration. Tooling used to ensure a smooth and correct process. - DNS Intricacies: Chasing down problems and surprising behavior. - Garbage Traffic: Analysis on unexpected traffic seen by authoritative and recursive servers. - DITL: Day In The Life of various roles and teams in DNS. As it is an online workshop, we'd like to encourage brevity; presentations should not be longer than 20 minutes (with additional time for questions). **Workshop Milestones:** * 04 Feb 2021 - Submissions open via Indico * 18 Mar 2021 - Deadline for submission (23:59 UTC) * 25 Mar 2021 - Initial Contribution list published * 08 Apr 2021 - Full agenda published * 22 Apr 2021 - Deadline for slideset submission and Rehearsal * 06 May 2021 - OARC 35 Workshop The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc35> DNS-OARC provides registration fee waivers for the workshop to support those who are part of under-represented groups at DNS-OARC. See the registration page for details. To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. Additional information for speakers of OARC 35: * your talk will be broadcast live and recorded for future reference * your presentation slides will be available for delegates and others to download and refer to, before, during and after the meeting * you will be expected to attend a rehearsal on April 22nd. It would be very useful to have your slides (even if draft) ready for this. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> Jacob Zack for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- Jacob Zack DNS Architect – CIRA (.CA TLD)

1 0

Anyone from Charter or Spectrum?
by Joseph Jenkins 26 Feb '21

26 Feb '21

Seeing some issues with packet loss from my users on Charter and Spectrum in California when trying to access my network on Level3/Lumen. Trying to figure out if there are any issues on the Charter or Spectrum side and how to help out my users.

1 0

Comcast Burp in Mass/Boston Area
by Jason Kuehl 25 Feb '21

25 Feb '21

Anyone else with Comcast have a small outage? About 5-7 minutes? -- Sincerely, Jason W Kuehl Cell 920-419-8983 jason.w.kuehl(a)gmail.com

2 3

Historic IRR/RADB snapshots?
by Lars Prehn 25 Feb '21

25 Feb '21

Does anybody have (somewhat frequent, e.g., monthly) snapshots of the various IRR databases lying around? Any snapshot since 2010 would be helpful! Best regards, Lars

3 2

Why are FCC outage reports treated as confidential?
by Sean Donelan 24 Feb '21

24 Feb '21

FCC is proposing a change to who can have access to FCC outage reports. But first a little history.... After the 1990 AT&T Long Distance switching network collapse, there were lots of investigations. The January 15th outage was the biggest, there were a few more smaller crashes in 1990 and 1991. The Network Reliability Council at was first organized by the FCC in January of 1992 following a series of major service outages in various local exchange and interexchange wireline telephone networks. In 1992, the FCC established mandatory network outage reporting requirements for telephone carriers. Originally, outage reports were public documents, although you needed to visit the FCC offices in Washington DC to view them in person. Eventually, the FCC posted the outage reports online during the early days of the Internet. Originally, outage reports were presumed public, unless specifically determined to be confidential. I recall an outage report about a circuit serving Area 51 which disappared after it was filed. In 2004, the FCC decided “[t]he disclosure of outage reporting information to the public could present an unacceptable risk of more effective terrorist activity". Actually what happened, one carrier started using FCC outage reports in its advertising claims that it was "more reliable" than other carriers because it reported fewer outages to the FCC. The other carriers got upset and complained to the FCC. Instead of telling the one carrier to stop using the outage reports in its advertisements, the FCC made all the outage reports confidential. After the decision to make outage reports presumptively confidential, in addition to the public, other state, local and federal agencies no longer had access to them. Although FCC still won't make the outage reports public, its creating a complicated process for selective parties to have access to the outage reports. Amendments to Part 4 of the Commission’s Rules Concerning Disruptions to Communications: Second Report and Order - PS Docket No. 15-80 https://docs.fcc.gov/public/attachments/DOC-370262A1.pdf

1 0

FCC March meeting: Notice of Inquiry: EAS alerts through the Internet
by Sean Donelan 24 Feb '21

24 Feb '21

In response to the recently passed READI Act, the Federal Communications Commission agenda for its March meeting includes the following notice of inquiry: https://www.fcc.gov/document/fcc-announces-tentative-agenda-march-open-meet… The NDAA21 directs the Commission, within 180 days, to adopt rules to implement Section 9201 (a)-(d) and to complete an inquiry under Section 9201(e). The FCC is required to report to Congress on the findings of the inquiry within 90 days after its completion. What the Notice of Inquiry Would Do: • Seek comment on whether it is technically feasible to deliver EAS alerts through the Internet, including through streaming services. • Seek comment on whether and how to leverage the capabilities of the Internet to enhance the alerting capabilities of the radio and television broadcasters, cable systems, satellite radio and television providers, and wireline video providers that currently participate in EAS.

1 0

Explore the best of NANOG 81 Virtual!
by NANOG News 24 Feb '21

24 Feb '21

The conference may be over, but the hours of archived talks, keynotes, and panel discussions are just waiting to be explored! We've gathered up all the very best, just for you. Scroll on to learn more! Details for NANOG 82 — June 14-16, 2021 — are forthcoming. Stay tuned for more information! View Agenda <https://nanog.org/meetings/nanog-81/agenda/> View Attendees <https://nanog.org/meetings/nanog-81/registered-attendees/> *Virtual Webcast* Whether virtual or IRL, we live-stream every conference so you can return to any recorded presentation you’d like at any time — from a panel on RIRs featuring representatives from AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC, to talks and keynotes on ROA deployments, automation, security, and a brief history of router architecture. You'll find a curated selection of NANOG 81 videos on NANOG TV + the full webcast on our YouTube channel, with hours of insights from some of the brightest minds in network engineering, operations, and architecture. Watch Webcast <https://www.nanog.org/news-stories/nanog-tv/nanog-81-webcast/> *Keynotes* “Donuts make lousy routers.” Toni Li, Arista Networks Didn't get to tune in to Tony Li's and Jennifer Rexford's keynotes? Be sure to check them out on NANOG TV! Tony's keynote, "A Brief History of Router Architecture" covered the earliest days of bus-based systems to today's multi-chassis monstrosities. In Jennifer's keynote "Securing Internet Applications from Routing Attacks," she discussed application-specific routing attacks, and why both application-layer and network-layer defenses are essential. Watch Keynotes <https://www.nanog.org/news-stories/nanog-tv/keynotes/> *Community Meeting * NANOG's success depends on the collective expertise of its dynamic community! Miss out on the NANOG 81 Virtual Community Meeting? Watch the recording to hear more from Executive Director Edward McNair, and NANOG Program Committee members Steve Feldman and Elizabeth Culley. Watch Now <https://www.nanog.org/news-stories/nanog-tv/nanog-81-webcast/> *Call for Presentations* Share your insights at a future NANOG meeting, with a presentation that brings your research + ideas to life. The NANOG PC accepts proposals on a rolling basis, and would love to see yours! Learn More <https://www.nanog.org/participate/call-presentations/> *Our community is the best! * The NANOG Staff, Board of Directors, and Program Committee would like to thank each and every attendee + sponsor + exhibitor <https://www.nanog.org/meetings/nanog-81/our-sponsors/> for making NANOG 81 an amazing experience — your continued support means everything to us! *There's still time to register for our next webinar!* Join us this Friday, Feb 26 (11am PST / 2pm EST) for "BGP Fundamentals" featuring Aaron Atac of Subspace. In this webinar, Aaron will cover the fundamentals of the Border Gateway Protocol (BGP) as well as service-provider operational insights and challenges not necessarily highlighted in textbooks. We'd love to see you there! Learn More <https://www.nanog.org/meetings/webinar-bgp-fundamentals/>

1 0

LOAs for Cross Connects - Something like PeeringDB for XC
by Douglas Fischer 23 Feb '21

23 Feb '21

I believe that almost everyone in here knows that LOAs for Cross Connects in Datacenters and Telecom Rooms can be a pain... I don't know if I'm suggesting something that already exists. Or even if I'm suggesting something that could be unpopular for some reason. But every time I need to deal with some Cross-Connect LOA, and mostly when we face some rework on data mistakes, I dream with a "PeeringDB for Cross Connects". So, this mail is a question and also a suggestion. There is something like an "online notary's office" exclusive for Cross-Connect LOAs? - Somewhere Organizations can register information authorizing connections of Port on their Places (Cages, Racks, etc)... If it doesn't exist. What would be necessary for that? Mostly considering the PeeringDB work model. - OpenSource. - Free access to the tool, and sponsors to keep the project alive. - API driven, with some Web-gui. And considering some data-modeling. - Most of the data being Open/Public (Organizations, Facilities(Datacenters and/or Telecom-Rooms), Presence on Facilities, etc). - Access control to Information that can not be public (A-side organization, Z-Side Organization, PathPanel/Port). And some workflow - Cross Connect Requiremento/Authorization from A-Side - Acceptance/Authorization from Z-side. - Acceptance/Authorization from Facilities involved (could be more than one) - Execution/Activation notice from Facilities. -- Douglas Fernando Fischer Engº de Controle e Automação

5 17

Wave Peering Contacts
by Michael Crute 22 Feb '21

22 Feb '21

Is there anyone from Wave Broadband (AS11404) around here that can contact me off-list? Trying to resolve some public IX peering issues. None of the usual contacts are responding. ~mike

1 0

Re: Famous operational issues
by Regis M. Donovan 22 Feb '21

22 Feb '21

On Thu, Feb 18, 2021 at 07:34:39PM -0500, Patrick W. Gilmore wrote: > And to put it on topic, cover your EPOs I worked somewhere with an uncovered EPO, which was okay until we had a telco tech in who was used to a different data center where a similar looking button controlled the door access, so he reflexively hit it on his way out to unlock the door. Oops. Also, consider what's on generator and what's not. I worked in a corporate data center where we lost power. The backup system kept all the machines running, but the ventilation system was still down, so it was very warm very fast as everyone went around trying to shut servers down gracefully while other folks propped the doors open to get some cooler air in. --r

3 2