On Mon, Apr 25, 2016 at 12:13 PM, Jim Schaad <i...@augustcellars.com> wrote:
> > > > > *From:* TLS [mailto:tls-boun...@ietf.org] *On Behalf Of *Eric Rescorla > *Sent:* Monday, April 25, 2016 11:10 AM > *To:* Jim Schaad <i...@augustcellars.com> > *Cc:* tls@ietf.org > *Subject:* Re: [TLS] NewSessionTicketFormat - for PSK > > > > > > > > On Mon, Apr 25, 2016 at 11:07 AM, Jim Schaad <i...@augustcellars.com> > wrote: > > I was looking at how TLS 1.3 was going to fit into an upgrade from the > existing 1.2 version that is used for RADIUS and having vague memories of > what was going on during the F2F meeting and I ended up with the following > question. > > We are planning to indicate in the NewSessionTicket items such as if early > data is going to be allowed. Do we need to make some statements someplace > about if early data is going to be accepted for a pure PSK (or PSK-ECDH) > configuration either as an marker that it needs to be configured into the > client or as a indication sent back from the server to the client that it > will or will not accept early data when connecting? > > > > There is no way to do do early data with PSK-ECDH because the data is > > encrypted under the PSK only. > > > > -Ekr > > > > What about the case of just pure PSK? > > > > I also assume that there is nothing to stop from getting a ticket if I > connect using PSK to begin with. > Yes... Maybe I'm missing your point -Ekr > > Jim > > > > > > > > Does this apply to > some of the other fields that were being discussed as being encoded into > the > ticket as well? > > Jim > > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > > >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
