August 2022 - Test - lists.nanog.org

Request for help: academic study (questionnaire)
by Etienne-Victor Depasquale 04 Oct '22

04 Oct '22

Hello NANOGers, I'm asking for your help through your response to a questionnaire that forms part of an academic study that I'm carrying out <https://forms.gle/AAJokyg98JLW7Ti6A>. The study is directed solely towards facilitating understanding of metro area networks, for analysts who approach from the perspective of energy consumption. The study is anonymous (no individual or company names are solicited), and individual responses will only be used in aggregate. I shall send a digest of the survey to the mailing list, and will correspond with respondents who would like a copy of the paper which I intend to produce with the results. Yours sincerely, Etienne -- Ing. Etienne-Victor Depasquale Assistant Lecturer Department of Communications & Computer Engineering Faculty of Information & Communication Technology University of Malta Web. https://www.um.edu.mt/profile/etiennedepasquale

1 5

RFC: BOGONs over BGP, adding some ranges
by James Shank 06 Sep '22

06 Sep '22

Dear NANOG! As many of you know, Team Cymru runs a free service delivering updated BOGONS to networks around the world. We've been doing this for decades at this point. For more information about this service, please see https://www.team-cymru.com/bogon. Recently, we've discussed internally a discrepancy between our BGP based feed and the other formats we deliver for our Traditional BOGONS feed. For historic reasons, we previously omitted delivery of some ranges that are BOGONS from our BGP advertisements. We are considering adding the below ranges back in, but want to hear feedback from the community on these ranges prior to advertising them, out of an abundance of caution. The below ranges are what we are currently considering advertising: 0/8 (this one we already have concluded is safe as it is already advertised in our "FULL BOGONS" set.) 127/8 224/4 240/4 Note that 224/4 and 240/4 may be aggregated differently in our advertisement, but are broken out here to facilitate discussion. So, fellow NANOGers, what say ye? I would love to hear your feedback, pro or con, well-reasoned with data points or general "argh! there be dragons!" sentiments. Looking forward to seeing folks in Hollywood for N86! Cheers! James -- *James Shank* Chief Architect of Community Services and Sr. Security Evangelist e: jshank(a)cymru.com o: +1 847 378-3365

7 7

Extended Deadline and Reminder OARC 39 - Call for Contribution
by John Todd 31 Aug '22

31 Aug '22

OARC 39 will be a two-day hybrid meeting held on 22 & 23 October in Belgrade, Serbia at 10:00 AM (Local time - CEST (UTC+02:00)) The onsite part of the meeting will be colocated with RIPE 85. 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: DNS config management and release process. Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. Scaling: DNS performance management and metrics. Increasing DNS Server Efficiency Security/Privacy: DNSSEC signing and validation, key storage, rollovers, qname minimization, DoH/DoT Note: OARC 39 will be a joint conference with CENTR and abstract submissions from CENTR members are welcome. As it is an hybrid workshop, we'd like to encourage brevity; presentations should not be longer than 20 minutes (with additional time for questions). Workshop Milestones: 2022-07-30 Submissions open via Indico 2022-09-06 Deadline for submission (23:59 UTC) 2022-09-08 Preliminary list of contributions published 2022-09-20 Full agenda published 2022-10-03 Deadline for slideset submission and Rehearsal 2022-10-22 OARC 39 Workshop - Day1 2022-10-23 OARC 39 Workshop - Day2 The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc39> 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 39 - 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 = Remote speakers have mandatory rehearsal on 2022-10-04 at 14:00 UTC. It would be very useful to have your slides (even if draft) ready for this. Note: DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented groups to speak at and/or attend DNS-OARC. More details will be provided when registration opens. 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.)

1 0

N86 Registration is Open + 2022 Election Cycle is Here!
by Nanog News 31 Aug '22

31 Aug '22

*NANOG 86 Registration is Now Open! * *Our 86th community-wide gathering is 17-19 Oct 2022* Join us in person or virtually for our next meeting, NANOG 86! Don't miss your chance to experience hours of ground-breaking industry talks, legendary keynote speakers, opportunities for networking + more. Standard registration rates are in effect until October 10th. *REGISTER NOW * <https://www.nanog.org/events/nanog-86/> *2022 Election Cycle is Here!* *Your Voice. Your Vote. Play a Role in Shaping NANOG's Future* - If you would like to self-nominate, verify that you are logged in with your NANOG Member credentials, then complete the "Candidate Nomination" form. - If you would like to nominate someone else, send their name and email address to nominations(a)nanog.org. - Nominations close on 14 Sep 2022 at 11:59 pm PDT. *LEARN MORE * <https://www.nanog.org/members/elections/elections-nominations/> *Meet NANOG's Newest Team Member* *A Conversation w/ Software "Craftsman" Greg Newman* Get to know a new face at NANOG! After 21 years of working full-time freelance, software "craftsman" Greg Newman has joined our small but mighty team. Learn more about Greg's background, including his incredible talent for drawing portraits and wildlife art. *READ NOW* <https://www.nanog.org/stories/meet-nanogs-newest-team-member/>

1 0

Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)
by Fernando Gont 31 Aug '22

31 Aug '22

Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a while now -- one of the most common cases being ISPs rotating home prefixes, and your devices ending up with stale/invalid addresses. We have done quite a bit of work already: * Problem statement: https://datatracker.ietf.org/doc/html/rfc8978 * CPE recommendations: https://datatracker.ietf.org/doc/html/rfc9096 But there's still some work to do to address this issue: The last remaining it is to improve SLAAC such that hosts can more gracefully deal with this renumbering events. In that light, IETF's 6man has been working on this document: https://www.ietf.org/archive/id/draft-ietf-6man-slaac-renum-04.txt And we have proposed a simple algorithm for SLAAC (an extension, if you wish) that can easily help, as follows: If you (host) receive an RA that contains options, but not all of the previously-received options/information, simply send a unicast RS to the local-router, to verify/refresh that such missing information is still valid. If the information is stale, get rid of it. I presented this algorithm at the last IETF meeting (https://youtu.be/eKEizC8xhhM?t=1308) (You may find the slides here: https://datatracker.ietf.org/meeting/114/materials/slides-114-6man-improvin…) Finally, I've sent draft text for the specification of the algorithm here: https://mailarchive.ietf.org/arch/msg/ipv6/KD_Vpqg0NmkVXOQntVTOMlWHWwA/ We would be super thankful if you could take a look at the draft text (i.e., https://mailarchive.ietf.org/arch/msg/ipv6/KD_Vpqg0NmkVXOQntVTOMlWHWwA/) and provide feedback/comments. If you can post/comment on the 6man wg mailing list (https://www.ietf.org/mailman/listinfo/ipv6) that´d be fabulous. But we'll appreciate your feedback off-line, on this list, etc. (that'd still be great ;-) ) Thanks in advance! Regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494

2 3

Disney+ Contact
by Mark Tinka 31 Aug '22

31 Aug '22

Hi all. Anyone from Disney who can help with a geo issue on-list? We have customers in South Africa mapping to India. Thanks. Mark.

2 2

BendTel ASN27008 moving router tonight
by Tim Howe 31 Aug '22

31 Aug '22

Between 9 and 11pm tonight our colo provider must move our router to a new rack. I'll shut down bgp a bit after 9pm and then restore once I verify the router is back up correctly and interfaces are normalized. -- Tim Howe tim.h(a)bendtel.com Data Processing 541-389-8252 BendTel GPG pubkey id: CBDE9FFE

1 1

Re: [anti-abuse-wg] Yet another BGP hijacking towards AS16509
by Ronald F. Guilmette 30 Aug '22

30 Aug '22

In message <CAO3CAMoT9gC_Evd-CcZg06A-o_MajmLtxLHbXFnauDoMyqoSYg(a)mail.gmail.com>, Siyuan Miao <siyuan(a)misaka.io> wrote: >Hjacking didn't last too long. AWS started announcing a more specific >announcement to prevent hijacking around 3 hours later. Kudos to Amazon's >security team :-) Sorry. I'm missing something here. If the hijack was of 44.235.216.0/24, then how did AWS propagate a "more specific" than that? Regards, rfg

4 3

IPv6 on Lumen/CL
by Nathan Anderson 29 Aug '22

29 Aug '22

We have a circuit on AS209 that was originally provisioned v4-only. I'm now trying to get Lumen to turn v6 up on it. How long does this typically take? I've had a configuration ticket open for nearly 3 biz days now with no movement (or even acknowledgement). For anybody who has gone through this with them, is this unusual or nah? When they do get around to it, what can I expect in terms of how they will prefer to set this up? Separate BGP session running over v6 itself, or modify existing session to have it also carry v6 NLRIs? Thanks, -- Nathan

2 1

VZ FIOS and Intel TCP IPv6 Checksum Offload problems
by Sean Donelan 29 Aug '22

29 Aug '22

Hopefully, my pain will help someone else. I've had sporadic Internet slowdowns and stuck networking since IPv6 was enabled on my FIOS ONT a few months ago. After too much troubleshooting, I found out some older Intel GbE ethernet cards have a IPv6 Checksum Offload incompatibility with certain fiber ONT terminals. As Verizon is enabling IPv6 on its FIOS network, you might find intermittent network problems. Intermittent are the worst kind of problems. In some situations where a client machine is connected via some specific Optical Network Terminals (ONTs), and data is appended after the packet checksum, the network adapter can drop receive packets when using TCP-IPv6 Checksum Offload for receive traffic. Intel published an alert in 2017, but I didn't have IPv6 on FIOS then. https://www.intel.com/content/www/us/en/download/19174/disabling-tcp-ipv6-c… TLDR; turn off TCP IPv6 Checksum Offload Affects all operating systems (Windows, BSD, Linux, etc) using the affected wired Intel ethernet controllers. Not a problem with Intel WiFi.

7 8