Online Certificate Status Protocol - Version 2 (OCSPv2)

Document Type Expired Internet-Draft (individual)
Last updated 2019-08-09 (latest revision 2019-02-05)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


With the increase number of protocols and applications that rely on digital certificates to authenticate either the communication channel (TLS) or the data itself (PKIX), the need for providing an efficient revocation system is paramount. Although the Online Certificate Status Protocol (OCSP) allows for efficient lookup of the revocation status of a certificate, the distribution of this information via HTTP (or very rarely) HTTPS is not particularly efficient for high volume websites without incurring in high distribution costs (e.g., CDN). In particular, this specification defines a new set of messages (i.e., OCSPv2 Request and OCSPv2 Response) that address the inefficiencies of OCSPv1 by (a) providing range-based responses to optimize (reduce) the number of pre-computed responses required by a CA, and (b) allowing the inclusion of other (certificate chain) responses in the same response for round-trip and caching optimization. The deployment of OCSPv2 to validate the status of a certificate is meant to lower the costs of providing revocation services and increase the efficiency of the service, thus allowing for short-lived responses (i.e., hours instead of days).


Massimiliano Pala (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)