Re: [TLS] First TLS cached information draft posted

[Simon Josefsson <simon at josefsson.org>]

Martin Rex <Martin.Rex at sap.com> writes:

> It might be sensible for the client to manage cache entries based
> on several attributes, and in particular distuigish also by the
> "server name" as used in the TLS extension "Server name indication"
> in order to support TLS-compatible virtual hosting.

That is a good point, and it would help implementers to make this
explicit.  Stefan, how about adding a sentence to explain this?  After
this paragraph

   Clients MAY include an extension of type "cached_information" in the
   (extended) client hello, which SHALL contain at least one
   CachedObject as specified in section 2.

you could add

   Clients MAY need the ability to cache different values depending on
   other information in the Client Hello that modify what values the
   server uses, in particular the Server Name Indication [RFC4366]
   value.

If XML source is available, I could send you a patch. ;)

Thanks,
/Simon