RFC 7713: Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
In plain English — editorial summary, not part of the RFC
This document describes an abstract mechanism by which senders inform the network about the congestion recently encountered by packets in the same flow. Today, network elements at any layer may signal congestion to the receiver by dropping packets or by Explicit Congestion Notification (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, "Congestion Exposure (ConEx) Concepts and Use Cases" (RFC 6789), provides the entry point to the set of ConEx documentation.
Document record
- Document ID
- RFC7713
- Published
- December 2015
- Authors
- M. Mathis; B. Briscoe
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 5696Baseline Encoding and Transport of Pre-Congestion InformationObsoleted
November 2009
- RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent
June 2009
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?