June 2022 - NANOG - lists.nanog.org

Re: Congrats to AS701
by Christopher Morrow 16 Jun '22

16 Jun '22

On Sat, Jun 11, 2022 at 11:03 PM Darrel Lewis (darlewis) <darlewis(a)cisco.com> wrote: > I, for one, am having a hard time finding the proper words to express the > joy that I am feeling at this momentous moment! > > It's quite amazing, I think... that it's taken so long to get to deployment you can actually see on the fios plant :) I'd note I can't see the below on my homestead, but I can at a relative's (where the ifconfig data is from). I also can't tell if the upstream will PD a block to the downstream... and the VZ CPE is 'not something I want to fiddle with', because everytime I have tried at my house I've just taken it out behind the woodshed with a maul... and replaced it with something I CAN configure successfully. (plus.. don't want that TR 069 in my home...) -chris > -Darrel > > On Jun 11, 2022, at 7:05 PM, Christopher Morrow <morrowc.lists(a)gmail.com> > wrote: > > > > Looks like FIOS customers may be getting ipv6 deployed toward them, > finally: > > ifconfig snippet from local machine: > inet6 2600:4040:2001:2200:73d2:6bcc:1e6b:43a1 prefixlen 64 > scopeid 0x0<global> > inet6 2600:4040:2001:2200:e87:bf36:b6cb:6ce1 prefixlen 64 > scopeid 0x0<global> > > ping attempt: > 64 bytes from bh-in-f106.1e100.net (2607:f8b0:4004:c09::6a): icmp_seq=1 > ttl=59 time=8.71 ms > > 8ms from mclean, va to ashburn, va isn't wondrous, but at least it's ipv6 > (and marginally faster than ipv4) > > Congrats to the 701 folk for deploying more widely! > (note: I don't know exactly when this started, nor how wide it really > is, but progress here is welcomed by myself at least :) ) > -chris > >

7 7

Bgpmon alternative
by Mehmet Akcin 15 Jun '22

15 Jun '22

Hi there What are the best alternatives to BGPmon these days? Goal is to try to monitor bgp routing changes for specific prefixes. Mehmet -- Mehmet +1-424-298-1903

10 9

Contact at NameCheap?
by Anne Mitchell 15 Jun '22

15 Jun '22

Does anyone have a technical contact or an abuse contact at NameCheap? Thank you in advance! Anne -- Anne P. Mitchell, Attorney at Law CEO Institute for Social Internet Public Policy Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Author: The Email Deliverability Handbook Board of Directors, Denver Internet Exchange Dean Emeritus, Cyberlaw & Cybersecurity, Lincoln Law School Prof. Emeritus, Lincoln Law School Chair Emeritus, Asilomar Microcomputer Workshop Counsel Emeritus, eMail Abuse Prevention System (MAPS)

1 0

Wired: Russia Is Taking Over [portions of] Ukraine’s Internet
by Sean Donelan 15 Jun '22

15 Jun '22

As always, complicated things are complicated. After Crimea was annexed by Russia, they learned the importance of controlling the telecommunications infrastructure. No, Russia did not cut a submarine cable, because there was no submarine cable connecting Crimea. In the old days, pre-1960s, invaders & revolutionaries would take over the capital city AM/shortwave radio station. Now they take over the ISPs and telecommunications. Russia Is Taking Over Ukraine’s Internet In occupied Ukraine, people’s internet is being routed to Russia—and subjected to its powerful censorship and surveillance machine. https://www.wired.com/story/ukraine-russia-internet-takeover/ [...] Technical analysis confirms that the connections are switching. Internet monitoring company Cloudflare has observed KhersonTelecom’s traffic passing through Miranda Media for more than two weeks in June. Doug Madory, director of internet analysis at monitoring firm Kentik, has observed around half a dozen networks in Kherson connecting to the provider. “It's not a one-time thing,” Madory says. “Every couple of days, there's another company getting switched over to Russian transit from Ukraine.” [...]

1 0

LACNOG2022 - Call for Presentations
by Hernan Moguilevsky 14 Jun '22

14 Jun '22

Dear NANOG, LACNOG 2022 - Call for Presentations https://www.lacnog.org/eventos/ <http://www.lacnog.org/eventos/> LACNOG, the Latin American and Caribbean Network Operators Group, will hold its LACNOG 2022 conference together with the LACNIC 38 event from 3 to 7 October 2022. This meeting will be held in person in the city of Santa Cruz, Bolivia (provided that the evolution of the epidemiological situation in the region allows). Otherwise, the conference will once again be held online. The LACNOG 2022 Program Committee invites the Internet community to submit their presentation proposals for the event. In line with the spirit of LACNOG, presentations should address topics geared towards regional Internet development. The following is a non-exhaustive list of some of the topics of interest for the LACNOG 2022 meeting: ●Network operation and professional experiences, success stories ●Internet of Things ●MANRS ●Community networks ●IPv6 integration and deployment ●Experiences involving botnets, malware, spam, viruses, denial of service attacks, and exploit techniques ●IP network architecture, sizing, configuration, and administration ●Routing and switching protocols, including unicast, multicast, anycast, SDN, etc. ●End-user applications (e.g., e-mail, HTTP, DNS, NFVs, etc.) ●Value-added services, such as VPNs, distributed systems, cloud computing, etc. ●Peering, Internet traffic exchange, IXPs ●Network data security and management, attack mitigation ●Network monitoring, performance, measurements, and telemetry ●Network automation, evolution, and convergence ●Infrastructure and physical transport, including optical and wireless networks ●Legislation, regulations, and Internet governance issues ●Research and education Possible presentation formats include: ●Lightning talk: brief, 10-minute presentation (including a space for Q&A). ●Presentation: 20-minute presentation (including a space for Q&A). ●Poster: includes a single-page PDF (A2 or smaller) with the basic information of the presentation and a 2- to 5-minute video with the presentation. The timeline for the 2022 call for proposals will be as follows: * Reception of proposals: 31 May to 17 July 2022 * Proposals will be accepted until: 17 July 2022 at 23:59 UTC-3 (Uruguay time) * Evaluation by the Program Committee: 18 July to 7 August 2022 * Announcement of results: 10 August 2022 * Reception of final presentations: 10 August to 18 September 2022 at 23:59 UTC-3 (Uruguay time) * Event date: 3 to 7 October 2022 Applicants must submit a summary and a draft of the slides of their proposed presentation along with a brief biography, for which they must use the form available at https://eventos.nog.lat/e/lacnog2022 <applewebdata://6F7DE8E8-1AC5-4759-93B1-180B907F9D82/%20%20> If your work is selected, you authorize LACNOG and LACNIC to publish your name, photograph, biography, and final work in the event program. Speakers presenting their work at the LACNOG 2022 conference will receive a certificate acknowledging their participation. Guidelines for Submitting a Presentation for LACNOG including a description of the criteria that will be considered when evaluating each proposal, presentation format, and other details are available at https://lacnog.org/seccion/postulacion-trabajos <https://lacnog.org/seccion/postulacion-trabajos> Communications with the Program Committee will be handled through pc(a)lacnog.org <mailto:pc@lacnog.org>. We thank you in advance for your attention and look forward to receiving your proposals for LACNOG 2022. The Program Committee

2 1

FCC Reminds Small Providers of June 30 STIR/SHAKEN Deadline
by Sean Donelan 14 Jun '22

14 Jun '22

The Wireline Competition Bureau reminds non-facilities-based small voice service providers that they must implement the STIR/SHAKEN caller ID authentication framework in their Internet Protocol networks no later than June 30, 2022. https://www.fcc.gov/document/fcc-reminds-small-providers-june-30-stirshaken…

1 0

Fwd: [lacnog] LACNOG2022 - Call for Presentations
by Carlos M. Martinez 14 Jun '22

14 Jun '22

FYI, Come join NANOG’s kid brother from the South ! :-) This year’s event will be hybrid, so traveling shouldn’t be an issue. Cheers! /Carlos Forwarded message: > From: Jorge Villa vía LACNOG <lacnog(a)lacnic.net> > To: Latin America and Caribbean Region Network Operators Group > <lacnog(a)lacnic.net> > Cc: Jorge Villa <villa(a)reduniv.edu.cu> > Subject: [lacnog] LACNOG2022 - Call for Presentations > Date: Tue, 14 Jun 2022 08:52:53 -0400 > > LACNOG 2022 - Call for Presentations > > > > LACNOG, the Latin American and Caribbean Network Operators Group, will > hold its LACNOG 2022 conference together with the LACNIC 38 event from > 3 to 7 October 2022. This meeting will be held in person in the city > of Santa Cruz, Bolivia (provided that the evolution of the > epidemiological situation in the region allows). Otherwise, the > conference will once again be held online. > > > > The LACNOG 2022 Program Committee invites the Internet community to > submit their presentation proposals for the event. > > > > In line with the spirit of LACNOG, presentations should address topics > geared towards regional Internet development. The following is a > non-exhaustive list of some of the topics of interest for the LACNOG > 2022 meeting: > > > > ● Network operation and professional experiences, success > stories > > ● Internet of Things > > ● MANRS > > ● Community networks > > ● IPv6 integration and deployment > > ● Experiences involving botnets, malware, spam, viruses, > denial of service attacks, and exploit techniques > > ● IP network architecture, sizing, configuration, and > administration > > ● Routing and switching protocols, including unicast, > multicast, anycast, SDN, etc. > > ● End-user applications (e.g., e-mail, HTTP, DNS, NFVs, etc.) > > ● Value-added services, such as VPNs, distributed systems, > cloud computing, etc. > > ● Peering, Internet traffic exchange, IXPs > > ● Network data security and management, attack mitigation > > ● Network monitoring, performance, measurements, and > telemetry > > ● Network automation, evolution, and convergence > > ● Infrastructure and physical transport, including optical > and wireless networks > > ● Legislation, regulations, and Internet governance issues > > ● Research and education > > > > Possible presentation formats include: > > > > ● Lightning talk: brief, 10-minute presentation (including a > space for Q&A). > > ● Presentation: 20-minute presentation (including a space for > Q&A). > > ● Poster: includes a single-page PDF (A2 or smaller) with the > basic information of the presentation and a 2- to 5-minute video with > the presentation. > > > > The timeline for the 2022 call for proposals will be as follows: > > > Reception of proposals: 31 May to 17 July 2022 > Proposals will be accepted until: 17 July 2022 at 23:59 UTC-3 (Uruguay > time) > Evaluation by the Program Committee: 18 July to 7 August 2022 > Announcement of results: 10 August 2022 > Reception of final presentations: 10 August to 18 September 2022 at > 23:59 UTC-3 (Uruguay time) > Event date: 3 to 7 October 2022 > > > > > Applicants must submit a summary and a draft of the slides of their > proposed presentation along with a brief biography, for which they > must use the form available at https://eventos.nog.lat/e/lacnog2022 > > > > If your work is selected, you authorize LACNOG and LACNIC to publish > your name, photograph, biography, and final work in the event program. > > > > Speakers presenting their work at the LACNOG 2022 conference will > receive a certificate acknowledging their participation. > > > > Guidelines for Submitting a Presentation for LACNOG including a > description of the criteria that will be considered when evaluating > each proposal, presentation format, and other details are available at > https://lacnog.org/seccion/postulacion-trabajos > > > > Communications with the Program Committee will be handled through > pc(a)lacnog.org. > > > > We thank you in advance for your attention and look forward to > receiving your proposals for LACNOG 2022. > > > > The Program Committee > _______________________________________________ > LACNOG mailing list > LACNOG(a)lacnic.net > https://mail.lacnic.net/mailman/listinfo/lacnog > Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog

1 0

Contact at Network Solutioins?
by Anne Mitchell 13 Jun '22

13 Jun '22

Does anyone have a technical contact at NetSol? We need to figure out something and have done everything that we can on our end. Thank you in advance! Anne --- Anne P. Mitchell, Attorney at Law CEO Institute for Social Internet Public Policy Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Board of Directors, Denver Internet Exchange Dean Emeritus, Cyberlaw & Cybersecurity, Lincoln Law School Prof. Emeritus, Lincoln Law School Chair Emeritus, Asilomar Microcomputer Workshop Counsel Emeritus, eMail Abuse Prevention System (MAPS)

1 0

[Story] When IPv6 Fixes IPv4 Peering Issues
by Brielle 13 Jun '22

13 Jun '22

Hi all, So fun story for you all, and a good lesson as to why spending the time to set up IPv6 can save your ass in a pinch. The players in this story are Me (and the company I consult with for when they have problems like this), Comcast (gig biz fiber), and CenturyLink (1/4th gig biz fiber). Now, some of you who have Comcast and/or CenturyLink/Lumen probably remember issues last year regarding IPSec traffic getting heavily fouled up at peering points somewhere. And, if you were like me, you probably remember that it was, well, lets be honest, impossible to get it looked into or dealt with (in reality). We resolved the issue ourselves between the three offices by switching to WireGuard which magically made the problems go away. Things have been going great until last week, when we noticed one of our WireGuard peers between CL/Lumen in Cheyenne and Comcast Denver was down. Packets from Den -> Cys were going through, but not Cys -> Den. Cys -> Boise on CL was still working perfectly fine and was acting as a backup connection to the Den office. I did my usual testing - changed ports, same behavior, changed IPs on the WireGuard endpoints on each end, same behavior. Even temp changed destination of the tunnel on Cys end to another off network node, and packets were going through, so we knew it had to be something relating going CL/Lumen -> Comcast. Weird thing was, I could dump iperf udp traffic over the same ports from same devices Cys -> Den, and the packets would go through perfectly fine... So.. sounds like there's some sort of throttling or IDS in the way somewhere toying with things. As expected, our first dealing with Comcast was less than spectacular where the tech tried to tell us that the live IPs they had assigned us, because they were a /27, they wouldn't work for VPN traffic (what?). I had to walk away from that call and let my partner finish it. We went to dinner, and as we were returning home and pulling into the driveway, I remembered we had 'wasted' (as some of you would put it) a bunch of time setting up IPv6 on the outward facing devices at each office... including the WireGuard boxes. I quickly reconfigured the Cys WireGuard node to connect to the Den node over IPv6 and, after WireGuard did its magic dynamically reconfiguring endpoints, suddenly the connection was back up and routing at full speed. Hell yeah! So, moral / TLDR of the story? Don't discount taking the time to set up IPv6, even if it's just for your important devices. Also, WireGuard > IPsec. -- Brie Sent from my iPad

6 6

Comcast Network Peer Survey on DSCP/ECN for L4S
by Livingood, Jason 13 Jun '22

13 Jun '22

Hi – Comcast is working on the implementation of ultra-low latency networking, leveraging the IETF’s upcoming L4S standard. This standard will require passing ECN and DSCP markings across network boundaries. As a result, we are interested in your perspective on this and in how you handle markings today. We have a short survey that should only take a few minutes to complete. Take the survey at https://forms.office.com/r/vGb0LUXfS1 While any network operator is welcome to take this, we are particularly interested in any networks that are directly interconnected with us today. Thank you! Jason Livingood Comcast – Technology Policy & Standards jason_livingood(a)comcast.com PS – Apologies if any of you get a duplicate of this request via other channels.

3 2