RFC 3852: Cryptographic Message Syntax (CMS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5652.
Current document in this lineage: RFC 3370 — Cryptographic Message Syntax (CMS) Algorithms; RFC 5652 — Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3852
- Published
- July 2004
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 56
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Read the full history of Cryptographic Message Syntax (CMS) →
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated
September 2002
- 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 3274Compressed Data Content Type for Cryptographic Message Syntax (CMS)Current
June 2002
- RFC 2984Use of the CAST-128 Encryption Algorithm in CMSCurrent
October 2000
- RFC 8933Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier ProtectionCurrent
October 2020
- RFC 4049BinaryTime: An Alternate Format for Representing Date and Time in ASN.1Obsoleted
April 2005
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?