Re: [TLS] Consensus call on codepoint strategy for draft-ietf-tls-hybrid-design

2023-05-01 Thread Christopher Wood
It looks like we have consensus for this strategy. We’ll work to remove codepoints from draft-ietf-tls-hybrid-design and then get experimental codepoints allocated based on draft-tls-westerbaan-xyber768d00. Best, Chris, for the chairs > On Mar 28, 2023, at 9:49 PM, Christopher Wood wrote: >

Re: [TLS] WG Adoption call for draft-sbn-tls-svcb-ech

2023-05-01 Thread Sean Turner
This WG adoption call has ended. There is consensus to adopt this I-D as a WG item. Authors: Please submit a WG version when you get the chance. Cheers, spt > On Mar 28, 2023, at 00:54, Sean Turner wrote: > > At TLS@IETF116, the sense of the room was that there was WG support to adopt > draf

Re: [TLS] WGLC for draft-ietf-tls-rfc8446bis and draft-ietf-tls-rfc8447bis

2023-05-01 Thread Sean Turner
> On Apr 11, 2023, at 12:50, Salz, Rich wrote: > > I am commenting on 8447bis. This document is just about ready to move > forward, but two fixes are needed. > > Why there are Notes still in the doc (e.g., near end of section 6 it says > about weaker elliptic curves) and think those should b

Re: [TLS] WGLC for draft-ietf-tls-rfc8446bis and draft-ietf-tls-rfc8447bis

2023-05-01 Thread Salz, Rich
Thanks for the info. >This tweak was introduced as a result of discussions in Philly (IETF115) to >address David Schinazi’s comment at the mic. If I remember correctly, the >discussion was that there’s not really a concern about exhausting the registry >space because it’s a “string" registry, b