Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
RFC 9599, “Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP”, is a Best Current Practice document published in August 2024 by B. Briscoe, J. Kaippallimalil. It updates RFC 3819. The canonical text is published by the RFC Editor.
Abstract
The purpose of this document is to guide the design of congestion notification in any lower-layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to propagate consistently from lower-layer protocols into IP. Then, the IP internetwork layer can act as a portability layer to carry congestion notification from non-IP-aware congested nodes up to the transport layer (L4). Specifications that follow these guidelines, whether produced by the IETF or other standards bodies, should assure interworking among IP-layer and lower-layer congestion notification mechanisms. This document is included in BCP 89 and updates the single paragraph of advice to subnetwork designers about Explicit Congestion Notification (ECN) in Section 13 of RFC 3819 by replacing it with a reference to this document.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 9599 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9598 Internationalized Email Addresses in X.509 Certificates
- RFC 9600 TRansparent Interconnection of Lots of Links : Explicit Congestion Notification Support
- RFC 9597 CBOR Web Token Claims in COSE Headers
- RFC 9601 Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
- RFC 9596 CBOR Object Signing and Encryption "typ" Header Parameter
- RFC 9602 Segment Routing over IPv6 Segment Identifiers in the IPv6 Addressing Architecture
- RFC 9595 YANG Schema Item iDentifier
- RFC 9603 Path Computation Element Communication Protocol Extensions for IPv6 Segment Routing