RFC 879: The TCP Maximum Segment Size and Related Topics
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7805, RFC 9293.
Current document in this lineage: RFC 7805 — Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status; RFC 9293 — Transmission Control Protocol (TCP)
In plain English — editorial summary, not part of the RFC
This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers".
Document record
- Document ID
- RFC879
- Published
- November 1983
- Authors
- J. Postel
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
- Updated by:
- RFC 6691
Standards lineage
This document is one revision in a chain of 18 RFCs, each formally replacing the one before it.
- RFC 675 (1974)
- RFC 721 (1976)
- RFC 761 (1980)
- RFC 793 (1981)
- RFC 813 (1982)
- RFC 816 (1982)
- RFC 879 (1983)
- RFC 896 (1984)
- RFC 1078 (1988)
- RFC 1948 (1996)
- RFC 2873 (2000)
- RFC 6013 (2011)
- RFC 6093 (2011)
- RFC 6429 (2011)
- RFC 6528 (2012)
- RFC 6691 (2012)
- RFC 7805 (2016)
- RFC 9293 (2022) ✓
Read the full history of Transmission Control Protocol (TCP) →
Referenced by
3 later RFCs formally update or obsolete part of this document.
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?