RFC 4212: Alternative Certificate Formats for the Public-Key Infrastructure Using X.509 (PKIX) Certificate Management Protocols
In plain English — editorial summary, not part of the RFC
The Public-Key Infrastructure using X.509 (PKIX) Working Group of the Internet Engineering Task Force (IETF) has defined a number of certificate management protocols. These protocols are primarily focused on X.509v3 public-key certificates. However, it is sometimes desirable to manage certificates in alternative formats as well. This document specifies how such certificates may be requested using the Certificate Request Message Format (CRMF) syntax that is used by several different protocols. It also explains how alternative certificate formats may be incorporated into such popular protocols as PKIX Certificate Management Protocol (PKIX-CMP) and Certificate Management Messages over CMS (CMC). This memo provides information for the Internet community.
Document record
- Document ID
- RFC4212
- Published
- October 2005
- Authors
- M. Blinov; C. Adams
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9158Update to the Object Identifier Registry for the PKIX Working GroupCurrent
November 2021
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
- RFC 4210Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)Obsoleted
September 2005
- RFC 5275CMS Symmetric Key Management and DistributionCurrent
June 2008
- RFC 2797Certificate Management Messages over CMSObsoleted
April 2000
- RFC 2511Internet X.509 Certificate Request Message FormatObsoleted
March 1999
- RFC 6403Suite B Profile of Certificate Management over CMSCurrent
November 2011
- RFC 8423Reclassification of Suite B Documents to Historic StatusCurrent
July 2018
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?