RFC 7786: TCP Modifications for Congestion Exposure (ConEx)

Congestion Exposure (ConEx) is a mechanism by which senders inform the network about expected congestion based on congestion feedback from previous packets in…

Read RFC 7786 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Normative reference — RFC 5681: TCP Congestion Control
Normative reference — RFC 2018: TCP Selective Acknowledgment Options
Normative reference — RFC 7713: Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
Normative reference — RFC 7837: IPv6 Destination Option for Congestion Exposure (ConEx)
Informative reference — RFC 3522: The Eifel Detection Algorithm for TCP
Informative reference — RFC 6582: The NewReno Modification to TCP's Fast Recovery Algorithm
Informative reference — RFC 3708: Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
Informative reference — RFC 4015: The Eifel Response Algorithm for TCP
Informative reference — RFC 6789: Congestion Exposure (ConEx) Concepts and Use Cases
Informative reference — RFC 7141: Byte and Packet Congestion Notification
Informative reference — RFC 5682: Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 7837: IPv6 Destination Option for Congestion Exposure (ConEx)
Informatively referenced by — RFC 9506: Explicit Host-to-Network Flow Measurements Techniques