RFC 9859: Generalized DNS Notifications

Le #DNS permet plusieurs sortes de messages, identifiés par un code d'opération. Si QUERY, pour demander à résoudre un nom en informations, est le plus connu, il y a aussi UPDATE et quelques autres. Et il y a NOTIFY, qui sert à indiquer à un serveur DNS qu'il y a du nouveau.

Ce nouveau #RFC généralise le concept et permet d'utiliser NOTIFY pour de nouvelles choses comme un changement dans la liste des serveurs faisant autorité.

https://www.bortzmeyer.org/9859.html

RFC 9874: Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP), S. Hollenbeck, et al., https://www.rfc-editor.org/info/rfc9874 #RFC The Extensible Provisioning Protocol (EPP) includes commands for clients to delete domain and host objects, both of which are used to publish information in the Domain Name System (DNS). EPP also includes guidance 1/3

RFC 9874: Best Practices for Deletion of Domain and Host Objects in #EPP

Dans un registre de noms de domaine, que se passe-t-il si on retire un objet alors que d'autres objets en dépendaient ? Va t-on scier une branche sur laquelle quelqu'un est assis ? Ce #RFC fait le point sur les solutions existantes, notant que certaines sont moins bonnes que d'autres, notamment pour la sécurité.

https://www.bortzmeyer.org/9874.html

RFC 9874: Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP), S. Hollenbeck, et al., https://www.rfc-editor.org/info/rfc9874 #RFC The Extensible Provisioning Protocol (EPP) includes commands for clients to delete domain and host objects, both of which are used to publish information in the Domain Name System (DNS). EPP also includes guidance 1/3

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

And now, since we have to do something against the Quantum Apocalypse, the pquip working group: post-quantum crypto in protocols. https://datatracker.ietf.org/meeting/123/materials/agenda-123-pquip-04

The first #RFC of the group, 9794 (terminology for hybrid schemes), has just been published. Soon, the RFC "PQ crypto for engineers" (introduction and explanations) is almost ready.

#IETF123

RFC erratum https://www.rfc-editor.org/errata/eid8305 is interesting because it is an example of the free-form (natural language) and formal schema in a #RFC saying different things.

#IETF123#EPP

RFC 9805: Deprecation of the IPv6 Router Alert Option for New Protocols, R. Bonica, https://www.rfc-editor.org/info/rfc9805#RFC This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option. This 1/2

RFC 9797: Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases, J. Henry, et al., https://www.rfc-editor.org/info/rfc9797#RFC To limit the privacy issues created by the association between a device, its traffic, its location, and its user in IEEE 802 networks, client vendors and client OS vendors have started implementing Media Access Control 1/4

RFC 9797: Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases, J. Henry, et al., https://www.rfc-editor.org/info/rfc9797#RFC To limit the privacy issues created by the association between a device, its traffic, its location, and its user in IEEE 802 networks, client vendors and client OS vendors have started implementing Media Access Control 1/4

RFC 9799: Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names, Q Misell, Ed., https://www.rfc-editor.org/info/rfc9799#RFC This document defines extensions to the Automated Certificate Management Environment (ACME) to allow for the automatic issuance of certificates to Tor Hidden Services (".onion" Special-Use Domain Names). This document is a 1/2

RFC 9799: ACME Extensions for ".onion" Domain Names

Le protocole #ACME permet d'automatiser le processus de création et de renouvellement de #certificats utilisables, par exemple, pour TLS. L'extension normalisée dans ce nouveau #RFC permet d'obtenir des certificats pour un service utilisant le .onion de #Tor. Si vous voulez passer à la télévision en disant « j'ai obtenu un certificat pour le Dark Web », ce RFC est la bonne lecture.

https://www.bortzmeyer.org/9799.html

RFC 9799: Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names, Q Misell, Ed., https://www.rfc-editor.org/info/rfc9799#RFC This document defines extensions to the Automated Certificate Management Environment (ACME) to allow for the automatic issuance of certificates to Tor Hidden Services (".onion" Special-Use Domain Names). This document is a 1/2

RFC 9805: Deprecation of the IPv6 Router Alert Option for New Protocols, R. Bonica, https://www.rfc-editor.org/info/rfc9805#RFC This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option. This 1/2

Wrote up an #RFC to get feedback on adding #ActivityPub support to https://apply.coop soon after we launch. If anyone else has feedback it is certainly welcome! It does require a Codeberg account to comment, but we're open to email feedback as well.

I am not an ActivityPub expert so a lot of this was learning while planning this out.

https://codeberg.org/limeleaf/apply.coop/issues/213

#Coop #JobBoard #BuildInPublic