I support the adoption. Might be able to review it. 

-- 
V/R, 

Uri 

From: tirumal reddy <[email protected]>
Date: Wednesday, April 16, 2025 at 04:22
To: Sean Turner <[email protected]>
Cc: TLS List <[email protected]>
Subject: [EXT] [TLS] Re: WG Adoption Call for Use of ML-DSA in TLS 1.3 

I support adoption and I will review it. -Tiru On Tue, 15 Apr 2025 at 23: 04, 
Sean Turner <sean@ 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 

ZjQcmQRYFpfptBannerStart 

This Message Is From an External Sender 

This message came from outside the Laboratory. 





ZjQcmQRYFpfptBannerEnd 

I support adoption and I will review it. 



-Tiru 


On Tue, 15 Apr 2025 at 23:04, Sean Turner <[email protected] 
<mailto:[email protected]>> 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/ 
<https://datatracker.ietf.org/doc/draft-tls-westerbaan-mldsa/>
[2] https://mailarchive.ietf.org/arch/msg/tls/KMOTm_lE5OIAKG8_chDlRKuav7c/ 
<https://mailarchive.ietf.org/arch/msg/tls/KMOTm_lE5OIAKG8_chDlRKuav7c/>

_______________________________________________
TLS mailing list -- [email protected] <mailto:[email protected]>
To unsubscribe send an email to [email protected] <mailto:[email protected]> 






Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to