Congestion Exposure (ConEx) Concepts and Use Cases
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- Abstract
- This document provides the entry point to the set of documentation about the Congestion Exposure (ConEx) protocol. It explains the motivation for including a ConEx marking at the IP layer: to expose information about congestion to network nodes. Although such information may have a number of uses, this document focuses on how the information communicated by the ConEx marking can serve as the basis for significantly more efficient and effective traffic management than what exists on the Internet today. This document is not an Internet Standards Track specification; it is published for informational purposes.
- Publication Date
- 2012-12-01
- Status Note
- Informational
- DOI
10.17487/RFC6789- Link
- https://doi.org/10.17487/RFC6789
- Author(s)
- Bob BriscoeRichard WoundyAlissa Cooper
- Keyword(s)
- Congestion Signaling
Latest version of IETF RFC 6789
Document Versions — IETF RFC 6789
-
▶ IETF RFC 6789 (2012-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Briscoe, B., "Initial Congestion Exposure (ConEx) Deployment Examples", Work in Progress, July 2012. EXTERNAL
- Mathis, M. and B. Briscoe, "Congestion Exposure (ConEx) Concepts and Abstract Mechanism", Work in Progress, October 2012. EXTERNAL
- Briscoe, B. and M. Sridharan, "Network Performance Isolation in Data Centres using Congestion Exposure (ConEx)", Work in Progress, July 2012. EXTERNAL
- Krishnan, S., Kuehlewind, M., and C. Ucendo, "IPv6 Destination Option for ConEx", Work in Progress, September 2012. EXTERNAL
- Kuehlewind, M. and R. Scheffenegger, "More Accurate ECN Feedback in TCP", Work in Progress, July 2012. EXTERNAL
- Bauer, S., Clark, D., and W. Lehr, "The Evolution of Internet Congestion", 2009. EXTERNAL
- Shalunov, S., Hazel, G., Iyengar, J., and M. Kuehlewind, "Low Extra Delay Background Transport (LEDBAT)", Work in Progress, September 2012. EXTERNAL
- Briscoe, B., Jacquet, A., and T. Moncaster, "Policing Freedom to Use the Internet Resource Pool", ReArch 2008 hosted at the 2008 CoNEXT conference , December 2008. EXTERNAL
- Anschutz, T., Ed., "DSL Forum Technical Report TR-059: Requirements for the Support of QoS-Enabled IP Services", September 2003. EXTERNAL
- Kutscher, D., Mir, F., Winter, R., Krishnan, S., Zhang, Y., and C. Bernardos, "Mobile Communication Congestion Exposure Scenario", Work in Progress, July 2012. EXTERNAL
- Kuehlewind, M. and R. Scheffenegger, "TCP modifications for Congestion Exposure", Work in Progress, May 2012. EXTERNAL
- Cohen, A., Ed. and E. Schrum, Ed., "DSL Forum Technical Report TR-101: Migration to Ethernet-Based DSL Aggregation", April 2006. EXTERNAL
- IETF RFC 2475 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 6057 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6789.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 6789, Congestion Exposure (ConEx) Concepts and Use Cases. Available at https://doi.org/10.17487/RFC6789
Snippet:
IETF RFC 6789, Congestion Exposure (ConEx) Concepts and Use Cases. Available at https://doi.org/10.17487/RFC6789
HTML (ISO 690 compliant)
Preview:
IETF RFC 6789, Congestion Exposure (ConEx) Concepts and Use Cases. Available at https://doi.org/10.17487/RFC6789
Snippet:
<span class="citation"><cite>IETF RFC 6789</cite>, Congestion Exposure (ConEx) Concepts and Use Cases. Available at <a href="https://doi.org/10.17487/RFC6789" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6789</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6789, Congestion Exposure (ConEx) Concepts and Use Cases
doi: 10.17487/RFC6789
url: https://doi.org/10.17487/RFC6789
doi: 10.17487/RFC6789
url: https://doi.org/10.17487/RFC6789
Snippet:
<li> <cite id="bib-rfc6789">IETF RFC 6789</cite>, Congestion Exposure (ConEx) Concepts and Use Cases <span class="doi">10.17487/RFC6789</span> </li>
Referenced By
- IETF RFC 7141 [Active*]
- IETF RFC 7560 [Active*]
- IETF RFC 7567 [Active*]