RFC 8103: Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document describes the conventions for using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS). ChaCha20-Poly1305 is an authenticated encryption algorithm constructed of the ChaCha stream cipher and Poly1305 authenticator.
Document record
- Document ID
- RFC8103
- Published
- February 2017
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8120Mutual Authentication Protocol for HTTPCurrent
April 2017
- RFC 8121Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)Current
April 2017
- RFC 8080Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSECCurrent
February 2017
- RFC 8129Authentication Indicator in Kerberos TicketsCurrent
March 2017
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 8070Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Freshness ExtensionCurrent
February 2017
- RFC 8062Anonymity Support for KerberosCurrent
February 2017
- RFC 8152CBOR Object Signing and Encryption (COSE)Obsoleted
July 2017
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?