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

[Robert Relyea <[e-mail]>]

On 4/10/26 4:35 PM, Rob Sayre wrote:
> Not sure it's ready yet.
> So, I am surprised Red Hat shipped it.

Why are you surprised, we've been pretty open about  our plans. We've 
blogged about it a lot (this is only a sample):

  * https://www.redhat.com/en/blog/how-red-hat-integrating-post-quantum-cryptography-our-products
  * https://www.redhat.com/en/blog/post-quantum-cryptography-red-hat-enterprise-linux-10
  * https://www.redhat.com/en/blog/prepare-post-quantum-future-rhel-97
  * https://www.redhat.com/en/blog/whats-new-post-quantum-cryptography-rhel-101

> A matter of concern.
>
> thanks,
> Rob

Openssl have already shipped this. We've supported projects that were 
experimenting with this for a couple of years. We are on the front end 
of they PQ deployment requirements. The infrastructure needs to be in 
place long before other applications deploy these algorithms. If other 
applications that depend out our security libraries need to be PQ-ready, 
we need those libraries to be PQ-ready. We can mitigate algorithm breaks 
with our policy files, but we can't mitigate breaks in RSA or ECC if we 
don't have those other algorithms deployed.

It's true that we usually hold up implementations until the file ietf 
spec is released. In this case the risk was lower because openssl 
already deployed, the spec was simple enough, and out ability to turn if 
off was relatively simple.

bob

>
>
> 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]
>