ll your
new tickets are at h3 and the steady state is 0-RTT-capable again.
David
>
>
> Kyle
>
>
>
> *From:* Eric Rescorla [mailto:e...@rtfm.com]
>
>
> *Sent:* Wednesday, October 12, 2016 4:03 PM
>
> *To:* David Benjamin <david...@chromium.org>
>
> *
to go away.
Kyle
From: Eric Rescorla [mailto:e...@rtfm.com]
Sent: Wednesday, October 12, 2016 4:03 PM
To: David Benjamin <david...@chromium.org>
Cc: Kyle Nekritz <knekr...@fb.com>; tls@ietf.org
Subject: Re: [TLS] ALPN with 0-RTT Data
On Wed, Oct 12, 2016 at 1:01 PM, David Benj
Currently the draft specifies that the ALPN must be "the same" as in the
connection that established the PSK used with 0-RTT, and that the server must
check that the selected ALPN matches what was previously used. I find this
unclear if
1) the client should select and offer one (and only one)
