Protocols
Saved & recent

0-RTT early data

Also called: 0-RTT, zero round-trip time, TLS early data, early data

Zero round-trip time early data lets a client send application data before waiting for a new handshake response, using an eligible pre-shared key. In TLS 1.3 this often comes from a previous connection. It can reduce startup latency, but early data has weaker security guarantees than ordinary post-handshake data, especially around replay.

For example, a returning client might send an eligible catalog lookup immediately, while a purchase operation waits for the handshake. Which requests are acceptable depends on the application’s replay policy, not just their HTTP method. Early data is encrypted, yet recorded requests may be replayed unless appropriate defenses prevent or safely handle duplicates. A server can reject early data; “zero” does not mean zero network delay.

Read first
TLS handshake
Related
QUIC, Idempotency, Retry backoff and jitter
Further reading
IETF RFC 9846 — The Transport Layer Security (TLS) Protocol Version 1.3
eligible prior PSK returning client server first flight ClientHello encrypted early catalog lookup handshake response purchase after handshake replay risk early lookup server early-data policy optional acceptance
Illustrative early-data policy: an eligible request can leave with the first handshake flight, while replay-sensitive work waits.

View in the full Protocols collection