| Network Working Group | M. Pala |
| Internet-Draft | CableLabs |
| Intended status: Experimental | February 5, 2019 |
| Expires: August 9, 2019 |
Online Certificate Status Protocol - Version 2 (OCSPv2)
draft-pala-ocspv2-00
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).
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 9, 2019.
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Introduction
Explains the limitations of OCSPv1 when it comes to efficiency.
Provides a description of the protocol with particular emphasis on the different approach (range vs. one-by-one).
The OCSPv2 Request.
The OCSPv2 Response.
No special considerations for IANA.
Several security considerations need to be explicitly considered for the system administrators and application developers to understand the weaknesses of the overall architecture.
The authors would like to thank everybody who provided insightful comments and helped in the definition of the deployment considerations. Last but not least, the authors would like to thank all the people that expressed interest in implementing support for this proposal.