TLS 1.3 Session Tickets Carry Resumption State Across Connections
TLS 1.3 Session Tickets Carry Resumption State Across Connections A completed TLS 1.3 handshake can establish more than traffic keys for the connection that is already open. After the handshake, a server can issue a NewSessionTicket that gives the client material for a later resumption attempt. The later connection can then authenticate continuity with the earlier TLS session without repeating the same certificate-based handshake path. That optimization changes where security state lives. A deployment that enables resumption is no longer concerned only with the server certificate and the keys of the current connection. Ticket lifetime, resumption secrets, cached authentication attributes, ticket protection keys, and the rules used when accepting a resumed connection become part of the boundary.