RFC 7713: Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements

This document describes an abstract mechanism by which senders inform the network about the congestion recently encountered by packets in the same flow.…

Read RFC 7713 on the RFC Editor

Outgoing relationships (3 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 5681: TCP Congestion Control
Informative reference — RFC 2018: TCP Selective Acknowledgment Options

Incoming relationships (10 related RFCs)

Normatively referenced by — RFC 7786: TCP Modifications for Congestion Exposure (ConEx)
Normatively referenced by — RFC 7837: IPv6 Destination Option for Congestion Exposure (ConEx)
Informatively referenced by — RFC 8083: Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
Informatively referenced by — RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Informatively referenced by — RFC 9957: The DOCSIS Queue Protection Algorithm to Preserve Low Latency
Informatively referenced by — RFC 7778: Mobile Communication Congestion Exposure Scenario
Informatively referenced by — RFC 9506: Explicit Host-to-Network Flow Measurements Techniques
Informatively referenced by — RFC 9768: More Accurate Explicit Congestion Notification (AccECN) Feedback in TCP