Ce #RFC normalise les #UUID, une famille d'identificateurs uniques, obtenus sans registre central. Il remplace l'ancienne norme, le RFC 4122, avec pas mal de nouveautés et un RFC complètement refait.
Although it was a long journey, I'm happy it is now ratified.
Thanks to everyone who spent time writing and reviewing it and provided valuable feedback!
There is still a lot of work ahead adapting and improving our tooling and I hope many will join in this effort.
Here is to #ArchLinux on many more architectures in the future 🥂
(meanwhile I have three more RFCs in the pipeline 😅)
@pollita I just read the #PHP#RFC called "RFC1867 for non-POST HTTP verbs". You were the only one voting "No" - I wonder why. Was that a "No, we don't need that" or did you have specific reason, maybe a technical one? https://wiki.php.net/rfc/rfc1867-non-post
RFC 9547: Report from the IAB Workshop on Environmental Impact of Internet Applications and Systems
La question de l'empreinte environnementale du numérique suscite beaucoup de débats. L'IAB avait organisé en 2022 un atelier sur le cas de l'empreinte environnementale de l'Internet dont ce #RFC est le compte-rendu.
"A relative reference that begins with a single slash character is termed an absolute-path reference. A relative reference that does not begin with a slash character is termed a relative-path reference."
Generating #DNSSEC signatures using the private keys from #RFC 9500 (a bunch a publicly known private keys, which is a strange concept 🤔) : it works nicely. :3 The keytag for "testECCP256" is 56715 or 56716 (whether it's a ZSK or a KSK).
RFC 9340: Architectural Principles for a Quantum Internet
Voici un #RFC assez futuriste qui explore à quoi pourrait ressembler un futur « Internet » #quantique. Je divulgâche tout de suite : ce ne sera pas de si tôt.
"The recent advances in artificial intelligence (#AI) such as large language models enable the design of the Faster than LIght speed Protocol (#FLIP) for Internet. FLIP provides a way to avoid congestion, enhance security, and deliver faster packets on the Internet by using AI to predict future packets at the receiving peer before they arrive. This document describes the protocol, its various encapsulations, and some operational considerations."
Is there any known implementation of #RFC 1149 not using columbidae (pigeons or doves)? Because the RFC does say avian carriers, meaning any bird could transport IP. That would bring passionate debates about the differences of MTU between African and European swallow 😬
“This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an #HTTP message”
Tomorrow we'll host a webinar on the GNU Name System (GNS) and the road to publishing an RFC.
Thursday Feb 22, 13.00 CET.
GNS provides a privacy-enhancing alternative to the Domain Name System. It was published as an #rfc. RFC authors Martin Schanzenbach & Bernd Fix will explain GNS and how the RFC process works.
Stephen Farrell advises on working with #standardisation bodies.
The #webinar is open to all. You can find the link to the BBB platform here: https://nlnet.nl/webinars/
Join the #webinar on the GNU Name System (GNS) and the road to publishing an RFC.
GNS is a decentralized and censorship-resistant domain name resolution protocol providing an alternative to DNS. In 2023 the GNS was published as RFC 9498. The authors of the #RFC Martin Schanzenbach & Bernd Fix will talk about GNS & the road to published an RFC.
Stephen Farrell of Tolerant Networks will talk about getting advice with #standardisation processes.
#TIL In #RFC 883 (the original not-yet-called-DNS), the serial in a SOA record was only 16-bits (unsigned).
The value already “wraps and should be compared using sequence space arithmetic” (this exact same wording is in RFC 1035. The arithmetic will be clearly defined in 1996 ^^ - RFC 1982)