RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9599
- Published
- August 2024
- Authors
- B. Briscoe; J. Kaippallimalil
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 28
- Also known as
- BCP89
- Updates:
- RFC 3819
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
- RFC 9601Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a ShimCurrent
August 2024
- RFC 9768More Accurate Explicit Congestion Notification (AccECN) Feedback in TCPCurrent
April 2026
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 2983Differentiated Services and TunnelsCurrent
October 2000
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?