[TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3

[Yaroslav Rosomakho <[e-mail]>]

I don't think "shipped" means "enabled by default".

As far as I can tell ML-DSA as described in this draft is shipped in the
following TLS stacks:
- OpenSSL
- BoringSSL
- Rustls (via rustls-post-quantum)
- s2n-tls
- WolfSSL
- BouncyCastle
- GnuTLS

I'm sure there are others.

Running code is supposed to be a good thing when it comes to WGLC, right?
Why is it concerning?

-yaroslav

On Sat, Apr 11, 2026 at 12:35 AM Rob Sayre <[e-mail]> wrote:

> Not sure it's ready yet.
> So, I am surprised Red Hat shipped it.
> A matter of concern.
>
> thanks,
> Rob
>
>
> On Fri, Apr 10, 2026 at 4:22 PM Robert Relyea <rrelyea=
> [e-mail]> wrote:
>
>> On 4/9/26 12:30 PM, Sean Turner wrote:
>> > This is the working group last call for Use of ML-DSA in TLS 1.3.
>> Please review draft-ietf-tls-mldsa [1] and reply to this thread indicating
>> if you think it is ready for publication or not. If you do not think it is
>> ready please indicate why. This call will end on April 23, 2026.
>>
>> I have read this draft and support publication.
>>
>> We have already built and deployed and implementation based on this draft.
>>
>>
>> >
>> > REMINDER: If you have not done so recently, review the TLS WG's Mail
>> List Procedures; see [2].
>> >
>> > The Chairs,
>> > Deirdre, Joe, and Sean
>> >
>> > [1] https://datatracker.ietf.org/doc/draft-ietf-tls-mldsa/
>> > [2]
>> https://mailarchive.ietf.org/arch/msg/tls/ucdImHExlbOf4Q3BCG81gjzi2xE/
>> >
>> > _______________________________________________
>> > TLS mailing list -- [e-mail]
>> > To unsubscribe send an email to [e-mail]
>> >
>>
>> _______________________________________________
>> TLS mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
> _______________________________________________
> TLS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>

-- 


This communication (including any attachments) is intended for the sole 
use of the intended recipient and may contain confidential, non-public, 
and/or privileged material. Use, distribution, or reproduction of this 
communication by unintended recipients is not authorized. If you received 
this communication in error, please immediately notify the sender and then 
delete all copies of this communication from your system.