RFC 5276: Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records
In plain English — editorial summary, not part of the RFC
The Server-based Certificate Validation Protocol (SCVP) defines an extensible means of delegating the development and validation of certification paths to a server. It can be used to support the development and validation of certification paths well after the expiration of the certificates in the path by specifying a time of interest in the past. The Evidence Record Syntax (ERS) defines structures, called evidence records, to support the non-repudiation of the existence of data. Evidence records can be used to preserve materials that comprise a certification path such that trust in the certificates can be established after the expiration of the certificates in the path and after the cryptographic algorithms used to sign the certificates in the path are no longer secure. This document describes usage of the SCVP WantBack feature to convey evidence records, enabling SCVP responders to provide preservation evidence for certificates and certificate revocation lists (CRLs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5276
- Published
- August 2008
- Authors
- C. Wallace
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
- RFC 5940Additional Cryptographic Message Syntax (CMS) Revocation Information ChoicesCurrent
August 2010
- RFC 4998Evidence Record Syntax (ERS)Current
August 2007
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- RFC 5293Sieve Email Filtering: Editheader ExtensionCurrent
August 2008
- RFC 5258Internet Message Access Protocol version 4 - LIST Command ExtensionsCurrent
June 2008
- RFC 5257Internet Message Access Protocol - ANNOTATE ExtensionCurrent
June 2008
- RFC 5256Internet Message Access Protocol - SORT and THREAD ExtensionsUpdated
June 2008
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?