RFC 5681: TCP Congestion Control
In plain English — editorial summary, not part of the RFC
This document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. This document obsoletes RFC 2581. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5681
- Published
- September 2009
- Authors
- M. Allman; V. Paxson; E. Blanton
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 18
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2001 (1997)
- RFC 2581 (1999)
- RFC 5681 (2009)
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6582The NewReno Modification to TCP's Fast Recovery AlgorithmCurrent
April 2012
- RFC 9937Proportional Rate Reduction (PRR)Current
December 2025
- RFC 9177Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust TransmissionCurrent
March 2022
- 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 9362Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block TransmissionCurrent
February 2023
- RFC 5682Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCPCurrent
September 2009
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?