Browse Prior Art Database

Long-Term Archive Service Requirements (RFC4810)

IP.com Disclosure Number: IPCOM000148759D
Original Publication Date: 2007-Mar-01
Included in the Prior Art Database: 2007-Mar-30
Document File: 18 page(s) / 36K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Wallace: AUTHOR [+3]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group                                         C. Wallace Request for Comments: 4810                            Cygnacom Solutions Category: Informational                                      U. Pordesch                                                  Fraunhofer Gesellschaft                                                              R. Brandner                                                    InterComponentWare AG                                                               March 2007

                  Long-Term Archive Service Requirements

Status of This Memo

   This memo provides information for the Internet community.  It does    not specify an Internet standard of any kind.  Distribution of this    memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   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.

Wallace, et al.              Informational                      [Page 1]
 RFC 4810                  Archive Requirements                March 2007

 Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4

   3.  General Principles . . . . . . . . . . . . . . . . . . . . . .  5

   4.  Technical Requirements . . . . . . . . . . . . . . . . . . . .  6

     4.1.  Enable Submission, Retrieval, and Deletion of Archived

           Data Objects . . . . . . . . . . . . . . . . . . . . . . .  6

       4.1.1.  Functional Requirements  . . . . . . . . . . . . . . .  7

       4.1.2.  Rationale  . . . . . . . . . . . . . . . . . . . . . .  7

     4.2.  Operate in accordance with a long-term archive policy  . .  8

       4.2.1.  Functional Requirements  . . . . . . . . . . . . . . .  8

       4.2.2.  Rationale  . . . . . . . . . . . . . . . . . . . . . .  9

     4.3.  Enable Management of Archived D...