Fwd: [TLS] RFC 10024 on Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3

Hi,

Brand new RFC 10024 (boy that's hard to type...) on three standard
PQC/Traditional hybrid key agreement
mechanisms for TLS 1.3.  Note the chose ciphers and the authors
(CloudFlare, AWS, PQShield, University
of Waterloo).  This had strong consensus in the IETF TLS WG and is deployed
already by major cloud
and content delivery providers.

Cheers,
- Ira

---------- Forwarded message ---------
From: <[email protected]>
Date: Mon, Aug 10, 2026 at 2:15 PM
Subject: [TLS] RFC 10024 on Post-Quantum Traditional (PQ/T) Hybrid Key
Agreement Mechanisms for TLS 1.3
To: <[email protected]>, <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]
>


A new Request for Comments is now available in online RFC libraries.

        RFC 10024

        Title:      Post-Quantum Traditional (PQ/T) Hybrid Key Agreement
                    Mechanisms for TLS 1.3
        Author:     K. Kwiatkowski,
                    P. Kampanakis,
                    B. E. Westerbaan,
                    D. Stebila
        Status:     Proposed Standard
        Stream:     IETF
        Date:       August 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      9


        I-D Tag:    draft-ietf-tls-ecdhe-mlkem-04

        URL:        https://www.rfc-editor.org/info/rfc10024

        DOI:        10.17487/RFC10024

This document defines three hybrid key agreement mechanisms for TLS 1.3 --
X25519MLKEM768, SecP256r1MLKEM768, and SecP384r1MLKEM1024 -- that combine
the post-quantum ML-KEM (Module-Lattice-Based Key Encapsulation Mechanism)
with an ECDHE (Ephemeral Elliptic Curve Diffie-Hellman) exchange.

This document is a product of the Transport Layer Security Working Group of
the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

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

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp