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

2023-05-19 Thread Christopher Wood
Thanks to everyone who provided reviews and feedback for these documents! I believe we have consensus to move both forward with changes that have been incorporated during the review cycle. We’ll start preparing the shepherd writeups and then move these on in the process. Best, Chris > On Mar 2

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

2023-05-19 Thread Kris Kwiatkowski
Hello, The codepoint for P-256+Kyber768 has been just assigned by IANA. The value is 0x639A. Thanks Rich for pointing to the request form. Kind regards, Kris On 18/05/2023 22:00, Christopher Wood wrote: Thanks, Rich! On May 17, 2023, at 3:44 PM, Salz, Rich wrote:  * Can we get anothe

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

2023-05-19 Thread Ilari Liusvaara
On Fri, May 19, 2023 at 06:57:09PM +0100, Kris Kwiatkowski wrote: > Hello, > > The codepoint for P-256+Kyber768 has been just assigned by IANA. The value > is 0x639A. > Thanks Rich for pointing to the request form. I get off-by-one for the sizes of key shares. The given size of client key share

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

2023-05-19 Thread Kris Kwiatkowski
However, the difference is stated to be UncompressedPointRepresentation for P256 from TLS 1.3. AFACIT, that is 65 bytes (1 legacy_form byte, 32 bytes for x, 32 bytes for y). Right, one byte for the legacy_form is missing. Let me fix it.___ TLS mailing