- NZNOG - lists.nznog.org

Routing Security - APRICOT - Call for Papers
by J Bateman 11 Jan '24

11 Jan '24

Dear NOG members, *Routing Security - Special Interest Group (SIG) - Call for Papers!* When: APRICOT, Bangkok, Thailand February 29th 9.30-11am Topics: Routing Security. Interested in everything from real world deployments, operations and maintenance, research, or new ideas. Call For Presentations Open: Now Deadline for Submission: February 1st 2024 Acceptance Notification: February 7th 2024 https://2024.apricot.net/ Please submit the presentation by email to sig-routingsecurity-chair(a)apnic.net Kind Regards, APNIC Routing Security SIG Chairs

2 1

Re: sigs wanted for a response to the fcc's NOI for faster broadband speeds
by Dave Taht 02 Dec '23

02 Dec '23

On Fri, Dec 1, 2023 at 6:21 PM Tom Samplonius <tom(a)samplonius.org> wrote: > > > > https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY… > > > > Us bufferbloat folk have been putting together a response to the FCC's > > NOI (notice of inquiry) asking for feedback as to increasing the > > broadband speeds beyond 100/20 Mbit. > > > The era of “buffer bloat” has passed. Buffer bloat is just about jitter, and jitter mitigation is just better now. I am really not sure what world you live in. Certainly the problem has got much better since 2010, but nearly every network I ever explore still has vast amounts of it. The global south, every coffee shop, and every hotel I have been in, all have major issues here. I make a habit of testing the conference wifi and posting results at every talk. The apartment complex I am staying in this week has a completely saturated backhaul and oversubscribed wifi, with tremendous amounts of delay and packet loss, where more constructive packet loss would help. Google docs is nearly unusable most of the day... and so it goes. I do hope the solutions for bloat continue to roll out globally and we cross this chasm in the next few years. > I don’t think jitter needs to be part of public policy. Congress has mandated a report from the FCC every year about the state of the internet, which is what this attempt at a constructive policy change of focus was about. > > Tom -- :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab Dave Täht CSO, LibreQos

1 0

Re: sigs wanted for a response to the fcc's NOI for faster broadband speeds
by Dave Taht 01 Dec '23

01 Dec '23

On Fri, Dec 1, 2023 at 1:55 PM Mel Beckman <mel(a)beckman.org> wrote: > > bufferbloat is rarely fatal This task will put me in my grave, sooner rather than later! > > > LOL! I know one person taht may disagree with that :) > > -mel > > On Dec 1, 2023, at 9:41 AM, Tom Mitchell <tmitchell(a)netelastic.com> wrote: > > > Not sure we need the FCC telling us how to build products or run networks. Seat belts are life-or-death, but bufferbloat is rarely fatal ;-) Let it be a point of differentiation. > > -- Tom > > > On Thu, Nov 30, 2023 at 4:56 PM Dave Taht <dave.taht(a)gmail.com> wrote: >> >> Over here: >> >> https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY… >> >> Us bufferbloat folk have been putting together a response to the FCC's >> NOI (notice of inquiry) asking for feedback as to increasing the >> broadband speeds beyond 100/20 Mbit. >> >> "Calls for further bandwidth increases are analogous to calling for >> cars to have top speeds of 100, 200, or 500 miles per hour. Without >> calling also for better airbags, bumpers, brakes, or steering wheels, >> (or roads designed to minimize travel delay), these initiatives will >> fail (and are failing) to meet the needs of present and future users >> of the internet." >> >> Comments (and cites) welcomed also! The text is still somewhat in flux... >> >> >> -- >> :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab >> Dave Täht CSO, LibreQos -- :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab Dave Täht CSO, LibreQos

1 0

Re: sigs wanted for a response to the fcc's NOI for faster broadband speeds
by Dave Taht 01 Dec '23

01 Dec '23

On Fri, Dec 1, 2023 at 12:46 PM Shane Ronan <shane(a)ronan-online.com> wrote: > > If you want money from the government to subsidize your network, you'll follow their rules... It is the misguided focus on too many too simple things from the regulator and Congress, without even understanding what a packet is, and enormous subsidies for things that don't matter, and great mis-understanding of the things that do, that bothers me the most. Anyway, for 14 years, I have been trying to get bufferbloat fixed, universally, and great progress is being made. I felt that with one political push like this, it might begin to turn the tide. We are accepting signatures on the FCC filing until 2PM EST today. https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY… > On Fri, Dec 1, 2023 at 12:39 PM Tom Mitchell <tmitchell(a)netelastic.com> wrote: >> >> Not sure we need the FCC telling us how to build products or run networks. Seat belts are life-or-death, but bufferbloat is rarely fatal ;-) Let it be a point of differentiation. >> >> -- Tom >> >> >> On Thu, Nov 30, 2023 at 4:56 PM Dave Taht <dave.taht(a)gmail.com> wrote: >>> >>> Over here: >>> >>> https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY… >>> >>> Us bufferbloat folk have been putting together a response to the FCC's >>> NOI (notice of inquiry) asking for feedback as to increasing the >>> broadband speeds beyond 100/20 Mbit. >>> >>> "Calls for further bandwidth increases are analogous to calling for >>> cars to have top speeds of 100, 200, or 500 miles per hour. Without >>> calling also for better airbags, bumpers, brakes, or steering wheels, >>> (or roads designed to minimize travel delay), these initiatives will >>> fail (and are failing) to meet the needs of present and future users >>> of the internet." >>> >>> Comments (and cites) welcomed also! The text is still somewhat in flux... >>> >>> >>> -- >>> :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab >>> Dave Täht CSO, LibreQos -- :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab Dave Täht CSO, LibreQos

2 1

sigs wanted for a response to the fcc's NOI for faster broadband speeds
by Dave Taht 01 Dec '23

01 Dec '23

Over here: https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY… Us bufferbloat folk have been putting together a response to the FCC's NOI (notice of inquiry) asking for feedback as to increasing the broadband speeds beyond 100/20 Mbit. "Calls for further bandwidth increases are analogous to calling for cars to have top speeds of 100, 200, or 500 miles per hour. Without calling also for better airbags, bumpers, brakes, or steering wheels, (or roads designed to minimize travel delay), these initiatives will fail (and are failing) to meet the needs of present and future users of the internet." Comments (and cites) welcomed also! The text is still somewhat in flux... -- :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab Dave Täht CSO, LibreQos

1 0

Your Input Needed: Can ROA Replace LOA? – Short Survey (7 mins)
by Christopher Hawker 16 Nov '23

16 Nov '23

Hello everyone, Aftab Siddiqui is currently exploring the possibility of using Route Object Authorisations (ROAs) as a potential replacement to LOAs. Separate to this (and unknowing of Aftab's research), I had started a discussion on the RPKI Community guild on Discord (https://discord.gg/9jYcqpbdRE) discussing the usage of ROAs instead of LOAs. An LOA, or "Letter of Authority" / "Letter of Authorization," is a formal document granting permission for third parties to take specific actions regarding network resources or services. In the service provider industry, its primary use is for advertising address resources (IPv4/v6 and ASN). When an organization intends to announce its IP prefixes through its own or a transit provider's ASN to the global internet, it typically needs to provide an LOA to their transit provider, confirming their custodianship or ownership of the resources. RPKI ROA, stands for "Resource Public Key Infrastructure Route Origin Authorization," is part of a security framework designed to validate the authenticity of internet routing information. It involves a digitally signed object that specifies which Autonomous Systems (ASes) are permitted to announce specific IP address prefixes. Could you please take a moment to fill out our brief survey? Your feedback will play a crucial role in our understanding of this topic. Survey Link: https://www.surveymonkey.com/r/JCHLWBB Thanks, Christopher Hawker

1 0

The Guardian report on Optus Outage
by Mark Foster 14 Nov '23

14 Nov '23

https://www.theguardian.com/business/2023/nov/13/optus-network-outage-cause… A spokesperson confirmed on Monday that the cause of the outage was changes to routing information from an international peering network after a routine software upgrade at 4.05am on Wednesday. "These routing information changes propagated through multiple layers in our network and exceeded preset safety levels on key routers which could not handle these. This resulted in those routers disconnecting from the Optus IP Core network to protect themselves," a spokesperson said. "The restoration required a large-scale effort of the team and in some cases required Optus to reconnect or reboot routers physically, requiring the dispatch of people across a number of sites in Australia. This is why restoration was progressive over the afternoon." There's a meme about how it's always 'one of you three' that came immediately to mind... Mark.

1 0

Re: NZNOG Digest, Vol 248, Issue 5
by William Tiʻitiʻi Asiata Hura 08 Nov '23

08 Nov '23

Please unsubscribe me from your mailing list. On Tue, 24 Oct 2023 at 00:00, <nznog-request(a)list.waikato.ac.nz> wrote: > Send NZNOG mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NZNOG digest..." > > Today's Topics: > > 1. Re: DiscountDomains (Shane Langley) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 23 Oct 2023 07:35:27 +0000 > From: Shane Langley <shane(a)webtastix.net> > Subject: [nznog] Re: DiscountDomains > To: Criggie <criggie(a)criggie.org.nz>, Craig Whitmore > <lennon(a)orcon.net.nz> > Cc: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> > Message-ID: <5faa61d8ce254bf68729a7232f78d834(a)webtastix.net> > Content-Type: text/plain; charset="utf-8" > > Nope, they have been incredibly quiet since that > > -----Original Message----- > From: Criggie <criggie(a)criggie.org.nz> > Sent: Friday, October 20, 2023 12:44 PM > To: Craig Whitmore <lennon(a)orcon.net.nz> > Cc: nznog(a)list.waikato.ac.nz > Subject: [nznog] Re: DiscountDomains > > > On Sep 29, 2023, at 11:03 AM, Shane Langley wrote: > > Just wondering if anyone from DD is on here? Am curious whatÃ¢Â€Â™s > > happened to their nameservers today as theres no updates on the > > network status page but all domains are giving SERVFAIL errors > > Craig Whitmore wrote: > > There is a discussion on : geekzone.co.nz But it's all third party . > > Did anyone ever get any kind of RCA or explanation of what went wrong at > DD that day, three weeks ago? > > Their web site simply says its fixed, without detail. > > > > > > _______________________________________________ > NZNOG mailing list -- nznog(a)list.waikato.ac.nz To unsubscribe send an > email to nznog-leave(a)list.waikato.ac.nz > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > NZNOG mailing list -- nznog(a)list.waikato.ac.nz > To unsubscribe send an email to nznog-leave(a)list.waikato.ac.nz > https://list.waikato.ac.nz/postorius/lists/nznog.list.waikato.ac.nz > > > ------------------------------ > > End of NZNOG Digest, Vol 248, Issue 5 > ************************************* >

1 0

IPv6 status in ANZ
by Mark Prior 07 Nov '23

07 Nov '23

It's been about seven years since I last nagged at AusNOG about the poor state of IPv6 adoption in Oz and it hasn't got any better since :-( And I don't mean the plumbing, I mean the services, I have recently rewritten the script I use to look for IPv6 services (web, mail, dns, ntp, xmpp and sip) and as part of that process I leveraged PeeringDB to find all the domains that claim to connect to an IX in either Australia or New Zealand. As a result I now have two sections on the web page that collect them all together. As an added bonus I also look for DNSSEC, and its deployment makes IPv6 look like a roaring success! The Australian IX member section is <https://www.mrp.net/ipv6_survey/#auix> and the New Zealand IX member section is <https://www.mrp.net/ipv6_survey/#nzix> Of course there will be organisations in both lists but I only probe them once (a day). Start from the top of the page if you want a better understanding of what is being checked (and see some graphs) and check out the link under the domain name to find "diagnostics" about the tests. Regards, Mark.

1 0

APRICOT 2024: Call for Presentations
by Mark 31 Oct '23

31 Oct '23

APRICOT 2024 21st February - 1st March, Bangkok, Thailand https://2024.apricot.net CALL FOR PRESENTATIONS ================= The APRICOT 2024 Programme Committee is now seeking contributions for Presentations and Tutorials for the APRICOT 2024 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; - Lead informal Birds of Feather break out sessions. Please submit on-line at: https://papers.apricot.net/user/login.php?event=186 CONFERENCE MILESTONES ---------------------------------- Call for Papers Opens: Now Outline Programme Published: As Papers Confirmed Final Deadline for Submissions: 29th January 2024 Final Program Published: 5th February 2024 Final Slides Received: 19th February 2024 *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, for example: - IPv4 / IPv6 Routing and Operations - Routing Security, including RPKI and MANRS - Internet backbone operations - Peering, Interconnects and IXPs - Content Distribution Network technology & operations - Research on Internet Operations and Deployment - Network Virtualisation - Network Automation/Programming - Network Infrastructure security - IPv6 deployment on fixed and Wireless/Cellular networks - DNS / DNSSEC and KINDNS - Access and Transport Technologies - Technical application of Web 3.0, public blockchains and cryptocurrency - Content & Service Delivery and "Cloud Computing" - 400G ZR, ZR+ & Open ROADM - Submarine cables - ChatGPT 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 the time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Slides must be of original work, with all company confidential marks removed. Any marketing, sales and vendor proprietary content in a presentation is against the spirit of APRICOT and it is strictly prohibited. Note that proper credit must be given for all content taken from other sources. Evidence of plagiarism is grounds for rejection. 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. Any questions or concerns should be addressed to the Programme Committee Chairs by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mark Tinka, Achie Atienza & Mark Duffell APRICOT 2024 Programme Committee Chairs

1 0