Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax
RFC 5084, “Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax”, is a Proposed Standard document published in November 2007 by R. Housley. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5084 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5083 Cryptographic Message Syntax Authenticated-Enveloped-Data Content Type
- RFC 5085 Pseudowire Virtual Circuit Connectivity Verification : A Control Channel for Pseudowires
- RFC 5082 The Generalized TTL Security Mechanism
- RFC 5086 Structure-Aware Time Division Multiplexed Circuit Emulation Service over Packet Switched Network
- RFC 5081 Using OpenPGP Keys for Transport Layer Security Authentication
- RFC 5087 Time Division Multiplexing over IP
- RFC 5080 Common Remote Authentication Dial In User Service Implementation Issues and Suggested Fixes
- RFC 5079 Rejecting Anonymous Requests in the Session Initiation Protocol