CertInfo single response extension Update to OCSP < draft-pinkas-2560bis-certinfo-00.txt >
draft-pinkas-2560bis-certinfo-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Denis Pinkas | ||
| Last updated | 2013-03-11 (Latest revision 2012-08-31) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
OCSP [RFC2560] has been designed to allow an OCSP server to use any kind of trustable information to answer to a client varying from CRLs to an access to a database of issued certificates. In its original version, OCSP does not allow taking full advantage of an access to a database of issued certificates. When a database of issued certificates is used by an OCSP server, this document explains how the OCSP server shall respond and how OCSP clients shall react. The proposal is intended to update 2560bis. It defines a new single extension in a single response, called certInfo. The extension is non critical. The meaning of "good", "revoked" and "unknown" are unchanged.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)