RFC 6277: Online Certificate Status Protocol Algorithm Agility
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6960.
Current document in this lineage: RFC 6960 — X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
In plain English — editorial summary, not part of the RFC
The Online Certificate Status Protocol (OCSP) requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used. This may lead to avoidable interoperability failures in contexts where multiple signature algorithms are in use. This document specifies rules for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6277
- Published
- June 2011
- Authors
- S. Santesson; P. Hallam-Baker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
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
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 6664S/MIME Capabilities for Public Key DefinitionsCurrent
July 2012
- RFC 6961The Transport Layer Security (TLS) Multiple Certificate Status Request ExtensionObsoleted
June 2013
- RFC 5019The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume EnvironmentsObsoleted
September 2007
- RFC 8739Support for Short-Term, Automatically Renewed (STAR) Certificates in the Automated Certificate Management Environment (ACME)Current
March 2020
- RFC 5940Additional Cryptographic Message Syntax (CMS) Revocation Information ChoicesCurrent
August 2010
- RFC 6290A Quick Crash Detection Method for the Internet Key Exchange Protocol (IKE)Current
June 2011
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
- RFC 6311Protocol Support for High Availability of IKEv2/IPsecCurrent
July 2011
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?