RFC 5084: Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document specifies the conventions for using the AES-CCM and the AES-GCM authenticated encryption algorithms with the Cryptographic Message Syntax (CMS) authenticated-enveloped-data content type. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5084
- Published
- November 2007
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5083Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content TypeCurrent
November 2007
- RFC 5081Using OpenPGP Keys for Transport Layer Security (TLS) AuthenticationObsoleted
November 2007
- RFC 5080Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested FixesCurrent
December 2007
- RFC 5090RADIUS Extension for Digest AuthenticationCurrent
February 2008
- RFC 5070The Incident Object Description Exchange FormatObsoleted
December 2007
- RFC 5055Server-Based Certificate Validation Protocol (SCVP)Current
December 2007
- RFC 5054Using the Secure Remote Password (SRP) Protocol for TLS AuthenticationUpdated
November 2007
- RFC 5126CMS Advanced Electronic Signatures (CAdES)Current
March 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?