OCSP Nonce Extension
draft-ietf-lamps-ocsp-nonce-02

Document Type Active Internet-Draft (lamps WG)
Last updated 2020-05-16 (latest revision 2020-05-15)
Replaces draft-msahni-lamps-ocsp-nonce
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd Russ Housley
Shepherd write-up Show (last changed 2020-05-18)
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Russ Housley <housley@vigilsec.com>
LAMPS                                                      M. Sahni, Ed.
Internet-Draft                                        Palo Alto Networks
Updates: 6960 (if approved)                                 May 15, 2020
Intended status: Standards Track
Expires: November 16, 2020

                          OCSP Nonce Extension
                     draft-ietf-lamps-ocsp-nonce-02

Abstract

   This document specifies the updated format of the Nonce extension in
   Online Certificate Status Protocol (OCSP) request and response
   messages.  OCSP is used to check the status of a certificate and the
   Nonce extension is used in the OCSP request and response messages to
   avoid replay attacks.  This document updates the RFC 6960

Status of This Memo

   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 November 16, 2020.

Copyright Notice

   Copyright (c) 2020 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

Sahni                   Expires November 16, 2020               [Page 1]
Internet-Draft            OCSP Nonce Extension                  May 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  OCSP Extensions . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Nonce Extension . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
     3.1.  Replay Attack . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Nonce Collision . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Changes to Appendix B. of RFC 6960  . . . . . . . . . . . . .   4
     5.1.  Changes to Appendix B.1. OCSP in ASN.1 - 1998 Syntax  . .   4
     5.2.  Changes to Appendix B.2 OCSP in ASN.1 - 2008 Syntax . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document updates the usage and format of the Nonce extension
   used in OCSP request and response messages.  This extension was
   previously defined in section 4.1.1 of [RFC6960].  The [RFC6960] does
   not mention any minimum and maximum length of the nonce extension.
   Due to not having an upper or lower limit of the length of the Nonce
   extension, the OCSP responders that follow [RFC6960] may be
   vulnerable to various attacks like Denial of Service attacks
   [RFC4732], chosen prefix attacks to get a desired signature from the
   OCSP responder and possible evasions that can use the Nonce extension
   data for evasion.  This document specifies a lower limit of 1 and an
   upper limit of 32 to the length of the Nonce extension.  This
   document updates the [RFC6960].

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Sahni                   Expires November 16, 2020               [Page 2]
Internet-Draft            OCSP Nonce Extension                  May 2020

2.  OCSP Extensions

   The message format for the OCSP request and response is defined in
   the [RFC6960].  It also defines the standard extensions for OCSP
   messages based on the extension model employed in X.509 version 3
   certificates (see [RFC5280]).  Following is the list of standard
Show full document text