How a previous session's PSK skips certificate exchange and finishes in one round trip — plus how 0-RTT early data works and when it's dangerous.
Scenario
Current step 7/7
HTTP GET /
With early_data this request already arrived inside ClientHello — data at zero extra round trips.
Round trips to first byte
1~2 RTT
PSK resumption takes 1 round trip; with 0-RTT early data the request rides with ClientHello
Numbers above arrows are the step order. In TLS 1.3, parts in {} are already encrypted — the certificate that was plaintext in 1.2 is hidden. Brackets [] mark conditional messages sent only with those cipher suites.
Re-running certificates and signature verification on every reconnect is expensive. Resumption ships a ticket (1.2) or PSK (1.3) inside ClientHello, deriving fresh session keys from the old session without certificates or signature checks.
0-RTT goes further: early_data rides with the PSK, so the request leaves before the server answers — one full round trip saved on return visits, an optimization CDNs lean on heavily.
The trade-off: early_data can't be replay-protected (idempotent reads only), and pure PSK sacrifices forward secrecy — which is why TLS 1.3 combines PSK with DH. TCP/TLS Handshake Visualizer