RFC 9654: Online Certificate Status Protocol (OCSP) Nonce Extension
In plain English — editorial summary, not part of the RFC
RFC 8954 imposed size constraints on the optional Nonce extension for the Online Certificate Status Protocol (OCSP). OCSP is used to check the status of a certificate, and the Nonce extension is used to cryptographically bind an OCSP response message to a particular OCSP request message. Some environments use cryptographic algorithms that generate a Nonce value that is longer than 32 octets. This document also modifies the "Nonce" section of RFC 6960 to clearly define and differentiate the encoding format and values for easier implementation and understanding. This document obsoletes RFC 8954, which includes updated ASN.1 modules for OCSP, and updates RFC 6960.
Document record
- Document ID
- RFC9654
- Published
- August 2024
- Authors
- H. Sharma
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 9635Grant Negotiation and Authorization Protocol (GNAP)Current
October 2024
- RFC 9678Forward Secrecy Extension to the Improved Extensible Authentication Protocol Method for Authentication and Key Agreement (EAP-AKA' FS)Current
March 2025
- RFC 9679CBOR Object Signing and Encryption (COSE) Key ThumbprintCurrent
December 2024
- RFC 9629Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)Current
August 2024
- RFC 9683Remote Integrity Verification of Network Devices Containing Trusted Platform ModulesCurrent
December 2024
- RFC 9684A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs)Current
December 2024
- RFC 9688Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS)Current
November 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?