Good bye, Yokohama! Sorry, I have to leave #IETF116 early, for another meeting.

Bientôt à Lyon pour #JDLL (ou #JDLL2023 ?) http://jdll.org/

Registration Extensions working group. https://datatracker.ietf.org/meeting/116/materials/agenda-116-regext-03

#IETF116 #EPP #RDAP

#LLM for standards discours analysis: even the IETF uses GPT-3.

#IETF116

Now, McQuistin on some data about the standardization process. 32 % of RFC have errata, 7 % of the errata are filed within 30 days. reviews could be more thorough.

#IETF116

"I'm an anthropologist"

"What are you doing here in the #IETF? Are you lost?"

#IETF116

Corinne Cath speaking "The hard work of the hum: using ethnography to study power & politics in the #IETF"

Spoiler: IETF does not work in practice as it does in theory

#IETF116

Now, the RASP research group: data about the #IETF processes.

#IETF116

Soon, the book, under a free licence https://github.com/sfc-aqua/Overview-of-Quantum-Communications-E

And the videos: https://www.youtube.com/@QuantumCommEdu

#IETF116

Making the entanglement is itself distributed quantum computation. Every node has to participate. The quantum Internet will be more circuit than datagram.

[Funny note: when you create entanglements, you need to create a lot of them since using them - in a quantum computation - destroys them.]

Routing will be fun, you have to take into account if the link is "good" or "bad" (noisy).

#IETF116

Today, we have quantum repeating (so we can carry the quantum state on some distance) but not yet "real" quantum networks.

#IETF116

Analog -> Digital -> Quantum. From waves to bits then to superposition of states.

#progress #IETF116

RFC 9340 summarizes what is "Quantum Internet". The goal is to be able to run distributed quantum applications.

Basic building block: entanglement (of qubits)

#IETF116

Now, let's go quantum with the talk on "Quantum Internet".

#IETF116

#DNSSEC "black lies" renamed "compact answers". "White lies" remain white?

#IETF116

Demo of an implementation at Vodafone/Akamai. (With a Google Chrome plugin and DoH to the resolver.)

#IETF116 #DNS

Now, draft-ietf-dnsop-structured-dns-error, a proposal to encode the reasons a lying #DNS resolver lied, in the hope it will be displayed to the user. (Redirecting to a Web page does not work, for instance if the HTTP connection was HTTPS.)

JSON in the DNS response :-(

#IETF116

First, something not #DNS: #GNS, the GNU Name System, an alternative to DNS, to fight censorship and provide privacy.

Debian packages at https://deb.taler.net/

In the future .alt TLD, it will be gns.alt.

.fr has been imported into GNS :-)

#IETF116

Let's start with dnsop: everything #DNS https://datatracker.ietf.org/meeting/116/materials/agenda-116-dnsop-04

#IETF116

Good morning, Yokohama! Sixth day of #IETF116. Packed program for me, with #DNS, regext (#EPP and #RDAP), quantum stuff, rasprg (data about #IETF activity), etc.
https://www.ietf.org/how/meetings/116/

RT @ietf
Jun Murai (@shimshamshimmy) founder of @WIDE_Project at the #IETF116 plenary, highlighting all the organizations supporting the meeting this week. https://www.ietf.org/how/meetings/116/