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-08 Thread Benjamin Kaduk
Hi Mikkel, I suspect I'm misunderstanding something, because it sounds to me like you are supporting a dedicated "quic_early_data" extension to help decouple QUIC from TLS. More inline... On Thu, Jan 07, 2021 at 04:14:05PM +0100, Mikkel Fahnøe Jørgensen wrote: > > > > On 7 Jan 2021, at 07.26,

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-08 Thread Spencer Dawkins at IETF
For what it's worth, On Thu, Jan 7, 2021 at 9:15 AM Mikkel Fahnøe Jørgensen wrote: > > > On 7 Jan 2021, at 07.26, Benjamin Kaduk wrote: > > It seems like only QUIC internals would have to change, not TLS internals? > > My expectation is roughly that, if we were to compare the work needed to go

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-07 Thread Mikkel Fahnøe Jørgensen
> On 7 Jan 2021, at 07.26, Benjamin Kaduk wrote: > > It seems like only QUIC internals would have to change, not TLS internals? > > My expectation is roughly that, if we were to compare the work needed to go > from (has TLS 1.3 implementation) to (has QUIC implementation that uses >

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] 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)

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

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

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

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

2021-01-05 Thread Benjamin Kaduk
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 volunteered to do transcription for that. Sounds good. > On Tue, Jan