RFC 8311: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation

This memo updates RFC 3168, which specifies Explicit Congestion Notification (ECN) as an alternative to packet drops for indicating network congestion to…

Read RFC 8311 on the RFC Editor

Outgoing relationships (12 related RFCs)

Updates — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Updates, Normative reference — RFC 6679: Explicit Congestion Notification (ECN) for RTP over UDP
Updates, Normative reference — RFC 4342: Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)
Updates, Normative reference — RFC 4341: Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control
Updates, Normative reference — RFC 5622: Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2914: Congestion Control Principles
Informative reference — RFC 6040: Tunnelling of Explicit Congestion Notification
Informative reference — RFC 5706: Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions
Informative reference — RFC 4844: The RFC Series and RFC Editor
Informative reference — RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Informative reference — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)

Incoming relationships (10 related RFCs)

Normatively referenced by — RFC 9332: Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)
Normatively referenced by — RFC 9600: TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support
Normatively referenced by — RFC 9957: The DOCSIS Queue Protection Algorithm to Preserve Low Latency
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 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Informatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Informatively referenced by — RFC 9565: An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element
Informatively referenced by — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
Informatively referenced by — RFC 9768: More Accurate Explicit Congestion Notification (AccECN) Feedback in TCP