RFC 8734: Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS) Version 1.3
In plain English — editorial summary, not part of the RFC
Elliptic Curve Cryptography (ECC) Brainpool curves were an option for authentication and key exchange in the Transport Layer Security (TLS) protocol version 1.2 but were deprecated by the IETF for use with TLS version 1.3 because they had little usage. However, these curves have not been shown to have significant cryptographical weaknesses, and there is some interest in using several of these curves in TLS 1.3. This document provides the necessary protocol mechanisms for using ECC Brainpool curves in TLS 1.3. This approach is not endorsed by the IETF.
Document record
- Document ID
- RFC8734
- Published
- February 2020
- Authors
- L. Bruckert; J. Merkle; M. Lochter
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7027Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS)Current
October 2013
- RFC 8902TLS Authentication Using Intelligent Transport System (ITS) CertificatesCurrent
September 2020
- RFC 8492Secure Password Ciphersuites for Transport Layer Security (TLS)Current
February 2019
- RFC 9189GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.2Current
March 2022
- RFC 7836Guidelines on the Cryptographic Algorithms to Accompany the Usage of Standards GOST R 34.10-2012 and GOST R 34.11-2012Current
March 2016
- RFC 7562Transport Layer Security (TLS) Authorization Using Digital Transmission Content Protection (DTCP) CertificatesUpdated
July 2015
- RFC 4050Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital SignaturesCurrent
April 2005
- RFC 8701Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS ExtensibilityCurrent
January 2020
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?