RFC 5912: New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)
In plain English — editorial summary, not part of the RFC
The Public Key Infrastructure using X.509 (PKIX) certificate format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates those ASN.1 modules to conform to the 2002 version of ASN.1. There are no bits-on-the-wire changes to any of the formats; this is simply a change to the syntax. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5912
- Published
- June 2010
- Authors
- P. Hoffman; J. Schaad
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 117
- Also known as
- —
Topics
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 5911New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIMEUpdated
June 2010
- RFC 6025ASN.1 TranslationCurrent
October 2010
- 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 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
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?