RFC 9227: Using GOST Ciphers in the Encapsulating Security Payload (ESP) and Internet Key Exchange Version 2 (IKEv2) Protocols
In plain English — editorial summary, not part of the RFC
This document defines a set of encryption transforms for use in the Encapsulating Security Payload (ESP) and in the Internet Key Exchange version 2 (IKEv2) protocols, which are parts of the IP Security (IPsec) protocol suite. The transforms are based on the GOST R 34.12-2015 block ciphers (which are named "Magma" and "Kuznyechik") in Multilinear Galois Mode (MGM) and the external rekeying approach. This specification was developed to facilitate implementations that wish to support the GOST algorithms. This document does not imply IETF endorsement of the cryptographic algorithms used in this document.
Document record
- Document ID
- RFC9227
- Published
- March 2022
- Authors
- V. Smyslov
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9385Using GOST Cryptographic Algorithms in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2023
- RFC 9058Multilinear Galois Mode (MGM)Current
June 2021
- RFC 9771Properties of Authenticated Encryption with Associated Data (AEAD) AlgorithmsCurrent
May 2025
- RFC 8452AES-GCM-SIV: Nonce Misuse-Resistant Authenticated EncryptionCurrent
April 2019
- RFC 8439ChaCha20 and Poly1305 for IETF ProtocolsCurrent
June 2018
- RFC 7905ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)Updated
June 2016
- RFC 7634ChaCha20, Poly1305, and Their Use in the Internet Key Exchange Protocol (IKE) and IPsecCurrent
August 2015
- RFC 7539ChaCha20 and Poly1305 for IETF ProtocolsObsoleted
May 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?