Re: [TLS] [Emu] Fwd: Benjamin Kaduk's Discuss on draft-ietf-emu-eap-tls13-13: (with DISCUSS and COMMENT)

2021-01-06 Thread Alan DeKok
On Jan 6, 2021, at 1:24 AM, Joseph Salowey wrote: > [Joe] I created a pull request > (https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/17) with the > proposed labels. Is this change going to cause significant problems for > implementation? After making this change: $ git diff src/

Re: [TLS] QUIC changes "early_data" extension semantics (Re: Benjamin Kaduk's Discuss on draft-ietf-quic-tls-33: (with DISCUSS and COMMENT))

2021-01-06 Thread Eric Rescorla
On Tue, Jan 5, 2021 at 7:54 PM Benjamin Kaduk wrote: > Changing Subject: and adding tls@ ... > > On Wed, Jan 06, 2021 at 02:04:02PM +1100, Martin Thomson wrote: > > Hi Ben, > > > > I'm going to respond here to your DISCUSS points, but leave the comments > to our issue tracker. Lucas has voluntee

Re: [TLS] draft-thomson-tls-snip-01

2021-01-06 Thread Martin Thomson
Hi Ben, Thanks for your input. As I am currently dealing with a DoS from the IESG, I'm going to just file issues for these and promise to get back to you. (You are flagged on them, and I've included some off-the-cuff responses there in case you want to add more.) On Thu, Jan 7, 2021, at 04:02

Re: [TLS] QUIC changes "early_data" extension semantics (Re: Benjamin Kaduk's Discuss on draft-ietf-quic-tls-33: (with DISCUSS and COMMENT))

2021-01-06 Thread Martin Thomson
Trimming this down. On Wed, Jan 6, 2021, at 14:53, Benjamin Kaduk wrote: > I didn't expect to find much appetite for changes, but I wouldn't be doing > my job if I didn't ask the question. It's a little unusual for something > outside the core protocol to change the behavior of an extension defin

Re: [TLS] QUIC changes "early_data" extension semantics (Re: Benjamin Kaduk's Discuss on draft-ietf-quic-tls-33: (with DISCUSS and COMMENT))

2021-01-06 Thread Benjamin Kaduk
On Thu, Jan 07, 2021 at 02:50:43PM +1100, Martin Thomson wrote: > Trimming this down. > > On Wed, Jan 6, 2021, at 14:53, Benjamin Kaduk wrote: > > I didn't expect to find much appetite for changes, but I wouldn't be doing > > my job if I didn't ask the question. It's a little unusual for somethin

Re: [TLS] QUIC changes "early_data" extension semantics (Re: Benjamin Kaduk's Discuss on draft-ietf-quic-tls-33: (with DISCUSS and COMMENT))

2021-01-06 Thread Martin Thomson
I'm not sure that the other discussions are productive any more, so I'll fix my errors... On Thu, Jan 7, 2021, at 15:04, Benjamin Kaduk wrote: > > This isn't an "Updates: X" moment at all in my view. Extensions to TLS > > have added new handshake messages (certificate status for instance) with

Re: [TLS] QUIC changes "early_data" extension semantics (Re: Benjamin Kaduk's Discuss on draft-ietf-quic-tls-33: (with DISCUSS and COMMENT))

2021-01-06 Thread Benjamin Kaduk
On Thu, Jan 07, 2021 at 04:11:22PM +1100, Martin Thomson wrote: > I'm not sure that the other discussions are productive any more, so I'll fix > my errors... > > On Thu, Jan 7, 2021, at 15:04, Benjamin Kaduk wrote: > > > > This isn't an "Updates: X" moment at all in my view. Extensions to TLS

Re: [TLS] [Emu] Fwd: Benjamin Kaduk's Discuss on draft-ietf-emu-eap-tls13-13: (with DISCUSS and COMMENT)

2021-01-06 Thread Benjamin Kaduk
On Tue, Jan 05, 2021 at 10:41:50AM -0500, Alan DeKok wrote: > On Jan 5, 2021, at 4:47 AM, Mohit Sethi M wrote: > > What I am gathering is that this commitment message should instead be > > made into a confirmation message, i.e. it should only be sent after > > receiving TLS Finished from the cli