This is indeed fantastic—congratulations! Will X25519MLKEM768 be enabled by default?
On Thu, Mar 6, 2025 at 2:32 PM John Mattsson <john.mattsson= 40ericsson....@dmarc.ietf.org> 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/HCdTYIoN/priorities-for-3-6 > > John > > > > *From: *Viktor Dukhovni <ietf-d...@dukhovni.org> > *Date: *Thursday, 6 March 2025 at 14:08 > *To: *tls@ietf.org <tls@ietf.org> > *Subject: *[TLS] Re: ML-KEM IANA and > draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies > > On Thu, Mar 06, 2025 at 11:29:16AM +0000, 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 -tls1_3 -tls-groups | tr ':' '\n' | tail -n6 > MLKEM512 > MLKEM768 > MLKEM1024 > SecP256r1MLKEM768 > X25519MLKEM768 > SecP384r1MLKEM1024 > > > Lowercase is generally more consistent with the other IANA codepoints, > > with some exceptions including the recent hybrids. For what it's > > worth, the slightly different bikeshed shade that I prefer is > > lowercase. > > We'll likely shortly change the group name lookup code to be > case-insensitive, just in case, and a convenience for the users. > > -- > Viktor. > > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-le...@ietf.org > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-le...@ietf.org >
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
