RFC 7413: TCP Fast Open
In plain English — editorial summary, not part of the RFC
This document describes an experimental TCP mechanism called TCP Fast Open (TFO). TFO allows data to be carried in the SYN and SYN-ACK packets and consumed by the receiving end during the initial connection handshake, and saves up to one full round-trip time (RTT) compared to the standard TCP, which requires a three-way handshake (3WHS) to complete before data can be exchanged. However, TFO deviates from the standard TCP semantics, since the data in the SYN could be replayed to an application in some rare circumstances. Applications should not use TFO unless they can tolerate this issue, as detailed in the Applicability section.
Document record
- Document ID
- RFC7413
- Published
- December 2014
- Authors
- Y. Cheng; J. Chu; S. Radhakrishnan; A. Jain
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7414A Roadmap for Transmission Control Protocol (TCP) Specification DocumentsUpdated
February 2015
- RFC 7417Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) DomainsCurrent
December 2014
- RFC 7390Group Communication for the Constrained Application Protocol (CoAP)Current
October 2014
- RFC 7478Web Real-Time Communication Use Cases and RequirementsCurrent
March 2015
- RFC 7337Content Distribution Network Interconnection (CDNI) RequirementsCurrent
August 2014
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 7496Additional Policies for the Partially Reliable Stream Control Transmission Protocol ExtensionCurrent
April 2015
- RFC 7323TCP Extensions for High PerformanceCurrent
September 2014
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?