RFC 6191: Reducing the TIME-WAIT State Using TCP Timestamps
In plain English — editorial summary, not part of the RFC
This document describes an algorithm for processing incoming SYN segments that allows higher connection-establishment rates between any two TCP endpoints when a TCP Timestamps option is present in the incoming SYN segment. This document only modifies processing of SYN segments received for connections in the TIME-WAIT state; processing in all other states is unchanged. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6191
- Published
- April 2011
- Authors
- F. Gont
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- BCP159
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6247Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic StatusCurrent
May 2011
- 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 6096Stream Control Transmission Protocol (SCTP) Chunk Flags RegistrationObsoleted
January 2011
- RFC 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
- RFC 6298Computing TCP's Retransmission TimerCurrent
June 2011
- RFC 6083Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)Updated
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?