RFC 2797: Certificate Management Messages over CMS
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5272.
Current document in this lineage: RFC 10002 — Certificate Management over CMS (CMC); RFC 10003 — Certificate Management over CMS (CMC): Transport Protocols; RFC 10004 — Certificate Management over CMS (CMC): Compliance Requirements
In plain English — editorial summary, not part of the RFC
This document defines a Certificate Management protocol using CMS (CMC). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2797
- Published
- April 2000
- Authors
- M. Myers; X. Liu; J. Schaad; J. Weinstein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 47
- Also known as
- —
- Obsoleted by:
- RFC 5272
Topics
Standards lineage
This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.
- RFC 2797 (2000)
- RFC 5272 (2008)
- RFC 5273 (2008)
- RFC 5274 (2008)
- RFC 6402 (2011)
- RFC 10002 (2026)
- RFC 10003 (2026)
- RFC 10004 (2026) ✓
Read the full history of Certificate Management over CMS (CMC): Compliance Requirements →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 2256A Summary of the X.500(96) User Schema for use with LDAPv3Obsoleted
December 1997
- RFC 1994PPP Challenge Handshake Authentication Protocol (CHAP)Updated
August 1996
- RFC 2818HTTP Over TLSObsoleted
May 2000
- RFC 2744Generic Security Service API Version 2 : C-bindingsUpdated
January 2000
- RFC 2743Generic Security Service Application Program Interface Version 2, Update 1Updated
January 2000
- RFC 2876Use of the KEA and SKIPJACK Algorithms in CMSCurrent
July 2000
- RFC 2659Security Extensions For HTMLCurrent
August 1999
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?