Internet-Draft Updated recommendations for TLS keyshare April 2026
Westerbaan Expires 16 October 2026 [Page]
Workgroup:
Transport Layer Security
Internet-Draft:
draft-westerbaan-tls-keyshare-recommendations-01
Updates:
8446, 9325 (if approved)
Published:
Intended Status:
Standards Track
Expires:
Author:
B. E. Westerbaan
Cloudflare

Updated recommendations for TLS keyshares

Abstract

This document recommends X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 for use in TLS by updating their entries in the TLS Supported Groups registry (previously EC Named Curve Registry) to Recommended in the light of the future arrival of cryptographically relevant quantum computers.

[[ NOTE I use key share in the title and here as it's more accurate than "group" and perhaps more well known in the context TLS than key agreement or key exchange. ]]

About This Document

This note is to be removed before publishing as an RFC.

The latest revision of this draft can be found at https://bwesterb.github.io/draft-westerbaan-tls-keyshare-recommendations/draft-westerbaan-tls-keyshare-recommendations.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-westerbaan-tls-keyshare-recommendations/.

Discussion of this document takes place on the Transport Layer Security Working Group mailing list (mailto:tls@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/tls/. Subscribe at https://www.ietf.org/mailman/listinfo/tls/.

Source for this draft and an issue tracker can be found at https://github.com/bwesterb/draft-westerbaan-tls-keyshare-recommendations.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 16 October 2026.

Table of Contents

1. Introduction

A future cryptographically relevant quantum computer (CRQC) [RFC9794] can decrypt TLS handshakes recorded today that do not use post-quantum algorithms for their key shares: algorithms designed to be resistant against quantum attack. This threat is known as "harvest now, decrypt later" (HNDL) [I-D.ietf-pquip-pqc-engineers].

To address this threat, this document updates the TLS Supported Groups registry to mark the post-quantum key shares X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 as Recommended (Y) as defined in Section 6 of [RFC9847].

2. Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. Security Considerations

Before the arrival of a cryptographically relevant quantum computer (CRQC), a TLS connection that negotiated a non-post quantum key share can be recorded decrypted in the future.

After the arrival of a CRQC, allowing a non-post quantum key share to be negotiated allows for an active quantum attack that achieves MITM, even if the server certificate is post quantum.

4. IANA Considerations

This document updates the TLS Supported Groups registry, according to the procedures in Section 6 of [RFC9847] as follows.

Table 1
Value Description Recommended
4587 SecP256r1MLKEM768 Y
4588 X25519MLKEM768 Y
4589 SecP384r1MLKEM1024 Y

5. References

5.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8446]
Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, , <https://www.rfc-editor.org/rfc/rfc8446>.
[RFC9325]
Sheffer, Y., Saint-Andre, P., and T. Fossati, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, , <https://www.rfc-editor.org/rfc/rfc9325>.
[RFC9847]
Salowey, J. and S. Turner, "IANA Registry Updates for TLS and DTLS", RFC 9847, DOI 10.17487/RFC9847, , <https://www.rfc-editor.org/rfc/rfc9847>.

5.2. Informative References

[I-D.ietf-pquip-pqc-engineers]
Banerjee, A., Reddy.K, T., Schoinianakis, D., Hollebeek, T., and M. Ounsworth, "Post-Quantum Cryptography for Engineers", Work in Progress, Internet-Draft, draft-ietf-pquip-pqc-engineers-14, , <https://datatracker.ietf.org/doc/html/draft-ietf-pquip-pqc-engineers-14>.
[RFC9794]
Driscoll, F., Parsons, M., and B. Hale, "Terminology for Post-Quantum Traditional Hybrid Schemes", RFC 9794, DOI 10.17487/RFC9794, , <https://www.rfc-editor.org/rfc/rfc9794>.

Author's Address

Bas Westerbaan
Cloudflare