RFC 2923: TCP Problems with Path MTU Discovery
In plain English — editorial summary, not part of the RFC
This memo catalogs several known Transmission Control Protocol (TCP) implementation problems dealing with Path Maximum Transmission Unit Discovery (PMTUD), including the long-standing black hole problem, stretch acknowlegements (ACKs) due to confusion between Maximum Segment Size (MSS) and segment size, and MSS advertisement based on PMTU. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2923
- Published
- September 2000
- Authors
- K. Lahey
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 3135Performance Enhancing Proxies Intended to Mitigate Link-Related DegradationsCurrent
June 2001
- RFC 3155End-to-end Performance Implications of Links with ErrorsCurrent
August 2001
- RFC 2582The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted
April 1999
- 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
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?