Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

BEST CURRENT PRACTICE

Updates:

RFC 3819

Authors:

B. Briscoe
J. Kaippallimalil

Stream:

IETF

Source:

tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9599

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9599

Abstract

The purpose of this document is to guide the design of congestionnotification in any lower-layer or tunnelling protocol thatencapsulates IP. The aim is for explicit congestion signals topropagate consistently from lower-layer protocols into IP. Then, theIP internetwork layer can act as a portability layer to carrycongestion notification from non-IP-aware congested nodes up to thetransport layer (L4). Specifications that follow these guidelines,whether produced by the IETF or other standards bodies, shouldassure interworking among IP-layer and lower-layer congestionnotification mechanisms. This document is included in BCP 89 andupdates the single paragraph of advice to subnetwork designers aboutExplicit Congestion Notification (ECN) in Section 13 of RFC 3819 byreplacing it with a reference to this document.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.