RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status
In plain English — editorial summary, not part of the RFC
This document reclassifies several TCP extensions that have never seen widespread use to Historic status. The affected RFCs are RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6247
- Published
- May 2011
- Authors
- L. Eggert
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 4614
Standards lineage
This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.
- RFC 1072 (1988)
- RFC 1106 (1989)
- RFC 1110 (1989)
- RFC 1145 (1990)
- RFC 1146 (1990)
- RFC 1185 (1990)
- RFC 1323 (1992)
- RFC 1379 (1992)
- RFC 1644 (1994)
- RFC 1693 (1994)
- RFC 2018 (1996)
- RFC 6247 (2011)
- RFC 7323 (2014) ✓
Read the full history of TCP Extensions for High Performance →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6263Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) FlowsCurrent
June 2011
- RFC 6266Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)Current
June 2011
- RFC 6284Port Mapping between Unicast and Multicast RTP SessionsCurrent
June 2011
- RFC 6298Computing TCP's Retransmission TimerCurrent
June 2011
- RFC 6191Reducing the TIME-WAIT State Using TCP TimestampsCurrent
April 2011
- RFC 6335Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number RegistryCurrent
August 2011
- RFC 6354Forward-Shifted RTP Redundancy Payload SupportCurrent
August 2011
- RFC 6096Stream Control Transmission Protocol (SCTP) Chunk Flags RegistrationObsoleted
January 2011
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?