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

2023-04-04 Thread Rob Sayre
Hi, I'm still not sure about the list/vector rename. Aside from that, here's what I found: > It tightens some requirements and contains > updated text in areas which were found to be unclear as well as other > editorial improvements. "It contains clarifications and tightened requirements."

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

2023-04-04 Thread Stephen Farrell
Hiya, On 05/04/2023 02:47, Sean Turner wrote: A post IETF 116 bump to make sure folks get their reviews in. If you look at the diffs from RFC 8446 you can see not that much has changed. We will also take “I read it and it looks good” response. I looked at the diff between 8446bis-07 and 8446

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

2023-04-04 Thread Sean Turner
A post IETF 116 bump to make sure folks get their reviews in. If you look at the diffs from RFC 8446 you can see not that much has changed. We will also take “I read it and it looks good” response. Cheers, spt > On Mar 28, 2023, at 21:00, Christopher Wood wrote: > > As mentioned during

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

2023-04-04 Thread Hubert Kario
On Saturday, 1 April 2023 03:50:04 CEST, Krzysztof Kwiatkowski wrote: I would pair secp384r1 with Kyber768 for completely different reasons: Kyber768 is what the team kyber recommends. Agreed. I don't think there are very good reasons for NIST curves here outside wanting CNSA1 compliance, and