Hi! It looks like we have consensus to adopt this draft as a working group item. There were issues raised about wanting to delay this work until after we have completed work on key-establishment (ensuring we maintain focus on addressing “harvest now, decrypt later”) and noting that there’s no rush. We believe these can be addressed after the draft is adopted, e.g., parking a document. We would also like to further note that we do not think that adoption is impacting work on key establishment. A couple of other things to note:
1. Authors, please submit the draft named as: draft-ietf-tls-mldsa 2. Authors, please make no changes other than the boilerplate, e.g., name & dates for the -00 WG version 3. We will start the WG adoption call for draft-reddy-tls-slhdsa <https://datatracker.ietf.org/doc/draft-reddy-tls-slhdsa/> shortly Cheers, Joe and Sean > On Apr 15, 2025, at 1:32 PM, Sean Turner <s...@sn3rd.com> wrote: > > We are continuing with our WG adoption calls for the following I-D: > Use of ML-DSA in TLS 1.3 [1]; see [2] for more information about this tranche > of adoption calls. If you support adoption and are willing to review and > contribute text, please send a message to the list. If you do not support > adoption of this draft, please send a message to the list and indicate why. > This call will close at 2359 UTC on 29 April 2025. > > Reminder: This call for adoption has nothing to do with picking the > mandatory-to-implement cipher suites in TLS. > > Cheers, > Joe and Sean > > [1] https://datatracker.ietf.org/doc/draft-tls-westerbaan-mldsa/ > [2] https://mailarchive.ietf.org/arch/msg/tls/KMOTm_lE5OIAKG8_chDlRKuav7c/
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
