Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 30
- Abstract
- 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.
- Publication Date
- 2015-12-01
- Status Note
- Informational
- DOI
10.17487/RFC7713- Link
- https://doi.org/10.17487/RFC7713
- Author(s)
- Matt MathisBob Briscoe
- Keyword(s)
- Quality Of Service, QoS, Congestion Control, Signaling, Encoding, Audit, Policing
Latest version of IETF RFC 7713
Document Versions — IETF RFC 7713
-
▶ IETF RFC 7713 (2015-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
Bibliographic Reference(s)
- 10.1016-S0005-1098_99_00135-1 — Evol_cc EXTERNAL
- 10.1109-MSPEC.2008.4687368 — FairerFaster EXTERNAL
- 10.1111-j.1430-9134.2001.00173.x — CheapPseud EXTERNAL
- 10.1145-1090191.1080124 — Re-fb EXTERNAL
- 10.1145-1851182.1851192 — DCTCP EXTERNAL
- IETF draft-briscoe-conex-policing-01 [Active*]
- IETF draft-briscoe-conex-re-ecn-motiv-03 [Active*]
- IETF draft-briscoe-conex-re-ecn-tcp-04 [Active*]
- IETF.draft-ietf-conex-destopt-11 — CONEX-DESTOPT EXTERNAL
- IETF.draft-ietf-conex-tcp-modifications-10 — TCP-MODIFICATION EXTERNAL
- IETF.draft-wagner-conex-audit-01 — CONEX-AUDIT EXTERNAL
- Briscoe, B., "Re-feedback: Freedom with Accountability for Causing Congestion in a Connectionless Internetwork", PhD Dissertation, University College London, May 2009, < http://discovery.ucl.ac.uk/16274/ >. EXTERNAL
- Salvatori, A., "Closed Loop Traffic Policing", Politecnico Torino and Institut Eurecom Masters Thesis, September 2005. EXTERNAL
- IETF RFC 2018 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 3514 [Active*]
- IETF RFC 3550 [Active*]
- IETF RFC 5348 [Active*]
- IETF RFC 5681 [Active*]
- IETF RFC 6040 [Active*]
- IETF RFC 6679 [Active*]
- IETF RFC 6789 [Active*]
- IETF RFC 6817 [Active*]
- IETF RFC 7141 [Active*]
- IETF RFC 7560 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7713.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7713, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements. Available at https://doi.org/10.17487/RFC7713
Snippet:
IETF RFC 7713, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements. Available at https://doi.org/10.17487/RFC7713
HTML (ISO 690 compliant)
Preview:
IETF RFC 7713, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements. Available at https://doi.org/10.17487/RFC7713
Snippet:
<span class="citation"><cite>IETF RFC 7713</cite>, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements. Available at <a href="https://doi.org/10.17487/RFC7713" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7713</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7713, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
doi: 10.17487/RFC7713
url: https://doi.org/10.17487/RFC7713
doi: 10.17487/RFC7713
url: https://doi.org/10.17487/RFC7713
Snippet:
<li> <cite id="bib-rfc7713">IETF RFC 7713</cite>, Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements <span class="doi">10.17487/RFC7713</span> </li>
Referenced By
- IETF RFC 8083 [Active*]
- IETF RFC 9330 [Active*]
- IETF RFC 9331 [Active*]
- IETF RFC 9599 [Active*]
- IETF RFC 9768 [Active*]