RFC 2001: TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2581.
Current document in this lineage: RFC 5681 — TCP Congestion Control
In plain English — editorial summary, not part of the RFC
Modern implementations of TCP contain four intertwined algorithms that have never been fully documented as Internet standards: slow start, congestion avoidance, fast retransmit, and fast recovery. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2001
- Published
- January 1997
- Authors
- W. Stevens
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 2581
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 2126ISO Transport Service on top of TCP (ITOT)Current
March 1997
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
October 1995
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 1792TCP/IPX Connection Mib SpecificationCurrent
April 1995
- RFC 2229A Dictionary Server ProtocolCurrent
October 1997
- RFC 1693An Extension to TCP : Partial Order ServiceObsoleted
November 1994
- RFC 1644T/TCP -- TCP Extensions for Transactions Functional SpecificationObsoleted
July 1994
- RFC 1613cisco Systems X.25 over TCP (XOT)Current
May 1994
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?