RFC 6789: Congestion Exposure (ConEx) Concepts and Use Cases
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6789
- Published
- December 2012
- Authors
- B. Briscoe; R. Woundy; A. Cooper
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 6801Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in the Forward Error Correction (FEC) FrameworkCurrent
November 2012
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 6816Simple Low-Density Parity Check (LDPC) Staircase Forward Error Correction (FEC) Scheme for FECFRAMECurrent
December 2012
- RFC 6817Low Extra Delay Background Transport (LEDBAT)Current
December 2012
- RFC 6824TCP Extensions for Multipath Operation with Multiple AddressesObsoleted
January 2013
- RFC 6726FLUTE - File Delivery over Unidirectional TransportCurrent
November 2012
- RFC 6865Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAMECurrent
February 2013
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?