Re: [TLS] Extensions and session resumption

[Eric Rescorla <ekr@xxxxxxxxxxxxxxxxxxxx>]

At Sat, 3 May 2008 13:09:03 +0200 (CEST),
badra@xxxxxxxx wrote:
> 
> > It's late, so I might be missing something, but I
> > can't find any information about what clients and
> > servers should put into hello extensions when they
> > intend to resume a previous session.
> 
> 
> In [RFC4366] section 3:
> 
>       If the resumption request is denied, the use of the extensions is
>       negotiated as normal.
> 
>       If, on the other hand, the older session is resumed, then the
>       server MUST ignore the extensions and send a server hello
>       containing none of the extension types.  In this case, the
>       functionality of these extensions negotiated during the original
>       session initiation is applied to the resumed session.
> 
> 
> > My code wants at least the server name extension
> > to be in the client hello in order for the server
> > to easily find the cached session (since you can
> > set up multiple session caches).  But it also makes
> > some sense to require the inclusion of truncated
> > HMAC, for example.
> 
> I think this is not possible with the current specifications (the *MUST*
> in the text above). Instead, this could be done using a local mapping.

Yes. Put an indicator in the session_id of which cache you wish to
use if you ahve more than one.

-Ekr

_______________________________________________
TLS mailing list
TLS@xxxxxxxx
https://www.ietf.org/mailman/listinfo/tls