RFC 2630: Cryptographic Message Syntax
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3369, RFC 3370.
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. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2630
- Published
- June 1999
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 60
- 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
2 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 2631Diffie-Hellman Key Agreement MethodCurrent
June 1999
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 2409The Internet Key Exchange (IKE)Obsoleted
November 1998
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 2875Diffie-Hellman Proof-of-Possession AlgorithmsObsoleted
July 2000
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 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?