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
Ahhhh this year we have a new RFC!
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
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 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
@RadioAzureus #rfc request to comment
