metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6402: Certificate Management over CMS (CMC) Updates

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 10002, RFC 10003, RFC 10004.

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 contains a set of updates to the base syntax for CMC, a Certificate Management protocol using the Cryptographic Message Syntax (CMS). This document updates RFC 5272, RFC 5273, and RFC 5274. The new items in this document are: new controls for future work in doing server side key generation, definition of a Subject Information Access value to identify CMC servers, and the registration of a port number for TCP/IP for the CMC service to run on. [STANDARDS-TRACK]

Document record

Document ID
RFC6402
Published
November 2011
Authors
J. Schaad
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
37
Also known as
—
Obsoleted by:
RFC 10002, RFC 10003, RFC 10004
Updates:
RFC 5272, RFC 5273, RFC 5274

Topics

Standards lineage

This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.

  1. RFC 2797 (2000)
  2. RFC 5272 (2008)
  3. RFC 5273 (2008)
  4. RFC 5274 (2008)
  5. RFC 6402 (2011)
  6. RFC 10002 (2026)
  7. RFC 10003 (2026)
  8. RFC 10004 (2026) ✓

Read the full history of Certificate Management over CMS (CMC): Compliance Requirements →

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.

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?

canonical URL: /rfc/6402-certificate-management-over-cms-cmc-updates