UpdatedPROPOSED STANDARDIETF stream

RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

Still current, but amended. Parts of this document are changed or extended by RFC 6818, RFC 8398, RFC 8399, RFC 9549, RFC 9598, RFC 9608, RFC 9618, RFC 9925, RFC 10007. Read both.

In plain English — editorial summary, not part of the RFC

This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. [STANDARDS-TRACK]

Document record

Document ID
RFC5280
Published
May 2008
Authors
D. Cooper; S. Santesson; S. Farrell; S. Boeyen; R. Housley; W. Polk
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
151
Also known as

Topics

Standards lineage

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

  1. RFC 2459 (1999)
  2. RFC 3280 (2002)
  3. RFC 4325 (2005)
  4. RFC 4630 (2006)
  5. RFC 5280 (2008)

Read the full history of Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

Referenced by

9 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/5280-internet-x-509-public-key-infrastructure-certificate-and-certificate-revocation