RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
In plain English — editorial summary, not part of the RFC
This memo specifies the incorporation of ECN (Explicit Congestion Notification) to TCP and IP, including ECN's use of two bits in the IP header. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3168
- Published
- September 2001
- Authors
- K. Ramakrishnan; S. Floyd; D. Black
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 63
- Also known as
- —
- Obsoletes:
- RFC 2481
Topics
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
- RFC 8311Relaxing Restrictions on Explicit Congestion Notification (ECN) ExperimentationCurrent
January 2018
- RFC 9768More Accurate Explicit Congestion Notification (AccECN) Feedback in TCPCurrent
April 2026
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3540Robust Explicit Congestion Notification (ECN) Signaling with NoncesCurrent
June 2003
- RFC 2638A Two-bit Differentiated Services Architecture for the InternetCurrent
July 1999
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3077A Link-Layer Tunneling Mechanism for Unidirectional LinksCurrent
March 2001
- RFC 3033The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet ProtocolCurrent
January 2001
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?