#ietf123 — Public Fediverse posts

#IETF123 Bad Attitude Pecha Kucha -- Let's talk about problems: The image of #DNSSEC
by Barbara from #deSEC (@ItsAutomatic )
https://youtu.be/7mQ5x7Jpj4I?feature=shared

I am definitely on the "best shot at #DNS security so far" side…

In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html

#IETF123

The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/

#ietf123 oauth wg session Brian Campbell about SD-JWT VC

Some subtle jokes included ;-)
Some not so subtle

https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-10

Ducks before heading off to the airport 🦆 :) #ietf123

Do I want to know why there is an ambulance outside #ietf123 ?

This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols

The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/

Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"

Just by sending the results of a resolution to your friends.

Implemented in Unbound at the IETf hackathon

#IETF123

Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).

Zone cut to nowhere:

internal.example.com. IN NS .

#DNS #IETF123

Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)

https://mastodon.gougere.fr/@DNSresolver/114913405013969936

#IETF123

@drk asking a question that's more of a comment (just kidding, he had both comments and questions) at the Friday Inter-Domain Routing session. #IETF123

#IETF123 in Madrid has been great! I ran an open side-meeting and had many conversations about bringing atproto as work. really appreciate the community for being welcoming and receptive.

DNSOP working group: a lot of small (and somestimes not so small) changes to #DNS https://datatracker.ietf.org/meeting/123/materials/agenda-123-dnsop-01

First: persistent references to services you authorize (such as CAA, wallets or also what Bluesky is doing). Related but not identical to TXT-based validation with a cookie/nonce/token in it.

#IETF123

#ietf123 current status

Good morning, Madrid! Fifth (and last) day of #IETF123 https://www.ietf.org/meeting/123/

For me, today, DNSOP (misc. #DNS stuff) and, unfortunately, no RPP (domain name provisioning), I have an early plane.

Discussion in the group about writing all RFCs as just formal specification language and then use a LLM to generate a natural language description.

#IETF123 #AI #RFC

Many Internet protocols are already specified in EverParse (but not #DNS, alas).

#IETF123

Presentation of Microsoft's EverParse system, which generates safe parsers from formal and validated specifications.

#IETF123

A bit of formality, now. "Usable Formal Methods Research Group" https://datatracker.ietf.org/meeting/123/materials/agenda-123-ufmrg-00

#IETF123

Cool set of tools linked to today in a presentation in the #IETF #HAPPYWG session:

https://www.happy-eyeballs.net/

It allows you to characterize the Happy Eyeballs behavior of a client, such as to see how much of a delay in DNS resolution or TCP connection response triggers a failback from IPv6 to IPv4.

See more details in Dave Plonka's talk:

https://datatracker.ietf.org/meeting/123/materials/slides-123-happy-hackathon-maprg-happy-eyeballs-and-ipv6-test-pod-open-testing-00

#HappyEyeballs #IPv6 #IETF123

Saying "we must be quantum-resistant" is one thing, deciding what algorithms to use is something else. Specially in a highly regulated industry like the telecoms, and with the desire to be used world-wide with as few changes as possible.

An example: hybridization or not?

#IETF123