RFC 2525: Known TCP Implementation Problems
In plain English — editorial summary, not part of the RFC
This memo catalogs a number of known TCP implementation problems. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2525
- Published
- March 1999
- Authors
- V. Paxson; M. Allman; S. Dawson; W. Fenner; J. Griner; I. Heavens; K. Lahey; J. Semke; B. Volz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 61
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2488Enhancing TCP Over Satellite Channels using Standard MechanismsCurrent
January 1999
- RFC 2582The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted
April 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 2398Some Testing Tools for TCP ImplementorsCurrent
August 1998
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- 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?