Just wanted to share some thoughts on #RFC9715 - an #RFC that defines standards on reducing the #DNS issue of IP fragmentation over #UDP. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the #Internet. A great leap forward to (hopefully) reduce the reflection/amplification #DDoS potential of DNS.

Just today I learned that #Google will share their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to #TCP.

Note 3581961 - [CVE-2025-27429] Code Injection Vulnerability in #SAP S/4HANA (Private Cloud)
#abap #rfc

RFC 9752: Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE, C. Li, et al., https://www.rfc-editor.org/info/rfc9752 #RFC This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) that enable the inclusion of vendor-specific information in stateful Path Computation Element (PCE) 1/3

RFC 9764: Bidirectional Forwarding Detection (BFD) Encapsulated in Large Packets, J. Haas, et al., https://www.rfc-editor.org/info/rfc9764 #RFC The Bidirectional Forwarding Detection (BFD) protocol is commonly used to verify connectivity between two systems. BFD packets are typically very small. It is desirable in some circumstances to know not only that the path between two systems is 1/3

RFC 9719: YANG Data Model for Routing in Fat Trees (RIFT), Z. Zhang, et al., https://www.rfc-editor.org/info/rfc9719 #RFC This document defines a YANG data model for the configuration and management of the Routing in Fat Trees (RIFT) Protocol. The model is based on YANG 1.1, which is defined in RFC 7950 and conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 1/2

RFC 9696: Routing in Fat Trees (RIFT) Applicability and Operational Considerations, Y. Wei, Ed., et al., https://www.rfc-editor.org/info/rfc9696 #RFC This document discusses the properties, applicability, and operational considerations of Routing in Fat Trees (RIFT) in different network scenarios with the intention of providing a rough guide on how RIFT can be deployed to simplify routing 1/2

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! This year, time management!

https://www.rfc-editor.org/rfc/rfc9759.txt

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.

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

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 9778: IANA Considerations for Internet Group Management Protocols, B. Haberman, Ed., https://www.rfc-editor.org/info/rfc9778 #RFC This document specifies revised IANA considerations for the Internet Group Management Protocol (IGMP) and the Multicast Listener Discovery (MLD) protocol. This document specifies the guidance provided to IANA to manage values associated with various fields 1/2

RFC 9777: Multicast Listener Discovery Version 2 (MLDv2) for IPv6, B. Haberman, Ed., https://www.rfc-editor.org/info/rfc9777 #RFC This document specifies the Multicast Listener Discovery version 2 (MLDv2) protocol. MLD is used by an IPv6 router to discover the presence of multicast listeners on directly attached links and to discover which multicast addresses are of interest to those 1/3

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 9628: RTP Payload Format for VP9 Video, J. Uberti, et al., https://www.rfc-editor.org/info/rfc9628 #RFC This specification describes an RTP payload format for the VP9 video codec. The payload format has wide applicability as it supports applications from low bitrate peer-to-peer usage to high bitrate video conferences. It includes provisions for temporal and spatial scalability. This 1/2

RFC 9627: The Layer Refresh Request (LRR) RTCP Feedback Message, J. Lennox, et al., https://www.rfc-editor.org/info/rfc9627 #RFC This memo describes the RTCP Payload-Specific Feedback Message Layer Refresh Request (LRR), which can be used to request a state refresh of one or more substreams of a layered media stream. This document also defines its use with several RTP payloads for scalable 1/2

RFC 9626: Video Frame Marking RTP Header Extension, M. Zanaty, et al., https://www.rfc-editor.org/info/rfc9626 #RFC This document describes a Video Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted and essential when the 1/2

RFC 9732: A Framework for NRP-Based Enhanced Virtual Private Networks, J. Dong, et al., https://www.rfc-editor.org/info/rfc9732 #RFC This document describes a framework for Enhanced Virtual Private Networks (VPNs) based on Network Resource Partitions (NRPs) in order to support the needs of applications with specific traffic performance requirements (e.g., low latency, bounded jitter). 1/3