Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, conex mailing list <email@example.com>, conex chair <firstname.lastname@example.org> Subject: Document Action: 'Congestion Exposure (ConEx) Concepts, Abstract Mechanism and Requirements' to Informational RFC (draft-ietf-conex-abstract-mech-13.txt) The IESG has approved the following document: - 'Congestion Exposure (ConEx) Concepts, Abstract Mechanism and Requirements' (draft-ietf-conex-abstract-mech-13.txt) as Informational RFC This document is the product of the Congestion Exposure Working Group. The IESG contact persons are Spencer Dawkins and Martin Stiemerling. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/
Technical Summary This document describes an abstract mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. Today, network elements at any layer may signal congestion to the receiver by dropping packets or by ECN markings, and the receiver passes this information back to the sender in transport-layer feedback. The mechanism described here enables the sender to also relay this congestion information back into the network in-band at the IP layer, such that the total amount of congestion from all elements on the path is revealed to all IP elements along the path, where it could, for example, be used to provide input to traffic management. This mechanism is called congestion exposure or ConEx. The companion document "ConEx Concepts and Use Cases" provides the entry-point to the set of ConEx documentation. Working Group Summary There were no special issues worth noting during the WG process. Document Quality The document received several thorough reviews. It is worth noting the reviews from Mirja Kuehlewind and David Wagner. Personnel Marcelo Bagnulo (email@example.com) is the document shepherd. Martin Stiemerling (firstname.lastname@example.org) is the responsible Area Director.