Last Call: <draft-ietf-tsvwg-ecn-encap-guidelines-20.txt> (Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 19 October 2023 21:11 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-tsvwg-ecn-encap-guidelines-20.txt> (Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
CC: David Black <david.black@dell.com>, draft-ietf-tsvwg-ecn-encap-guidelines@ietf.org, gorry@erg.abdn.ac.uk, martin.h.duke@gmail.com, tsvwg-chairs@ietf.org, tsvwg@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169774989370.26427.9835887461351407172@ietfa.amsl.com>
Date: Thu, 19 Oct 2023 14:11:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UsMcSyOoTGiM-Vw1fbPl94q0dVQ>

The IESG has received a request from the Transport and Services Working Group
WG (tsvwg) to consider the following document: - 'Guidelines for Adding
Congestion Notification to Protocols that
Encapsulate IP'
<draft-ietf-tsvwg-ecn-encap-guidelines-20.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-11-02. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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). Following these guidelines should assure
interworking among IP layer and lower layer congestion notification
mechanisms, whether specified by the IETF or other standards bodies.
This document is included in BCP 89 and updates the advice to
subnetwork designers about ECN in RFC 3819.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
rfc5129: Explicit Congestion Marking in MPLS (Proposed Standard - Internet Engineering Task Force (IETF))
rfc6040: Tunnelling of Explicit Congestion Notification (Proposed Standard - Internet Engineering Task Force (IETF))
draft-ietf-trill-ecn-support: TRILL (TRansparent Interconnection of Lots of Links): ECN (Explicit Congestion Notification) Support (None - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-tsvwg-ecn-encap-guidelines… The IESG