TLS 1.3 Handshake

How TLS 1.3 ships key_share in the first message to finish in 1-RTT — why it's one round trip faster than 1.2, what's now encrypted, and what was removed.

Scenario

Speed
TCP CONNECTIONTLS 1.3 HANDSHAKEENCRYPTED DATAClientServer1SYN seq=1002SYN, ACK seq=300 ack=1013ACK seq=101 ack=3014ClientHello (SNI, key_share)5ServerHello,{EncryptedExtensions, Certificate, CertificateVerify, Finished}6{Finished}↓ everything below is encrypted7{NewSessionTicket} ×N8HTTP GET /
ClientESTABLISHED
ServerESTABLISHED

Current step 8/8

HTTP GET /

Application data now flows — over TLS as encrypted records.

Round trips to first byte

2 RTT

TCP 1 + TLS 1 = 2 round trips — one less than 1.2

TCP segmentTLS handshakeApplication data

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.

TLS 1.3's big change: key_share rides inside ClientHello. In 1.2, sides first negotiated *how* to exchange keys, then sent material on round two. With 1.3's small set of groups the client just sends its most-likely DH share immediately — the server derives keys at once and returns Finished within one round trip.

Encryption coverage widened: everything after ServerHello (the {} parts in the diagram) is encrypted — the certificate hidden from observers, and CertificateVerify proves private-key ownership right away.

Cleanup too: RSA key transport, CBC, RC4, SHA-1 were removed outright, shrinking cipher-suite negotiation and downgrade surface. The caveat: 0-RTT early data is replayable, so only idempotent requests should use it. TCP/TLS Handshake Visualizer

Frequently asked questions

Exactly why is 1.3 faster than 1.2?
Key-exchange material (key_share) arrives in the first message, so the server's single reply already finalizes keys — 1 RTT vs 1.2's 2 RTT for the TLS layer.
Why is 0-RTT early data considered risky?
An attacker can record and replay it — the server can't tell a replay apart. Payments and other non-idempotent requests must disable 0-RTT; idempotent reads are fine.

Other scenarios