[tsvwg] BCP 89, RFC 9599 on Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP

A new Request for Comments is now available in online RFC libraries.

        BCP 89        
        RFC 9599

        Title:      Guidelines for Adding Congestion Notification 
                    to Protocols that Encapsulate IP 
        Author:     B. Briscoe,
                    J. Kaippallimalil
        Status:     Best Current Practice
        Stream:     IETF
        Date:       August 2024
        Mailbox:    ietf@bobbriscoe.net,
                    kjohn@futurewei.com
        Pages:      28
        Updates:    RFC 3819
        See Also:   BCP 89

        I-D Tag:    draft-ietf-tsvwg-ecn-encap-guidelines-22.txt

        URL:        https://www.rfc-editor.org/info/rfc9599

        DOI:        10.17487/RFC9599

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.

This document is a product of the Transport and Services Working Group Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC