Re: [TLS] Question on Stateless TLS Session Resumption

No disagreements, just clarifying below:

Eric Rescorla wrote:
> Lakshminath Dondeti <ldondeti@qualcomm.com> writes:
> 
>
> 
> Yes, as I said there are *two* issues. One issue is about what
> happens when a client simply initiates a full handshake. In
> that case there is no general need to invalidate an old ticket.
> TLS is quite capable of having two parallel sessions between any
> pair of communicating parties.

This and key separation between sessions etc., are quite clear and there 
are no issues there.
> 
> However, as you indicate, you might want to explicitly terminate
> a session. As Vidya indicated, this requires server side state,
> though less than a session cache would require.

Right, this is what I was pointing out as "difficult" (for some degree 
of difficulty :) ).  Either we need more state or more state plus some 
more computation to invalidate a ticket (I am thinking a hash 
computation), if the identity (session id) is not fixed.  Yes, I took a 
quick at the relevant portions of the paper you cite, but that analysis 
assumes that there is a session id and assumes that the server has a 
blacklist of invalidated sessions.

In any event, I understand this better now.  Thanks for the clarifications.

regards,
Lakshminath

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls