| Internet-Draft | draft-hsharma-lamps-ocsp-nonce-02 | November 2023 |
| Sharma | Expires 9 May 2024 | [Page] |
This document updates the Nonce extension section of RFC-8954. Nonce extension is a optional extension for Online Certificate Status Protocol (OCSP) request and response messages. OCSP is used for checking the status of a certificate, and the Nonce extension is used to cryptographically bind an OCSP response message to a particular OCSP request message. This document updates RFC 8954.¶
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 9 May 2024.¶
Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document updates the usage of the Nonce extension in OCSP request and response messages. This extension was previously defined in Section 4.4.1 of [RFC6960] and updated in [RFC8954]. [RFC6960] defines OCSP extensions as optional extension, and defines condition for different extension options. [RFC6960] Nonce extension is defined as an optional extension and that provides the freedom to OCSP responders to ignore the nonce extension regardless of its existence or value in OCSP request, whereas [RFC8954] language directs the OCSP responders to MUST take action based on Nonce value in OCSP requests. For example it directs OCSP responder to MUST respond with the malformedRequest OCSPResponseStatus in case of zero or longer nonce values.¶
OCSP responder SHOULD be able to ignore the nonce values (valid or invalid) as it is an optional extension. Ignoring the longer nonce value helps OCSP responder to achieve the better backward compatibility as it wont impact the existing OCSP client that has already been sending longer nonce values. This document updates the Nonce extension section of [RFC8954] by removing the instruction to OCSP responder to reject the OCSP response that violates the nonce length requirment, provides an example of Nonce value and reinstate the backward compatibility while clearly differentiating the OCSP client and responder expectations.¶
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.¶
The message formats for OCSP requests and responses are defined in [RFC6960] and Nonce extension was updated in [RFC8954]. [RFC6960] also defines the standard extensions for OCSP messages based on the extension model employed in X.509 version 3 certificates (see [RFC5280]). [RFC8954] replaces this section to enforce minimum and maximum length for Nonce value. This document updates the Nonce extension section of [RFC8954] with clearly define the behavior of OCSP responder and client under precondition of support of Nonce extension while ignoring the OCSP request with longer Nonce length of 32 octets. This document doesn't change the length requirement for Nonce value and does not change the specifications of any of the other standard extensions defined in [RFC6960] or [RFC8954].¶
This section updates the Section 2.1 of [RFC8954], which describes the OCSP Nonce extension.¶
The nonce cryptographically binds a request and a response to prevent replay attacks.The nonce is included as one of the requestExtensions in requests; in responses, it would be included as one of the responseExtensions.In both the request and the response, the nonce will be identified by the object identifier id-pkix-ocsp- nonce, while the extnValue is the value of the nonce. If the Nonce extension is present, then the length of the nonce MUST be at least 1 octet and can be up to 32 octets.¶
The value of the nonce MUST be generated using a cryptographically strong pseudorandom number generator (see [RFC4086]). The minimum nonce length of 1 octet is defined to provide backward compatibility with older clients that follow [RFC6960].¶
id-pkix-ocsp OBJECT IDENTIFIER ::= { id-ad-ocsp }
id-pkix-ocsp-nonce OBJECT IDENTIFIER ::= { id-pkix-ocsp 2 }
¶
Nonce ::= OCTET STRING(SIZE(1..32)) Raw Nonce Example: 1FA16041C0E2D739898EC69972A4B967DFD3488148E6DA61CF3AF2DC32383383 OCSP Nonce Octet String: 04201FA16041C0E2D739898EC69972A4B967DFD3488148E6DA61CF3AF2DC32383383¶
This memo includes no request to IANA.¶
This document should not affect the security of the Internet.¶