[TLS] tls@ietf122: agenda

Hi! We have posted the draft agenda for the tls@ietf122 session. The draft agenda can be found here: https://datatracker.ietf.org/doc/agenda-122-tls/ If I forgot anybody please let the chairs know; send . Remember that at this meeting we have two sessions for a total

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

On Thu, Mar 06, 2025 at 09:01:13PM +0100, Bas Westerbaan wrote: > This is indeed fantastic—congratulations! > > Will X25519MLKEM768 be enabled by default? Yes, not only enabled, but preferred, with servers sending an HRR when a client reports support for X25519MLKEM768, but does not send a corre

[TLS] ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

Hi group, I'd like to point out some inconsistencies with the IANA ML-KEM (non-hybrid) TLS Supported Groups codepoint assignments. First, the reference document for them is [draft-connolly-tls-mlkem-key-agre

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

On Thu, Mar 06, 2025 at 11:29:16AM +, Daniel Van Geest wrote: > IANA went with the uppercase naming, while OpenSSL went with lower. That is not the case, OpenSSL uses the IANA names, but the matching is now case-insensitive. Perhaps you were testing with the oqsprovider? $ openssl list

[TLS] Re: Implicit ECH Config for TLS 1.3 – addressing public_name fingerprinting

I'm not sure that we need to change the draft now in light of this. Extensions have the wonderful ability to change behavior in ways that are predictable and consistent. Given that we have the ability to extend in places that will be seen before handshaking -- i.e., the ECH config -- there is

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

On 2025-03-06 1:05 p.m., Viktor Dukhovni wrote: On Thu, Mar 06, 2025 at 11:29:16AM +, Daniel Van Geest wrote: IANA went with the uppercase naming, while OpenSSL went with lower. That is not the case, OpenSSL uses the IANA names, but the matching is now case-insensitive. Perhaps you were

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

Great that X25519MLKEM768 and MLKEM1024 will be in the 3.5 LTS release https://openssl-library.org/post/2025-02-04-release-announcement-3.5/ Also great to see DTLS 1.3 as a top priority for 3.6. https://openssl-communities.org/d/HCdTYIoN/priorities-for-3-6 John From: Viktor Dukhovni Date: Thurs

[TLS] Re: Implicit ECH Config for TLS 1.3 – addressing public_name fingerprinting

Hiya, On 06/03/2025 14:47, Martin Thomson wrote: On the broader topic, Marwan and I have a draft that looks at a different angle on this problem. That has a bunch of complicated stuff in there, but those pieces aren't necessarily core to the idea. I'm also aware of ongoing conversations about

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

First, the reference document for them is [draft-connolly-tls-mlkem-key-agreement-03], however -

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

This is indeed fantastic—congratulations! Will X25519MLKEM768 be enabled by default? On Thu, Mar 6, 2025 at 2:32 PM John Mattsson wrote: > Great that X25519MLKEM768 and MLKEM1024 will be in the 3.5 LTS release > https://openssl-library.org/post/2025-02-04-release-announcement-3.5/ > > Also grea

[TLS] [IANA #1413503] expert review for draft-ietf-tls-esni (tls-extensiontype-values)

Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list), As a designated expert for the TLS ExtensionType Values registry, can you review the proposed registration in draft-ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-author for this draft and that Rich had already approved.

[TLS] Publication has been requested for draft-ietf-tls-rfc8447bis-10

Deirdre Connolly has requested publication of draft-ietf-tls-rfc8447bis-10 as Proposed Standard on behalf of the TLS working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis/ ___ TLS mailing list

[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

On Thu, Mar 6, 2025 at 11:30 PM John Mattsson wrote: > Great that X25519MLKEM768 and MLKEM1024 will be in the 3.5 LTS release > https://openssl-library.org/post/2025-02-04-release-announcement-3.5/ > > Also great to see DTLS 1.3 as a top priority for 3.6. > > https://openssl-communities.org/d/HCd