RFC 9692: RIFT: Routing in Fat Trees, T. Przygienda, Ed., et al., https://www.rfc-editor.org/info/rfc9692 #RFC This document defines a specialized, dynamic routing protocol for Clos, fat tree, and variants thereof. These topologies were initially used within crossbar interconnects and consequently router and switch backplanes, but their characteristics make them ideal for constructing IP 1/2
@ffhl @videolan die technische Hintergrund der neuen Streams:
Statt #IPv6 / UDP / #RTP / #Opus. Ist es jetzt: IPv6 / UDP / #MPEG2TS / RTP / Opus.
Es ist also noch ein gaaanz toller (Sarkasmus), proprietärer, unnötiger Protokollheader dazwischen gekommen, der nur das Paket aufbläht. VLC v3 kann aber noch nicht das #IETF #RFC standardisierte, native RTP-Opus, das kann erst der nightly/v4.
Sobald VLC endlich mal releasen sollte, schmeiß ich das MPEG-TS auch ganz schnell wieder weg.
Ahh, here it is. Maybe the IETF should publish a list or something including the publication date, so they can be found more easily.
RFC 9759, Unified Time Scaling for Temporal Coordination Frameworks
RFC 9759: Unified Time Scaling for Temporal Coordination Frameworks, K. Kuhns, https://www.rfc-editor.org/info/rfc9759 #RFC Estimating time requirements for tasks, both critical and mundane, remains a challenge in engineering, business, and everyday communication. Existing models fail due to inherent unpredictability and inconsistencies in human estimation. This document introduces the 1/2
Was really looking forward to an April 1 IETF RFC this year - but it appears i will be disappointed this year.
Instead - I guess I'll have to share some of my favorites from years past
RFC 3514 "The Security Flag in the IPv4 Header"
https://datatracker.ietf.org/doc/html/rfc3514
RFC 1149 "A Standard for the Transmission of IP Datagrams on Avian Carriers"
RFC 9726: Operational Considerations for Use of DNS in IoT Devices
Les objets connectés sont une source de risques de sécurité. Pour les limiter, le RFC 8250 normalisait le format #MUD, pour que le fournisseur du machin connecté documente les accès au réseau de l'objet. Dans un fichier MUD, les services avec lesquels l'objet communique sont indiqués par un nom de domaine. Le #DNS a quelques subtilités, décrites dans ce #RFC.
RFC 9726: Operational Considerations for Use of DNS in Internet of Things (IoT) Devices, M. Richardson, et al., https://www.rfc-editor.org/info/rfc9726 #RFC This document details considerations about how Internet of Things (IoT) devices use IP addresses and DNS names. These concerns become acute as network operators begin deploying Manufacturer Usage Descriptions (MUD), as specified in RFC 1/2
RFC 9776: Internet Group Management Protocol, Version 3, B. Haberman, Ed., https://www.rfc-editor.org/info/rfc9776 #RFC The Internet Group Management Protocol (IGMP) is the protocol used by IPv4 systems to report their IP multicast group memberships to neighboring multicast routers. Version 3 of IGMP (IGMPv3) adds support for source filtering, that is, the ability for a system to report 1/3
RFC 9754: Extensions for Opening and Delegating Files in NFSv4.2, T. Haynes, et al., https://www.rfc-editor.org/info/rfc9754 #RFC The Network File System v4 (NFSv4) allows a client to both open a file and be granted a delegation of that file. This delegation provides the client the right to authoritatively cache metadata on the file locally. This document presents several extensions for 1/2
RFC 9725: WebRTC-HTTP Ingestion Protocol (WHIP), S. Garcia Murillo, et al., https://www.rfc-editor.org/info/rfc9725 #RFC This document describes a simple HTTP-based protocol that will allow WebRTC-based ingestion of content into streaming services and/or Content Delivery Networks (CDNs). This document updates RFCs 8840 and 8842. This document is a product of the WebRTC Ingest Signaling over 1/2
RFC 9724: Randomized and Changing MAC Address State of Affairs
Dans le contexte de la surveillance massive qui s'exerce contre les utilisateurices de l'Internet, tout identifiant un peu stable peut être utilisé pour pister quelqu'un. On en laisse, des traces ! C'est par exemple le cas avec l'#adresseMAC. Ce nouveau #RFC décrit les mécanismes existants pour diminuer le risque de pistage par l'adresse MAC. Il ne spécifie pas un protocole, il liste les solutions.
My first #PHP #RFC with a lot richer discussion passed today :)
https://wiki.php.net/rfc/marking_return_value_as_important
48 Mails all in all: https://externals.io/message/126232 with some additional feedback on social media.
Thanks to everyone :)
What to do next now 
RFC 9694: Guidelines for the Definition of New Top-Level Media Types
Vous savez que les types de médias comportent un type de premier niveau et un sous-type. Dans image/gif, image est le type de premier niveau et gif le sous-type. La création du type haptics (données haptiques), qui a été faite dans le #RFC 9695, a été l'occasion de formaliser un peu plus le processus de création de types de médias.
RFC 9695: The 'haptics' Top-level Media Type
L'enregistrement d'un nouveau type de média de premier niveau est plutôt rare (le dernier avait été font/ en 2017). Notre #RFC introduit le type haptics/, pour les formats de fichier des interfaces haptiques, celles qu'on touche et qui vous touchent (une manette de jeu vidéo à retour d'effort, par exemple).
RFC 9775: IRTF Code of Conduct, C. S. Perkins, https://www.rfc-editor.org/info/rfc9775 #RFC This document describes the code of conduct for participants in the Internet Research Task Force (IRTF). The IRTF believes that research is most effective when done in an open and inclusive forum that encourages diversity of ideas and participation. Through this code of conduct, the IRTF continues to 1/2
RFC 9695: The 'haptics' Top-Level Media Type, Y. K. Muthusamy, et al., https://www.rfc-editor.org/info/rfc9695 #RFC This memo registers and documents the 'haptics' top-level media type, under which subtypes for representation formats for haptics may be registered. This document also serves as a registration for a set of subtypes, which are representative of some existing subtypes already in 1/2
RFC 9694: Guidelines for the Definition of New Top-Level Media Types, M.J. Dürst, https://www.rfc-editor.org/info/rfc9694 #RFC This document defines best practices for defining new top-level media types. It also introduces a registry for top-level media types, and contains a short history of top-level media types. It updates RFC 6838. This document is a product of the Media Type Maintenance 1/2
RFC 9724: State of Affairs for Randomized and Changing Media Access Control (MAC) Addresses, JC. Zúñiga, et al., https://www.rfc-editor.org/info/rfc9724 #RFC Internet users are becoming more aware that their activity over the Internet leaves a vast digital footprint, that communications might not always be properly secured, and that their location and actions can be tracked. One of the main 1/3
RFC 9743: Specifying New Congestion Control Algorithms
La lutte contre la #congestion du réseau est une tâche permanente dans l'Internet. Si les émetteurs de données envoyaient des octets aussi vite qu'ils le pouvaient, l'Internet s'écroulerait vite. Les protocoles contiennent donc des algorithmes de contrôle de la congestion. Il y en a plusieurs et ce #RFC explique comment de nouveaux algorithmes doivent être évalués avant d'être déployés en vrai.
