RFC 5562: Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets

The proposal in this document is Experimental. While it may be deployed in the current Internet, it does not represent a consensus that this is the best…

Read RFC 5562 on the RFC Editor

Outgoing relationships (10 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 793: Transmission Control Protocol
Informative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Informative reference — RFC 2988: Computing TCP's Retransmission Timer
Informative reference — RFC 2309: Recommendations on Queue Management and Congestion Avoidance in the Internet
Informative reference — RFC 2581: TCP Congestion Control
Informative reference — RFC 3042: Enhancing TCP's Loss Recovery Using Limited Transmit
Informative reference — RFC 4987: TCP SYN Flooding Attacks and Common Mitigations
Informative reference — RFC 3390: Increasing TCP's Initial Window
Informative reference — RFC 3360: Inappropriate TCP Resets Considered Harmful

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Normatively referenced by — RFC 8257: Data Center TCP (DCTCP): TCP Congestion Control for Data Centers
Informatively referenced by — RFC 8087: The Benefits of Using Explicit Congestion Notification (ECN)
Informatively referenced by — RFC 7141: Byte and Packet Congestion Notification
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 9768: More Accurate Explicit Congestion Notification (AccECN) Feedback in TCP