RFC 2581: TCP Congestion Control
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5681.
Current document in this lineage: 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2581
- Published
- April 1999
- Authors
- M. Allman; V. Paxson; W. Stevens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- 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
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
- RFC 6675A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCPCurrent
August 2012
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4413TCP/IP Field BehaviorCurrent
March 2006
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?