Re: [TLS] WGLC for draft-ietf-tls-grease

2019-02-27 Thread Hubert Kario
On Wednesday, 27 February 2019 13:52:57 CET Stephen Farrell wrote: > On 27/02/2019 12:30, Hubert Kario wrote: > > I'm not sure which part for the key_share extension you mean as being > > empty, but the key_exchange in the KeyShareEntry can't be empty, per RFC > > 8446,> > > Section 4.2.8: > >

Re: [TLS] WGLC for draft-ietf-tls-grease

2019-02-27 Thread Stephen Farrell
On 27/02/2019 12:30, Hubert Kario wrote: > I'm not sure which part for the key_share extension you mean as being empty, > but the key_exchange in the KeyShareEntry can't be empty, per RFC 8446, > Section 4.2.8: > > struct { > NamedGroup group; > opaque

Re: [TLS] WGLC for draft-ietf-tls-grease

2019-02-27 Thread Hubert Kario
On Wednesday, 27 February 2019 09:54:17 CET Stephen Farrell wrote: > Hiya, > > On 27/02/2019 01:57, Sean Turner wrote: > > This messages closes the WGLC for draft-ietf-tls-grease. The draft > > will progress as is because we received no WGLC comments. > > Apologies

Re: [TLS] WGLC for draft-ietf-tls-grease

2019-02-27 Thread Stephen Farrell
Hiya, On 27/02/2019 01:57, Sean Turner wrote: > This messages closes the WGLC for draft-ietf-tls-grease. The draft > will progress as is because we received no WGLC comments. Apologies for missing the WGLC. I've just read this and fully support it progressing. I have one question

Re: [TLS] WGLC for draft-ietf-tls-grease

2019-02-26 Thread Sean Turner
This messages closes the WGLC for draft-ietf-tls-grease. The draft will progress as is because we received no WGLC comments. spt > On Jan 24, 2019, at 10:50, Sean Turner wrote: > > This is the working group last call for the "Applying GREASE to TLS > Extensibility

[TLS] WGLC for draft-ietf-tls-grease

2019-01-24 Thread Sean Turner
This is the working group last call for the "Applying GREASE to TLS Extensibility" draft available at https://datatracker.ietf.org/doc/draft-ietf-tls-grease/. Please review the document and send your comments to the list by 2359 UTC on 8 February 2019. NOTE: There is one outstanding issue