RFC 7539: ChaCha20 and Poly1305 for IETF Protocols
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8439.
Current version: RFC 8439 — ChaCha20 and Poly1305 for IETF Protocols
In plain English — editorial summary, not part of the RFC
This document defines the ChaCha20 stream cipher as well as the use of the Poly1305 authenticator, both as stand-alone algorithms and as a "combined mode", or Authenticated Encryption with Associated Data (AEAD) algorithm. This document does not introduce any new crypto, but is meant to serve as a stable reference and an implementation guide. It is a product of the Crypto Forum Research Group (CFRG).
Document record
- Document ID
- RFC7539
- Published
- May 2015
- Authors
- Y. Nir; A. Langley
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 45
- Also known as
- —
- Obsoleted by:
- RFC 8439
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7253The OCB Authenticated-Encryption AlgorithmCurrent
May 2014
- RFC 8452AES-GCM-SIV: Nonce Misuse-Resistant Authenticated EncryptionCurrent
April 2019
- RFC 9771Properties of Authenticated Encryption with Associated Data (AEAD) AlgorithmsCurrent
May 2025
- RFC 7634ChaCha20, Poly1305, and Their Use in the Internet Key Exchange Protocol (IKE) and IPsecCurrent
August 2015
- RFC 7905ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)Updated
June 2016
- RFC 9058Multilinear Galois Mode (MGM)Current
June 2021
- RFC 9227Using GOST Ciphers in the Encapsulating Security Payload (ESP) and Internet Key Exchange Version 2 (IKEv2) ProtocolsCurrent
March 2022
- RFC 5116An Interface and Algorithms for Authenticated EncryptionCurrent
January 2008
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?