RFC 7786: TCP Modifications for Congestion Exposure (ConEx)
In plain English — editorial summary, not part of the RFC
Congestion Exposure (ConEx) is a mechanism by which senders inform the network about expected congestion based on congestion feedback from previous packets in the same flow. This document describes the necessary modifications to use ConEx with the Transmission Control Protocol (TCP).
Document record
- Document ID
- RFC7786
- Published
- May 2016
- Authors
- M. Kuehlewind; R. Scheffenegger
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7778Mobile Communication Congestion Exposure ScenarioCurrent
March 2016
- RFC 7806On Queuing, Marking, and DroppingCurrent
April 2016
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 7846Peer-to-Peer Streaming Tracker Protocol (PPSTP)Current
May 2016
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
- RFC 7928Characterization Guidelines for Active Queue Management (AQM)Current
July 2016
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 7982Measurement of Round-Trip Time and Fractional Loss Using Session Traversal Utilities for NAT (STUN)Current
September 2016
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?