Re: [ltans] Concrete examples of long-term archiving

"Liaquat Khan" <liaquat.khan@ascertia.com> Fri, 05 August 2011 10:12 UTC

Return-Path: <liaquat.khan@ascertia.com>
X-Original-To: ltans@ietfa.amsl.com
Delivered-To: ltans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 464F621F898E for <ltans@ietfa.amsl.com>; Fri, 5 Aug 2011 03:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaMI8kvT3MC4 for <ltans@ietfa.amsl.com>; Fri, 5 Aug 2011 03:12:51 -0700 (PDT)
Received: from mail.ascertia.com (unknown [94.136.44.33]) by ietfa.amsl.com (Postfix) with ESMTP id EF2A321F8426 for <ltans@ietf.org>; Fri, 5 Aug 2011 03:12:50 -0700 (PDT)
Received: from LENOVOLK ([188.28.190.173]) by ascertia.com with MailEnable ESMTP; Fri, 5 Aug 2011 11:14:36 +0100
From: "Liaquat Khan" <liaquat.khan@ascertia.com>
To: "'Aljosa Jerman Blazic'" <aljosa@setcce.si>, <ltans@ietf.org>
References: <BE403E73-8966-4FB9-9624-DAC303A0EC0D@cdc.informatik.tu-darmstadt.de><4E3ADCF5.2000206@sonnenglanz.net> <4E3AEF1C.2000809@earthlink.net> <B365DBD652563B41A90F1F3B546A6C8FDA395D@localpolitix.setcce.local>
In-Reply-To: <B365DBD652563B41A90F1F3B546A6C8FDA395D@localpolitix.setcce.local>
Date: Fri, 5 Aug 2011 11:12:56 +0100
Message-ID: <00c501cc5358$4362d600$ca288200$@ascertia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJG1ddWi7J7qPPlJ19l09vAZJTn0gLrj7rtAf1sstMDJf89G5PYgSVg
Content-Language: en-gb
X-ME-Bayesian: 0.000000
Subject: Re: [ltans] Concrete examples of long-term archiving
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ltans>, <mailto:ltans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltans>
List-Post: <mailto:ltans@ietf.org>
List-Help: <mailto:ltans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 10:12:56 -0000

Some clarifications, the British Library Digital Library Programme uses
timestamps to satisfy the needs expressed in this publicised programme of
work http://www.bl.uk/aboutus/foi/transparency/contracts/contractEIS7397.pdf


This document describes the project that was awarded to Ascertia to replace
the Thales DSE 200 units with Ascertia ADSS TSA Servers.  The document also
describes the use of evidence records to preserve the integrity of the
original data.  The British Library long-term archiving scheme pre-dates the
ERS RFC, however a similar approach of extensible long-life timestamped
evidence records are used.  Other British Library publications describe
their data storage approach.

Regards
LK

-----Original Message-----
From: ltans-bounces@ietf.org [mailto:ltans-bounces@ietf.org] On Behalf Of
Aljosa Jerman Blazic
Sent: 05 August 2011 09:00
To: ltans@ietf.org
Subject: Re: [ltans] Concrete examples of long-term archiving

> On 8/4/2011 10:55 AM, Ernst Jan van Nigtevecht wrote:
> > Dear Martin,
> > As far as I know, the British Library uses the ERS standard to proof 
> > the integrity through time of the digital collection. (I have to
check
> > for some more info; it's some time ago I heard about it.)
> Hmm - according to my spies this apparently is what was used.
> 
> http://www.thales-
> esecurity.com/EN/Products/Time%20Stamping/Time%20Stamp%20Server.as
> px

This is only time-stamping device which does not implement ERS, only
RFC3161 protocol
(http://www.thales-esecurity.com/EN/Products/Time%20Stamping/Time%20Stam
p%20Server.aspx#2). However it may be used to include archive timestamp into
ERS record... That must be separate service, not part of Thales solution.

BR

Aljosa
_______________________________________________
ltans mailing list
ltans@ietf.org
https://www.ietf.org/mailman/listinfo/ltans