RFC 2582: The NewReno Modification to TCP's Fast Recovery Algorithm
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3782.
Current document in this lineage: RFC 6582 — The NewReno Modification to TCP's Fast Recovery Algorithm
In plain English — editorial summary, not part of the RFC
This document describes a specific algorithm for responding to partial acknowledgments, referred to as NewReno. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2582
- Published
- April 1999
- Authors
- S. Floyd; T. Henderson
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 3782
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2582 (1999)
- RFC 3782 (2004)
- RFC 6582 (2012) ✓
Read the full history of The NewReno Modification to TCP's Fast Recovery Algorithm →
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 2525Known TCP Implementation ProblemsCurrent
March 1999
- RFC 2488Enhancing TCP Over Satellite Channels using Standard MechanismsCurrent
January 1999
- RFC 2416When TCP Starts Up With Four Packets Into Only Three BuffersCurrent
September 1998
- RFC 2415Simulation Studies of Increased Initial TCP Window SizeCurrent
September 1998
- RFC 2414Increasing TCP's Initial WindowObsoleted
September 1998
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 2398Some Testing Tools for TCP ImplementorsCurrent
August 1998
- RFC 2923TCP Problems with Path MTU DiscoveryCurrent
September 2000
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?