RFC 8954: Online Certificate Status Protocol (OCSP) Nonce Extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9654.
Current version: RFC 9654 — Online Certificate Status Protocol (OCSP) Nonce Extension
In plain English — editorial summary, not part of the RFC
This document specifies the updated format of the Nonce extension in the 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 to cryptographically bind an OCSP response message to a particular OCSP request message. This document updates RFC 6960.
Document record
- Document ID
- RFC8954
- Published
- November 2020
- Authors
- M. Sahni
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8951Clarification of Enrollment over Secure Transport (EST): Transfer Encodings and ASN.1Current
November 2020
- RFC 8940Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)Current
October 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8933Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier ProtectionCurrent
October 2020
- RFC 8983Internet Key Exchange Protocol Version 2 (IKEv2) Notification Status Types for IPv4/IPv6 CoexistenceCurrent
February 2021
- RFC 8996Deprecating TLS 1.0 and TLS 1.1Current
March 2021
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?