+1 to EKR’s suggestion “just changing the IANA value in the other spec in AUTH48 and skipping all this wordsmithing”.
X25519MLKEM768 as “Y” asap would be very welcome. This also gives TLS WG time to discussion other RECOMMENDED and MTI changes over the next years. Cheers, John Preuß Mattsson From: Peter C <[email protected]> Date: Thursday, 7 May 2026 at 11:24 To: TLS List <[email protected]> Subject: [TLS] Re: Working group adoption call for draft-westerbaan-tls-keyshare-recommendations-02 I agree with Ekr on this. If the only change is to mark X25519MLKEM768 as "Y", then that is better done in draft-ietf-tls-ecdhe-mlkem. Adopting draft-westerbaan-tls-keyshare-recommendations brings with it the temptation to do more, e.g. deprecating ECDHE, which is premature. Peter From: Sean Turner <[email protected]> Sent: 06 May 2026 17:47 To: TLS List <[email protected]> Subject: [TLS] Re: Working group adoption call for draft-westerbaan-tls-keyshare-recommendations-02 Reminder that this is still ongoing. spt On Apr 28, 2026, at 16:46, Joseph Salowey <[email protected]> wrote: This is a working group adoption call for draft-westerbaan-tls-keyshare-recommendations-02 that we noted in [1]. The purpose of this draft is solely to mark X25519MLKEM768 as recommended "Y" in the registry. This draft represents what the authors think is an acceptable compromise combining two drafts: draft-westerbaan-tls-keyshare-recommendations-00 and draft-usama-tls-ecdhe-mlkem-update-00. The notable differences in the latest draft are: 1. The draft does not deprecate the traditional ECDHE groups 2. The draft only marks X25519MLKEM768 as "Y" and the other hybrid ECDHE groups remain "N" These differences can be addressed in future documents if necessary Please respond to this thread if you approve of adopting this draft as a working group item. If you do not approve of adopting this work, please explain why. This call will close on May 11, 2026. The chairs are not sending this draft to the FATT for review because it only updates an IANA registry for an algorithm defined in another draft. REMINDER 1: If you have not done so recently, review the TLS WG's Mail List Procedures; see [2]. REMINDER 2: As noted in [1], we plan to WGLC this draft soon after successful adoption on a working group document incorporating any changes identified in the adoption process. Thanks, Joe, Deirdre, Sean [1] https://mailarchive.ietf.org/arch/msg/tls/ckzUlvxUpa38lzHEVKwBlXwQ8x0/ [2] https://mailarchive.ietf.org/arch/msg/tls/ucdImHExlbOf4Q3BCG81gjzi2xE/ _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
