RFC 6960: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
In plain English — editorial summary, not part of the RFC
This document specifies a protocol useful in determining the current status of a digital certificate without requiring Certificate Revocation Lists (CRLs). Additional mechanisms addressing PKIX operational requirements are specified in separate documents. This document obsoletes RFCs 2560 and 6277. It also updates RFC 5912.
Document record
- Document ID
- RFC6960
- Published
- June 2013
- Authors
- S. Santesson; M. Myers; R. Ankney; A. Malpani; S. Galperin; C. Adams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 41
- Also known as
- —
- Updates:
- RFC 5912
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2560 (1999)
- RFC 6277 (2011)
- RFC 6960 (2013)
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6961The Transport Layer Security (TLS) Multiple Certificate Status Request ExtensionObsoleted
June 2013
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
- RFC 6664S/MIME Capabilities for Public Key DefinitionsCurrent
July 2012
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 5911New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIMEUpdated
June 2010
- RFC 8398Internationalized Email Addresses in X.509 CertificatesObsoleted
May 2018
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?