#rfc — Public Fediverse posts

@bortzmeyer Au niveau RFC 6014, le statut actuel n'est pas suffisant ? @shaft #RFC #RFC6014 #DNS #DNSSEC #PQC

RFC 10024: Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3

On met du post-quantique partout en ce moment. Ce court #RFC normalise l'utilisation de clés hybrides (post-quantiques et traditionnelles) dans les échanges de clés de #TLS.

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

#RFC 3901 is now obsoleted

“This document provides guidelines and documents best current practice for operating authoritative #DNS servers, recursive resolvers, and stub resolvers in a mixed #IPv4 / #IPv6 environment."

RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments
https://www.rfc-editor.org/info/rfc10001/

#RFC 10030: NOP.

(That's NTP Over PTP obviously)

https://www.rfc-editor.org/info/rfc10030/

https://blog.gslin.org/archives/2026/08/13/13146/%e8%b3%a3-domain-%e7%9a%84-rfc-10023-_for-sale/

賣 domain 的 RFC 10023 (_for-sale)

#dns #domain #for #name #rfc #sale #standard

@ataudte

@tfiebig @ietf
Thank you to the authors and v6ops

Time to poke @ZDF
You are not reachable on the current Internet.

#BCP #RFC #RFC10001 #BCP91 #DNS #IPv4 #IPv6

@ataudte

#fediadmin please open a support case if you are using #Fastly as a CDN or such.
They are not providing autorative Nameservers via #IPv6

#BCP #RFC #RFC10001 #BCP91 #DNS #IPv4 #IPv6

#Development #Guides
_for-sale DNS records · A domain can now advertise it is for sale https://ilo.im/16f6a8

_____
#Business #Marketing #Advertising #Domains #DNS #TxtRecord #RFC #WebDev #Frontend #Backend

TIL about RFC3271 (The Internet is for Everyone) which is not an April's Fool RFC despite being published on 2002-04-01.

The Internet is proving to be one of the most powerful amplifiers of speech ever invented. It offers a global megaphone for voices that might otherwise be heard only feebly, if at all. It invites and facilitates multiple points of view and dialog in ways unimplementable by the traditional, one-way, mass media.

~25 years later, I wish that Internet wasn't for everyone.

#rfc #vintcerf

My take on #RFC 10023 (the "_for-sale" domain thingy)

https://piaille.fr/@shaft/117042177464473926

One more straw on the #DNS camel, but a possibly nice straw if deployed in software

"This document specifies a method for a DNS client to request additional DNS record types to be delivered alongside the primary record type specified in the Question section of a DNS QUERY (OpCode=0)."

"For example, it may be desirable to receive the A, AAAA, and HTTPS RRs for a domain name together, rather than having to issue multiple queries."

#RFC 10029: DNS Multiple QTYPEs
https://www.rfc-editor.org/info/rfc10029/

@isAutonomous @karlsruhedigital Richtig. Mir ist nicht bekannt, dass sich jemand aus Karlsruhe an den relevanten RFCs, allen voran 822, beteiligt hätte.
RFC 822:
https://datatracker.ietf.org/doc/html/rfc822

#RFC #EMail

RFC 10015: Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2

https://www.rfc-editor.org/rfc/rfc10015.html

#RFC #TLS #Cryptography #Encryption

🎉 Oh joy, yet another RFC! In the thrilling world of Internet engineering, someone finally realized that using obsolete key exchange methods is as effective as a chocolate teapot. 🚀 Welcome to 2026, where we've officially decided not to use security techniques that even your grandma could outsmart! 🍵🔑
https://www.rfc-editor.org/rfc/rfc10015.html #RFC #InternetSecurity #ObsoleteMethods #KeyExchange #TechInnovation #Cybersecurity #HackerNews #ngated

@bortzmeyer : De toute façon, les #RFC, c'est devenu une fête commerciale.