RFC 8452: AES-GCM-SIV: Nonce Misuse-Resistant Authenticated Encryption
In plain English — editorial summary, not part of the RFC
This memo specifies two authenticated encryption algorithms that are nonce misuse resistant -- that is, they do not fail catastrophically if a nonce is repeated. This document is the product of the Crypto Forum Research Group.
Document record
- Document ID
- RFC8452
- Published
- April 2019
- Authors
- S. Gueron; A. Langley; Y. Lindell
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 42
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9771Properties of Authenticated Encryption with Associated Data (AEAD) AlgorithmsCurrent
May 2025
- RFC 9058Multilinear Galois Mode (MGM)Current
June 2021
- RFC 8439ChaCha20 and Poly1305 for IETF ProtocolsCurrent
June 2018
- RFC 7539ChaCha20 and Poly1305 for IETF ProtocolsObsoleted
May 2015
- RFC 7253The OCB Authenticated-Encryption AlgorithmCurrent
May 2014
- RFC 8750Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP)Current
March 2020
- RFC 7905ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)Updated
June 2016
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
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?