No Revocation Available for X.509 Public Key Certificates
RFC 9608
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed author "J. Mandel": changed name from "Joseph Mandel" to "J. Mandel", changed affiliation from "SecureG Inc." to "AKAYLA, Inc.", cleared country (was "USA") |
|
2026-05-20
|
(System) | Changed author "T. Okubo": changed name from "Tomofumi Okubo" to "T. Okubo", changed affiliation from "DigiCert, Inc." to "DigiCert", cleared country (was "US") |
|
2026-05-20
|
(System) | Changed author "R. Housley": changed name from "Russ Housley" to "R. Housley", changed affiliation from "Vigil Security, LLC" to "Vigil Security", cleared country (was "US") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-07-01
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2024-06-28
|
(System) | Received changes through RFC Editor sync (created document RFC 9608, created became rfc relationship between draft-ietf-lamps-norevavail and RFC 9608, set abstract to 'X.509v3 … Received changes through RFC Editor sync (created document RFC 9608, created became rfc relationship between draft-ietf-lamps-norevavail and RFC 9608, set abstract to 'X.509v3 public key certificates are profiled in RFC 5280. Short-lived certificates are seeing greater use in the Internet. The Certification Authority (CA) that issues these short-lived certificates do not publish revocation information because the certificate lifespan that is shorter than the time needed to detect, report, and distribute revocation information. Some long-lived X.509v3 public key certificates never expire, and they are never revoked. This specification defines the noRevAvail certificate extension so that a relying party can readily determine that the CA does not publish revocation information for the certificate, and it updates the certification path validation algorithm defined in RFC 5280 so that revocation checking is skipped when the noRevAvail certificate extension is present.', set standardization level to Proposed Standard, added RFC published event at 2024-06-28, created updates relation between RFC 9608 and RFC 5280) |
|
2024-06-28
|
(System) | RFC published |