metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6961: The Transport Layer Security (TLS) Multiple Certificate Status Request Extension

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8446, RFC 9846.

Current document in this lineage: RFC 6066 — Transport Layer Security (TLS) Extensions: Extension Definitions; RFC 9846 — The Transport Layer Security (TLS) Protocol Version 1.3

In plain English — editorial summary, not part of the RFC

This document defines the Transport Layer Security (TLS) Certificate Status Version 2 Extension to allow clients to specify and support several certificate status methods. (The use of the Certificate Status extension is commonly referred to as "OCSP stapling".) Also defined is a new method based on the Online Certificate Status Protocol (OCSP) that servers can use to provide status information about not only the server's own certificate but also the status of intermediate certificates in the chain.

Document record

Document ID
RFC6961
Published
June 2013
Authors
Y. Pettersen
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
10
Also known as
—
Obsoleted by:
RFC 8446, RFC 9846

Topics

Standards lineage

This document is one revision in a chain of 15 RFCs, each formally replacing the one before it.

  1. RFC 2246 (1999)
  2. RFC 3268 (2002)
  3. RFC 3546 (2003)
  4. RFC 4346 (2006)
  5. RFC 4366 (2006)
  6. RFC 4492 (2006)
  7. RFC 4507 (2006)
  8. RFC 5077 (2008)
  9. RFC 5246 (2008)
  10. RFC 6066 (2011)
  11. RFC 6961 (2013)
  12. RFC 7627 (2015)
  13. RFC 8422 (2018)
  14. RFC 8446 (2018)
  15. RFC 9846 (2026) ✓

Read the full history of The Transport Layer Security (TLS) Protocol Version 1.3 →

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.

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?

canonical URL: /rfc/6961-the-transport-layer-security-tls-multiple-certificate-status-request-extension