Re: [TLS] Proposed text for removing renegotiation

[Brian Smith <[e-mail]>]

On Tue, May 27, 2014 at 5:44 PM, Martin Rex <[e-mail]> wrote:

> Conceptually, the TLS session cache is readonly after an entry
> is created, and that is GOOD, i.e. full TLS handshakes create new,
> distict session cache entries, and abbreviated TLS handshakes resume
> existing session cache entries and *NEVER* modify them.
>

That is not true. During session resumption, the server can send a new
session ticket for the existing session and the client has the option of
adding the new ticket to the session (and removing the old ticket).

Also often timestamps (e.g. for LRU replacement bookkeeping) and/or
counters (e.g. for cache hit rate statistics) in a session are updated
during resumption, though these are "just" implementation issues.

Cheers,
Brian