RFC 10015: Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2
In plain English — editorial summary, not part of the RFC
For (D)TLS 1.2, this document deprecates the use of two key exchanges, namely Diffie-Hellman (DH) over a finite field and RSA. It also discourages the use of static Elliptic Curve Diffie-Hellman (ECDH) cipher suites. These prescriptions apply only to (D)TLS 1.2, since (D)TLS 1.0 and TLS 1.1 are deprecated by RFC 8996 and (D)TLS 1.3 either does not use the affected algorithms or does not share the relevant configuration options. (There is no DTLS version 1.1.) This document updates RFCs 4162, 4279, 4346, 4785, 5246, 5288, 5289, 5469, 5487, 5932, 6209, 6347, 6367, 6655, 7905, 8422, and 9325 to either deprecate or discourage the use of cipher suites using the above key exchange methods in (D)TLS 1.2 connections.
Document record
- Document ID
- RFC10015
- Published
- July 2026
- Authors
- N. Aviram
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
- RFC 10024Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3Current
August 2026
- RFC 6955Diffie-Hellman Proof-of-Possession AlgorithmsCurrent
May 2013
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
- RFC 8731Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448Current
February 2020
- RFC 8270Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 BitsCurrent
December 2017
- RFC 7919Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)Current
August 2016
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?