dnsop working group at#IETF115 If you have ideas about the future of the #DNS, it is time to voice them. https://datatracker.ietf.org/meeting/115/materials/agenda-115-dnsop-03
First big issue : the .ALT TLD. A TLD for non-#DNS resolution systems. Quite politically loaded... (ICANN, alternative roots, etc)
Proposal to move it to Working Group Last Call.
#DNS error reporting was tested at the hackathon two days ago. "What we learned: the food was amazing."
This technique allows a DNS resolver to report to the operatior of a domain, not to the client (like RFC 8914 does).
Now, caching of #DNS resolution failures. The Facebook breakage on october 2021 showed that many resolvers keep trying and overload the parent name servers. The goal is to be more specific that resolvers MUST cache resolution failures.
@bortzmeyer You’re thinking of things like jsonschema for instance? There are a few standardizations that exist and is widely supported in many programming languages
@immae The idea was to replace a network protocol (DNS) by an API, since, in that use case, client and server are on the same machine.
So a network "API" would not help.
mastodon.immae.eu is one server in the network