Re: [TLS] SNI and tickets and resumption

As per RFC 6066--->Transport Layer Security (TLS) Extensions:
Extension Definitions

Note also that all the extensions defined in this document are
   relevant only when a session is initiated.  A client that requests
   session resumption does not in general know whether the server will
   accept this request, and therefore it SHOULD send the same extensions
   as it would send if it were not attempting resumption.  When a client
   includes one or more of the defined extension types in an extended
   client hello while requesting session resumption:

   -  The server name indication extension MAY be used by the server
      when deciding whether or not to resume a session as described in
      Section 3 <http://tools.ietf.org/html/rfc6066#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.

Regards,
Sajeev

On Sat, Aug 9, 2014 at 1:48 AM, Salz, Rich <rsalz@akamai.com> wrote:

> Can a client connect with an SNI extension and then later on resume or
> send a ticket with a different SNI value?
>
>
>
> I couldn’t find it documented anywhere. Am I missing something, or should
> we?
>
>
>
> --
>
> Principal Security Engineer
>
> Akamai Technologies, Cambridge MA
>
> IM: rsalz@jabber.me Twitter: RichSalz
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>