Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
RFC 9599
part of BCP 89
Revision differences
Document history
Date | By | Action |
---|---|---|
2024-08-30
|
(System) | Received changes through RFC Editor sync (created document RFC 9599, created became rfc relationship between draft-ietf-tsvwg-ecn-encap-guidelines and RFC 9599, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9599, created became rfc relationship between draft-ietf-tsvwg-ecn-encap-guidelines and RFC 9599, set abstract to '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.', set pages to 28, set standardization level to Best Current Practice, added RFC published event at 2024-08-30, created updates relation between RFC 9599 and RFC 3819) |
2024-08-30
|
(System) | Added rfc9599 to bcp89 |
2024-08-30
|
(System) | RFC published |