Visual RFC.
ALL RFCs / RFC 8446
Read the RFC ↗
RFC 8446 / RESUMPTION

Resume with a ticket

04

A later connection can use a previously established PSK associated with a session ticket.

This guide explains the 2018 publication. Superseded by RFC 9846.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 2.2 ↗
RFC 8446 · § 2.2EXAMPLE
4 / 4
Resume with a ticketA ticket-shaped resumption credential returns on a new connection alongside binder proof and fresh key exchange.A ticket starts a new connectionClientServerNewSessionTicketticketPSK identity + binderfresh (EC)DHE key sharesnew connection · new traffic secrets
04
Protect the new connection.

This is PSK-with-(EC)DHE, not a replay of the old application keys.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A ticket helps establish a new connection; it is not the old traffic key.

  • NewSessionTicket is sent after a completed handshake.
  • A resumption ClientHello proves knowledge of its PSK through a binder.
  • PSK resumption can include a fresh (EC)DHE exchange for forward secrecy.
DETAILS

The examples simplify the wire representation. Follow the linked specification and application profile for implementation.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. The encrypted handshake
  2. Separate keys for separate jobs
  3. Inside an encrypted record
  4. Resume with a ticket
  5. Early data can be replayed
  6. Authentication and failure

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗