No Revocation Available for Short-lived X.509 Public Key Certificates
draft-housley-lamps-norevavail-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Russ Housley , Tomofumi Okubo , Joseph Mandel | ||
| Last updated | 2023-10-06 | ||
| Replaced by | draft-ietf-lamps-norevavail | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lamps-norevavail | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Short-lived X.509v3 public key certificates as profiled in RFC 5280 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. 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.
Authors
Russ Housley
Tomofumi Okubo
Joseph Mandel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)