RFC 4810: Long-Term Archive Service Requirements
In plain English — editorial summary, not part of the RFC
There are many scenarios in which users must be able to prove the existence of data at a specific point in time and be able to demonstrate the integrity of data since that time, even when the duration from time of existence to time of demonstration spans a large period of time. Additionally, users must be able to verify signatures on digitally signed data many years after the generation of the signature. This document describes a class of long-term archive services to support such scenarios and the technical requirements for interacting with such services. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4810
- Published
- March 2007
- Authors
- C. Wallace; U. Pordesch; R. Brandner
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4197Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching NetworksCurrent
October 2005
- RFC 4051Additional XML Security Uniform Resource Identifiers (URIs)Obsoleted
April 2005
- RFC 5753Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Current
January 2010
- RFC 3778The application/pdf Media TypeObsoleted
May 2004
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6014Cryptographic Algorithm Identifier Allocation for DNSSECUpdated
November 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 3586IP Security Policy (IPSP) RequirementsCurrent
August 2003
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?