RFC 7836: Guidelines on the Cryptographic Algorithms to Accompany the Usage of Standards GOST R 34.10-2012 and GOST R 34.11-2012
In plain English — editorial summary, not part of the RFC
The purpose of this document is to make the specifications of the cryptographic algorithms defined by the Russian national standards GOST R 34.10-2012 and GOST R 34.11-2012 available to the Internet community for their implementation in the cryptographic protocols based on the accompanying algorithms. These specifications define the pseudorandom functions, the key agreement algorithm based on the Diffie-Hellman algorithm and a hash function, the parameters of elliptic curves, the key derivation functions, and the key export functions.
Document record
- Document ID
- RFC7836
- Published
- March 2016
- Authors
- S. Smyshlyaev; E. Alekseev; I. Oshkin; V. Popov; S. Leontiev; V. Podobaev; D. Belyavsky
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 8229TCP Encapsulation of IKE and IPsec PacketsObsoleted
August 2017
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 9329TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec PacketsCurrent
November 2022
- RFC 9395Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted AlgorithmsCurrent
April 2023
- RFC 5114Additional Diffie-Hellman Groups for Use with IETF StandardsCurrent
January 2008
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
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?