RFC 9189: GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.2
In plain English — editorial summary, not part of the RFC
This document specifies three new cipher suites, two new signature algorithms, seven new supported groups, and two new certificate types for the Transport Layer Security (TLS) protocol version 1.2 to support the Russian cryptographic standard algorithms (called "GOST" algorithms). This document specifies a profile of TLS 1.2 with GOST algorithms so that implementers can produce interoperable implementations. This specification facilitates implementations that aim to support the GOST algorithms. This document does not imply IETF endorsement of the cipher suites, signature algorithms, supported groups, and certificate types.
Document record
- Document ID
- RFC9189
- Published
- March 2022
- Authors
- S. Smyshlyaev; D. Belyavsky; E. Alekseev
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 92
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9367GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3Current
February 2023
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 9215Using GOST R 34.10-2012 and GOST R 34.11-2012 Algorithms with the Internet X.509 Public Key InfrastructureCurrent
March 2022
- RFC 9337Generating Password-Based Keys Using the GOST AlgorithmsCurrent
December 2022
- RFC 8902TLS Authentication Using Intelligent Transport System (ITS) CertificatesCurrent
September 2020
- RFC 9548Generating Transport Key Containers (PFX) Using the GOST AlgorithmsCurrent
May 2024
- RFC 8734Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS) Version 1.3Current
February 2020
- RFC 8492Secure Password Ciphersuites for Transport Layer Security (TLS)Current
February 2019
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?