Archivenetworking
TCP Fast Open Saves a Round Trip and Rarely Gets Used
TFO carries data in the SYN, but middleboxes, cookies, and replay concerns limit deployment.
- Published
- Reading time
- 1 min read
TCP Fast Open (TFO) lets a client send data in the initial SYN using a cookie obtained from a previous connection. It removes one round trip from connection setup, which matters most on high-latency links.
How it works
- First connection: client requests a TFO cookie; server returns one.
- Later connections: client includes the cookie and application data in the SYN.
- Server validates the cookie and processes the data before the handshake completes.
Why adoption is uneven
- Middleboxes may drop SYN data or cookies.
- Replay: early data can be replayed, so it must be idempotent.
- TLS interplay: 0-RTT already covers much of the same use case at the application layer.
- Kernel and CDN support varies.
The alternative
For HTTPS, TLS 1.3 0-RTT and connection resumption achieve similar latency wins with better-defined replay semantics — and QUIC bakes this in.
Takeaway: TFO is a niche optimization. Measure whether 0-RTT or QUIC already solves your setup latency before adding another moving part.