RFC 5275: CMS Symmetric Key Management and Distribution
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to manage (i.e., set up, distribute, and rekey) keys used with symmetric cryptographic algorithms. Also defined herein is a mechanism to organize users into groups to support distribution of encrypted content using symmetric cryptographic algorithms. The mechanism uses the Cryptographic Message Syntax (CMS) protocol and Certificate Management over CMS (CMC) protocol to manage the symmetric keys. Any member of the group can then later use this distributed shared key to decrypt other CMS encrypted objects with the symmetric key. This mechanism has been developed to support Secure/Multipurpose Internet Mail Extensions (S/MIME) Mail List Agents (MLAs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5275
- Published
- June 2008
- Authors
- S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 89
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5274Certificate Management Messages over CMS (CMC): Compliance RequirementsObsoleted
June 2008
- RFC 5273Certificate Management over CMS (CMC): Transport ProtocolsObsoleted
June 2008
- RFC 5272Certificate Management over CMS (CMC)Obsoleted
June 2008
- RFC 3852Cryptographic Message Syntax (CMS)Obsoleted
July 2004
- RFC 3657Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
January 2004
- RFC 3565Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
- RFC 3560Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
- RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated
September 2002
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?