- Test - lists.nanog.org

"Hackathon" Solves Real-World Tech Issue + Committee Nominations + More
by Nanog News 13 Jan '22

13 Jan '22

*“Hackathon” Solves Real-World Tech Issue* Code Developed during NANOG Hackathon Goes Live Hackathons are an essential part of NANOG conferences. They are designed as a “fail forward” space where mistakes can be made as learning, having fun + building community is the prime objective. And sometimes this perfect cocktail of sophisticated fun leads to solving real-world technical issues. The work done at the NANOG 83 Hackathon improved the PeeringDB Simple Search and resolved a vital search issue. Thus, allowing PeeringDB (a freely available, user-maintained, database of networks, and a go-to location for interconnection data) to provide more relevant search results for the end-user. The developed code during the Hackathon, officially went live early Wednesday morning (Jan. 12). NANOG had the opportunity to catch up with PeeringDB product manager Leo Vegoda to learn more. *READ MORE <https://www.nanog.org/stories/hackathon-solves-real-world-tech-issue/>* *Now Accepting Committee Nominations* The 2022 Committee Nominations are now open and run through Tuesday, Feb. 15, 2022. Reminder, only NANOG members in good standing are allowed to serve on a NANOG committee. We are currently seeking volunteers for the Program Committee. **If you are not a member and wish to participate in the nomination process, your membership must be received by 9:00 p.m. PST on Tuesday, Feb. 15, 2022.** Click here to review the nomination process and volunteer for a committee! *COMMITTEE NOMINATIONS <https://www.nanog.org/members/elections/committee-nomination-process/>* *NANOG 84 Sponsorships Still Available * NANOG is, and always has been, dedicated to the people who make up our community. Our in-person conferences draw up to 1,500 individuals in multiple facets of network engineering, operations, and architecture, who gather with us in major cities across North America. As a sponsor of NANOG, you’ll help us in our mission to continue cultivating and strengthening our community of networking professionals. *SPONSORSHIP NOMINATIONS <https://www.nanog.org/events/sponsorship/sponsorship-opportunities/>*

1 0

home router battery backup
by james.cutler＠consultant.com 13 Jan '22

13 Jan '22

> On Jan 12, 2022, at 5:11 PM, Scott T Anderson via NANOG <nanog(a)nanog.org <mailto:nanog@nanog.org>> wrote: > > For those individuals with backup battery power for their modem/router, do they maintain Internet access throughout a power outage (as long as their backup power solution works)? I.e., does the rest of the ISP network maintain service throughout a power outage? The answer is, “It depends.” Plymouth in Michigan recently had a substation fire that took out a large fraction of the city. Restoration of the substation was a lengthy process as mobile transformers and the like were required. My Comcast connection was only down for a short time until some generators were dispatched to some pole-mounted equipment within the city. Since my local power comes from a different substation, the brief Comcast outage was the only noticeable event. I frequently hear the UPS beep for short interruptions, confirming that the battery is still strong. My original UPS was installed to ride through momentary outages and to inhibit spikes since spikes and arbitrary power shutdowns can cause damage to both data and equipment. My cable modem, router, network hub, several computers and monitors, and task lighting are all protected from outages for a decent interval followed by a spike-free shutdown. The latter is important, especially as compared to the transients occurring as trees fall on power lines. The 2003 midwest blackout was days long. I helped a friend wire his well pump to a portable generator so one could “flush”. I then grabbed my laptop and took refuge up north outside the outage area. At that time, WFH had long been part of my vocabulary.

1 0

DNS-OARC 37 Call for Presentations
by John Todd 12 Jan '22

12 Jan '22

OARC 37 will be a online/hybrid meeting on February 17th and 18th, 2022 starting at 16:00 UTC (10:00 CST). The onsite part of the meeting will be held in Austin, Texas. 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: - Operations: Any operational gotchas, lessons learned from an outage, details/reasons for a recent outage (how to improve TTR, tooling). - Deployment: Managing DNS changes and propagation, release process, change management. - Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. - Scaling: Managing service capacity, failovers, disaster recovery. As it is an online/hybrid workshop, we'd like to encourage brevity; presentations should not be longer than 20 minutes (with additional time for questions). **Workshop Milestones:** * 27 December 2021 - Submissions open via Indico * 10 January 2022 - Deadline for submission (23:59 UTC) * 11 January 2022 - Initial Contribution list published * 18 January 2022 - Full agenda published * 3 February 2022 - Deadline for slideset submission and Rehearsal * 17 & 18 February 2022 - OARC 37 Workshop The Registration page and details for presentation submission are published at: https://www.dns-oarc.net/oarc37 DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented 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 37: * 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 3rd February 2022. 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> John Todd, 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.) -- John Todd - jtodd(a)quad9.net General Manager - Quad9 Recursive Resolver

1 1

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN73 Community Forum
by Jacques Latour 12 Jan '22

12 Jan '22

Hi all, Happy new year! 8 weeks left before the next virtual ICANN DNSSEC & Security workshop. Let us know if you are interested to present. Jacques Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN73 Community Forum In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN73 Community Forum being held virtually from 05-10 March 2022 in the Atlantic Standard Time Zone (UTC -4). 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 ICANN72 Annual General Meeting on Wednesday 27 October 2021. The presentations and transcripts are available at https://72.schedule.icann.org/meetings/M24SJN375N2rcupnS, https://72.schedule.icann.org/meetings/NQMcvSwdLbpdGPaz6, and https://72.schedule.icann.org/meetings/9g4P3ceRA8FGS34Ei. The DNSSEC Workshop Program Committee is developing a program. 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 ICANN72 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 we 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 and Routing 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-2 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by COB Friday, January 21 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

Responses to my troubles with IP reputation
by Eric C. Miller 10 Jan '22

10 Jan '22

Friends, I just realized that it's been some time since all of this happened. I owe a huge thanks to Sean, Sean, Viktor, Joshua, Tomoc, Nathan, and others that I'm sure that I missed. You all make this a valuable community. Regards, Eric

1 0

SAP contact
by Andy Ringsmuth 10 Jan '22

10 Jan '22

Anyone on here from SAP, or know someone who is? Thanks. Would appreciate an off-list reply. ---- Andy Ringsmuth 5609 Harding Drive Lincoln, NE 68521-5831 (402) 304-0083 andy(a)andyring.com

1 0

2022 NANOG Committee Nominations
by NANOG Member Support 10 Jan '22

10 Jan '22

Dear NANOG Community, Nominations <https://www.nanog.org/members/elections/committee-nomination-process/> are now open for the NANOG Program Committee! The volunteers on the Program Committee are responsible to develop and select content to program each of the three yearly NANOG conferences and other events. The Program Committee is a highly skilled, dedicated and diverse team of people who strive to improve the NANOG organization and make our industry, as a whole, better. Specific committee member responsibilities are listed here <https://www.nanog.org/about/who-we-are/program-committee/> and appointments are to 2 year terms, except when appointed to complete a retiring members term. Committee nominations will close at 9:00pm PST on Tuesday, February 15, 2022. The NANOG Board of Directors will make appointments within the week. Emails detailing the selection results will be sent to candidates shortly thereafter, and a full announcement will be sent during the following week. Volunteer participation by members on NANOG committees is part of the essential fabric of the NANOG organization. Committee members have developed new programs, brought new ideas and new methods into practice, and helped to evolve the NANOG organization. Please consider running for a NANOG committee if you are passionate about NANOG and can commit to participating! If you know someone that you believe would be interested, please nominate them. The nomination forms <https://www.nanog.org/members/elections/2022-committee-candidates-nominatio…> are linked from the 2022 Committee Nominations webpage and accept either self or 3rd party nominations. Board members are available to discuss the opportunities, so do not hesitate to reach out to them if you are interested and want to learn more. As always, you can reach us through our website contact form here <https://www.nanog.org/contact/>, or by email to either nanog-support(a)nanog.org or member-support(a)nanog.org Valerie Wittkop Program Director vwittkop(a)nanog.org | www.nanog.org NANOG | 305 E. Eisenhower Pkwy, Suite 100 | Ann Arbor, MI 48108, USA ASN 19230

1 0

Fwd: [APRICOT-PC-Chairs] APRICOT 2022 Call for Presentations
by Mark Tinka 10 Jan '22

10 Jan '22

FYI. Mark. -------- Forwarded Message -------- Subject: [APRICOT-PC-Chairs] APRICOT 2022 Call for Presentations Date: Thu, 7 Oct 2021 21:16:43 +1000 From: Philip Smith <philip(a)apricot.net> Reply-To: APRICOT PC Chairs <pc-chairs(a)apricot.net> Organization: Asia Pacific Regional Conference on Operational Technologies To: apops(a)apops.net CC: APRICOT PC Chairs <pc-chairs(a)apricot.net> Hi everyone, Please find below the call for presentations for APRICOT 2022! :-) Best wishes, philip -- APRICOT 2022 21st February - 3rd March, Online https://2022.apricot.net CALL FOR PRESENTATIONS ====================== The APRICOT 2022 Programme Committee is now seeking contributions for Presentations and Tutorials for the APRICOT 2022 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; Please submit on-line at: http://papers.apricot.net/user/login.php?event=142 Tutorials will take place during the week of 21st February. Conference sessions and the Peering Forum will take place on the week of 28th February. All APRICOT 2022 session times will be one hour long, with up to four sessions scheduled per day. CONFERENCE MILESTONES --------------------- Call for Papers Opens: Now Initial Draft Programme: 6th December 2021 Final Deadline for Submissions: 31st January 2022 Final Program Published: 7th February 2022 Final Slides Received: 14th February 2022 *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: - IPv4 / IPv6 Routing and Operations - Internet backbone operations - Routing Security, including RPKI and MANRS - Peering, Interconnects and IXPs - Network Function Virtualisaton - Network Automation/Programming - Content Distribution Network technology & operations - Research on Internet Operations and Deployment - Network infrastructure security - IPv6 deployment on fixed and Wireless/Cellular networks - DNS / DNSSEC - Access and Transport Technologies - Content & Service Delivery and "Cloud Computing" PEERING FORUM ------------- Due to APRICOT 2022 being held online, the PC will only accept Peering Personals prior to the event starting. Submissions must be of a single slide listing the operator's PeeringDB entry. Please refer to https://tinyurl.com/y46954n5 for how to create a successful Peering Personal presentation. 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 time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Slides must be of original work, preferably not presented before at other venues, with all company confidential marks removed. 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. For any questions or concerns, please email the PC Chairs. We look forward to receiving your presentation proposals. Mark Tinka, Tugsorshikh Badarch & Marijana Novakovic Co-Chairs, APRICOT 2022 Programme Committee -- -- To unsubscribe from this group and stop receiving emails from it, send an email topc-chairs+unsubscribe(a)apricot.net.

1 1

Spoofer Report for NANOG for Dec 2021
by CAIDA Spoofer Project 08 Jan '22

08 Jan '22

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 Dec 2021: ASN Name Fixed-By 54825 PACKET 2021-12-03 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Dec 2021: ASN Name First-Spoofed Last-Spoofed 577 BACOM 2016-03-09 2021-12-29 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2021-12-30 20412 CLARITY-TELECOM 2016-09-30 2021-12-31 6181 FUSE-NET 2016-10-10 2021-12-27 11427 TWC-11427-TEXAS 2016-10-21 2021-12-24 32440 LONI 2016-11-03 2021-12-30 12083 WOW-INTERNET 2016-11-09 2021-12-22 1403 EBOX 2016-11-12 2021-12-08 22898 ATLINK 2016-12-16 2021-12-28 54119 BOINGO-MDU 2017-04-14 2021-12-30 701 UUNET 2017-06-14 2021-12-04 63296 AWBROADBAND 2017-09-01 2021-12-28 546 PARSONS-PGS-1 2017-11-20 2021-12-23 12222 AKAMAI 2018-02-14 2021-12-30 33452 RW 2018-09-19 2021-12-31 62904 EONIX-COMMUNICATIONS-ASBLOCK-6 2019-07-14 2021-12-29 398836 NP-NETWORKS 2021-03-12 2021-12-31 56207 Converge 2021-03-26 2021-12-01 399318 2021-08-29 2021-12-27 63457 EMPIRE-CONNECT 2021-09-08 2021-12-30 212934 AS_POTVIN 2021-10-03 2021-12-27 22773 ASN-CXA-ALL-CCI-22773-RDC 2021-10-24 2021-12-29 46449 ASTREA-NORTHWI-WESTUPMI 2021-11-07 2021-12-30 394437 PSLIGHTWAVE 2021-12-02 2021-12-27 62887 WHITESKY-COMMUNICATIONS 2021-12-03 2021-12-29 54201 WEWORK-MANAGEMENT-LLC 2021-12-16 2021-12-16 139247 2021-12-22 2021-12-22 46997 NATOLAB 2021-12-22 2021-12-29 5009 EATEL 2021-12-26 2021-12-26 4922 SHENTEL 2021-12-28 2021-12-28 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

Cloudflare Abuse Contact
by Mike Hale 08 Jan '22

08 Jan '22

Hi all, Does anyone have a cloudflare abuse contact? The email address in the whois doesn't actually go to their abuse team, and their abuse form doesn't address the issue we're seeing (a massive DNS flood). Thank you much! - Mike -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

7 7