From owner-ietf-ltans Fri Apr 8 12:29:25 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j38JTPvZ091697; Fri, 8 Apr 2005 12:29:25 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j38JTPts091696; Fri, 8 Apr 2005 12:29:25 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j38JTON4091689 for ; Fri, 8 Apr 2005 12:29:24 -0700 (PDT) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26828; Fri, 8 Apr 2005 15:29:22 -0400 (EDT) Message-Id: <200504081929.PAA26828@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ietf-ltans@imc.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ltans-ers-02.txt Date: Fri, 08 Apr 2005 15:29:22 -0400 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Long-Term Archive and Notary Services Working Group of the IETF. Title : Evidence Record Syntax (ERS) Author(s) : R. Brandner, et al. Filename : draft-ietf-ltans-ers-02.txt Pages : 25 Date : 2005-4-8 In many scenarios, users need to be able to ensure and prove the existence and integrity of data, especially digitally signed data, in a common and reproducible way over a long and possibly undetermined period of time. This document specifies the syntax and processing of an Evidence Record, designed for long-term non-repudiation of existence of data, which particularly can be used for conservation of evidence of digitally signed data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ltans-ers-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-4-8155957.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ltans-ers-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ltans-ers-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-4-8155957.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-ltans Fri Apr 29 01:46:12 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T8kCvf079756; Fri, 29 Apr 2005 01:46:12 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T8kCUf079755; Fri, 29 Apr 2005 01:46:12 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T8kA2W079717 for ; Fri, 29 Apr 2005 01:46:11 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 10:46:07 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 10:46:06 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78B08@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPA From: "HOUSSIER Loic RD-MAPS-ISS" To: X-OriginalArrivalTime: 29 Apr 2005 08:46:07.0710 (UTC) FILETIME=[E2B347E0:01C54C97] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T8kB2W079741 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Hi all, Reading ERS_02, I have question : It s said that ER can be part of the Archive or can be stored as another file. What I understand is that we can (using CMS or XADES) do ER as part of the Archive. But Is it compliant with ERS ? Thanks Loïc > -----Message d'origine----- > De : owner-ietf-ltans@mail.imc.org > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > Internet-Drafts@ietf.org > Envoyé : vendredi 8 avril 2005 21:29 > À : i-d-announce@ietf.org > Cc : ietf-ltans@imc.org > Objet : I-D ACTION:draft-ietf-ltans-ers-02.txt > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Long-Term Archive and Notary > Services Working Group of the IETF. > > Title : Evidence Record Syntax (ERS) > Author(s) : R. Brandner, et al. > Filename : draft-ietf-ltans-ers-02.txt > Pages : 25 > Date : 2005-4-8 > > In many scenarios, users need to be able to ensure and prove the > existence and integrity of data, especially digitally > signed data, in > a common and reproducible way over a long and possibly > undetermined > period of time. This document specifies the syntax and > processing of > an Evidence Record, designed for long-term non-repudiation of > existence of data, which particularly can be used for > conservation of > evidence of digitally signed data. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in > the body of the message. > You can also visit > https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login > with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-ltans-ers-02.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > From owner-ietf-ltans Fri Apr 29 02:02:19 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T92JnY086777; Fri, 29 Apr 2005 02:02:19 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T92JVH086774; Fri, 29 Apr 2005 02:02:19 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from e5.ijs.si (kekec.e5.ijs.si [193.138.1.2]) by above.proper.com (8.12.11/8.12.9) with SMTP id j3T92Gif086725 for ; Fri, 29 Apr 2005 02:02:17 -0700 (PDT) (envelope-from aljosa@e5.ijs.si) Message-Id: <200504290902.j3T92Gif086725@above.proper.com> Received: (qmail 17514 invoked from network); 29 Apr 2005 09:02:15 -0000 Received: from localhost (127.0.0.1) by e5.ijs.si with SMTP; 29 Apr 2005 09:02:15 -0000 Received: from e5.ijs.si ([127.0.0.1]) by localhost (kekec.e5.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15929-06 for ; Fri, 29 Apr 2005 11:02:13 +0200 (CEST) Received: (qmail 17507 invoked from network); 29 Apr 2005 09:02:13 -0000 Received: from arthur.e5.ijs.si (HELO Arthur) (193.138.1.27) by e5.ijs.si with SMTP; 29 Apr 2005 09:02:13 -0000 From: "A. Jerman Blazic" To: "'HOUSSIER Loic RD-MAPS-ISS'" , Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:08:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <3418F3471F1CA4409901547349FFAE2E03B78B08@FTRDMEL2.rd.francetelecom.fr> thread-index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIA= X-Virus-Scanned: amavisd-new at e5.ijs.si Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T92Iif086763 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Dear Loic I would be very careful here. XAdES for example is like the name says: syntax for extended signature, which builds on top of a signature and includes all needed complementary data to provide long term stability of digital signatures. The LTANS position, as I understand it, distances from such approach and deals with long term stability of data. ERS in this case defines requirements on how to demonstrate the existence and stability of data (not signature on particular) on a timeline. It does not define the data structure nor the syntax and at the moment you can freely use any interpretation of an evidence record including CMS. But XAdES? I am not so sure.... Best regards Aleksej > -----Original Message----- > From: owner-ietf-ltans@mail.imc.org > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER > Loic RD-MAPS-ISS > Sent: 29. april 2005 10:46 > To: ietf-ltans@imc.org > Subject: [ers-02.txt] Questions > > > Hi all, > > Reading ERS_02, I have question : > It s said that ER can be part of the Archive or can be stored > as another file. What I understand is that we can (using CMS > or XADES) do ER as part of the Archive. > But Is it compliant with ERS ? > > Thanks > > Loïc > > > > > -----Message d'origine----- > > De : owner-ietf-ltans@mail.imc.org > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 21:29 À : > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > ACTION:draft-ietf-ltans-ers-02.txt > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > This draft is a work item of the Long-Term Archive and > Notary Services > > Working Group of the IETF. > > > > Title : Evidence Record Syntax (ERS) > > Author(s) : R. Brandner, et al. > > Filename : draft-ietf-ltans-ers-02.txt > > Pages : 25 > > Date : 2005-4-8 > > > > In many scenarios, users need to be able to ensure and prove the > > existence and integrity of data, especially digitally > signed data, > > in > > a common and reproducible way over a long and possibly > undetermined > > period of time. This document specifies the syntax and > processing > > of > > an Evidence Record, designed for long-term non-repudiation of > > existence of data, which particularly can be used for > conservation > > of > > evidence of digitally signed data. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > To remove yourself from the I-D Announcement list, send a > message to > > i-d-announce-request@ietf.org with the word unsubscribe in > the body of > > the message. > > You can also visit > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > > > > > > Internet-Drafts are also available by anonymous FTP. Login with the > > username "anonymous" and a password of your e-mail address. After > > logging in, type "cd internet-drafts" and then > > "get draft-ietf-ltans-ers-02.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html or > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant > mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > From owner-ietf-ltans Fri Apr 29 02:24:34 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9OYwo096343; Fri, 29 Apr 2005 02:24:34 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T9OYj6096342; Fri, 29 Apr 2005 02:24:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9OW8i096327 for ; Fri, 29 Apr 2005 02:24:33 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 11:24:30 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:24:28 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78BE4@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsA== From: "HOUSSIER Loic RD-MAPS-ISS" To: "A. Jerman Blazic" , X-OriginalArrivalTime: 29 Apr 2005 09:24:30.0358 (UTC) FILETIME=[3F2F7B60:01C54C9D] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T9OX8i096335 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Aleksej, Thanks for your reply. So, to demonstrate the existantce and stability of signature on particular, there will be two ways in PKIX community: One using rfc3126, one with ERS attribute within a CMS signature object. Am I wrong ? Loïc > -----Message d'origine----- > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > Envoyé : vendredi 29 avril 2005 11:08 > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > Objet : RE: [ers-02.txt] Questions > > Dear Loic > > I would be very careful here. XAdES for example is like the name says: > syntax for extended signature, which builds on top of a signature and > includes all needed complementary data to provide long term > stability of > digital signatures. The LTANS position, as I understand it, > distances from > such approach and deals with long term stability of data. ERS > in this case > defines requirements on how to demonstrate the existence and > stability of > data (not signature on particular) on a timeline. It does not > define the > data structure nor the syntax and at the moment you can freely use any > interpretation of an evidence record including CMS. But > XAdES? I am not so > sure.... > > Best regards > > Aleksej > > > -----Original Message----- > > From: owner-ietf-ltans@mail.imc.org > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER > > Loic RD-MAPS-ISS > > Sent: 29. april 2005 10:46 > > To: ietf-ltans@imc.org > > Subject: [ers-02.txt] Questions > > > > > > Hi all, > > > > Reading ERS_02, I have question : > > It s said that ER can be part of the Archive or can be stored > > as another file. What I understand is that we can (using CMS > > or XADES) do ER as part of the Archive. > > But Is it compliant with ERS ? > > > > Thanks > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : owner-ietf-ltans@mail.imc.org > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 21:29 À : > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > A New Internet-Draft is available from the on-line > Internet-Drafts > > > directories. > > > This draft is a work item of the Long-Term Archive and > > Notary Services > > > Working Group of the IETF. > > > > > > Title : Evidence Record Syntax (ERS) > > > Author(s) : R. Brandner, et al. > > > Filename : draft-ietf-ltans-ers-02.txt > > > Pages : 25 > > > Date : 2005-4-8 > > > > > > In many scenarios, users need to be able to ensure and prove the > > > existence and integrity of data, especially digitally > > signed data, > > > in > > > a common and reproducible way over a long and possibly > > undetermined > > > period of time. This document specifies the syntax and > > processing > > > of > > > an Evidence Record, designed for long-term non-repudiation of > > > existence of data, which particularly can be used for > > conservation > > > of > > > evidence of digitally signed data. > > > > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > To remove yourself from the I-D Announcement list, send a > > message to > > > i-d-announce-request@ietf.org with the word unsubscribe in > > the body of > > > the message. > > > You can also visit > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > to change your subscription settings. > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > Login with the > > > username "anonymous" and a password of your e-mail address. After > > > logging in, type "cd internet-drafts" and then > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > A list of Internet-Drafts directories can be found in > > > http://www.ietf.org/shadow.html or > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > Send a message to: > > > mailserv@ietf.org. > > > In the body type: > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > NOTE: The mail server at ietf.org can return the document in > > > MIME-encoded form by using the "mpack" utility. To use this > > > feature, insert the command "ENCODING mime" before the "FILE" > > > command. To decode the response(s), you will need "munpack" or > > > a MIME-compliant mail reader. Different MIME-compliant > > mail readers > > > exhibit different behavior, especially when dealing with > > > "multipart" MIME messages (i.e. documents which have been split > > > up into multiple messages), so check your local documentation on > > > how to manipulate these messages. > > > > > > > > > Below is the data which will enable a MIME compliant mail reader > > > implementation to automatically retrieve the ASCII version of the > > > Internet-Draft. > > > > > > > From owner-ietf-ltans Fri Apr 29 02:41:37 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9fajR002339; Fri, 29 Apr 2005 02:41:36 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T9fapo002338; Fri, 29 Apr 2005 02:41:36 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from e5.ijs.si (kekec.e5.ijs.si [193.138.1.2]) by above.proper.com (8.12.11/8.12.9) with SMTP id j3T9fZKa002315 for ; Fri, 29 Apr 2005 02:41:35 -0700 (PDT) (envelope-from aljosa@e5.ijs.si) Message-Id: <200504290941.j3T9fZKa002315@above.proper.com> Received: (qmail 20253 invoked from network); 29 Apr 2005 09:41:34 -0000 Received: from localhost (127.0.0.1) by e5.ijs.si with SMTP; 29 Apr 2005 09:41:34 -0000 Received: from e5.ijs.si ([127.0.0.1]) by localhost (kekec.e5.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20126-01 for ; Fri, 29 Apr 2005 11:41:32 +0200 (CEST) Received: (qmail 20244 invoked from network); 29 Apr 2005 09:41:32 -0000 Received: from arthur.e5.ijs.si (HELO Arthur) (193.138.1.27) by e5.ijs.si with SMTP; 29 Apr 2005 09:41:32 -0000 From: "A. Jerman Blazic" To: "'HOUSSIER Loic RD-MAPS-ISS'" , Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:47:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <3418F3471F1CA4409901547349FFAE2E03B78BE4@FTRDMEL2.rd.francetelecom.fr> thread-index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQ X-Virus-Scanned: amavisd-new at e5.ijs.si Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T9faKa002332 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Loic This is what I didn't state. You have to distinguish the level of the two approaches. ERS deals mainly with providing syntax on (time) evidence and evidence on integrity of a data, while RFC3126 provides data strucutre for long term validity of a digital signatures. In this case RFC can rely on ERS for time and integrity evidence of a signature, so it is a more low level syntax. Or in other words, if you equip CMS with accredited time, you can ged basic ERS structure (of course ERS is more than that: e.g. grouping and hash trees). This is why I said the approaches of LTANS vs. XAdES are somehow different, while addressing similar problems. BR Aleksej > -----Original Message----- > From: HOUSSIER Loic RD-MAPS-ISS > [mailto:loic.houssier@francetelecom.com] > Sent: 29. april 2005 11:24 > To: A. Jerman Blazic; ietf-ltans@imc.org > Subject: RE: [ers-02.txt] Questions > > Aleksej, > Thanks for your reply. > > So, to demonstrate the existantce and stability of signature > on particular, there will be two ways in PKIX community: > One using rfc3126, one with ERS attribute within a CMS > signature object. Am I wrong ? > > Loïc > > > > > -----Message d'origine----- > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > vendredi 29 > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > Objet : RE: [ers-02.txt] Questions > > > > Dear Loic > > > > I would be very careful here. XAdES for example is like the > name says: > > syntax for extended signature, which builds on top of a > signature and > > includes all needed complementary data to provide long term > stability > > of digital signatures. The LTANS position, as I understand it, > > distances from such approach and deals with long term stability of > > data. ERS in this case defines requirements on how to > demonstrate the > > existence and stability of data (not signature on particular) on a > > timeline. It does not define the data structure nor the > syntax and at > > the moment you can freely use any interpretation of an > evidence record > > including CMS. But XAdES? I am not so sure.... > > > > Best regards > > > > Aleksej > > > > > -----Original Message----- > > > From: owner-ietf-ltans@mail.imc.org > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER Loic > > > RD-MAPS-ISS > > > Sent: 29. april 2005 10:46 > > > To: ietf-ltans@imc.org > > > Subject: [ers-02.txt] Questions > > > > > > > > > Hi all, > > > > > > Reading ERS_02, I have question : > > > It s said that ER can be part of the Archive or can be stored as > > > another file. What I understand is that we can (using CMS > or XADES) > > > do ER as part of the Archive. > > > But Is it compliant with ERS ? > > > > > > Thanks > > > > > > Loïc > > > > > > > > > > > > > -----Message d'origine----- > > > > De : owner-ietf-ltans@mail.imc.org > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > 21:29 À : > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts > > > > directories. > > > > This draft is a work item of the Long-Term Archive and > > > Notary Services > > > > Working Group of the IETF. > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > Author(s) : R. Brandner, et al. > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > Pages : 25 > > > > Date : 2005-4-8 > > > > > > > > In many scenarios, users need to be able to ensure and > prove the > > > > existence and integrity of data, especially digitally > > > signed data, > > > > in > > > > a common and reproducible way over a long and possibly > > > undetermined > > > > period of time. This document specifies the syntax and > > > processing > > > > of > > > > an Evidence Record, designed for long-term > non-repudiation of > > > > existence of data, which particularly can be used for > > > conservation > > > > of > > > > evidence of digitally signed data. > > > > > > > > A URL for this Internet-Draft is: > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > message to > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > the body of > > > > the message. > > > > You can also visit > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > to change your subscription settings. > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > Login with the > > > > username "anonymous" and a password of your e-mail > address. After > > > > logging in, type "cd internet-drafts" and then > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > A list of Internet-Drafts directories can be found in > > > > http://www.ietf.org/shadow.html or > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > Send a message to: > > > > mailserv@ietf.org. > > > > In the body type: > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > MIME-encoded form by using the "mpack" utility. > To use this > > > > feature, insert the command "ENCODING mime" > before the "FILE" > > > > command. To decode the response(s), you will > need "munpack" or > > > > a MIME-compliant mail reader. Different MIME-compliant > > > mail readers > > > > exhibit different behavior, especially when dealing with > > > > "multipart" MIME messages (i.e. documents which > have been split > > > > up into multiple messages), so check your local > documentation on > > > > how to manipulate these messages. > > > > > > > > > > > > Below is the data which will enable a MIME compliant > mail reader > > > > implementation to automatically retrieve the ASCII > version of the > > > > Internet-Draft. > > > > > > > > > > > > From owner-ietf-ltans Fri Apr 29 04:12:45 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TBCicG038672; Fri, 29 Apr 2005 04:12:44 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TBCiTG038671; Fri, 29 Apr 2005 04:12:44 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TBCdwR038627 for ; Fri, 29 Apr 2005 04:12:42 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 13:12:37 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 13:12:36 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78D10@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmA= From: "HOUSSIER Loic RD-MAPS-ISS" To: "A. Jerman Blazic" , X-OriginalArrivalTime: 29 Apr 2005 11:12:37.0423 (UTC) FILETIME=[59C70BF0:01C54CAC] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TBChwR038660 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Aleksej, Well, it's more clear to me now... ERS just proposes a syntax for EV that can be used by CSM to kepp electronic signature valid. But according to RFC-3126, ES-A is a format that reech the same target than ERS in CMS. So my question is, if i want to archive signature, i have the choice between RFC3126 ES-A or ERS in CMS. Am I right ? If I am, will ES-A be obsoleted by ERS in CSM (as shown in Appendix A in [ers-02]) ? But be sure that I understand ERS is more than just a way to maintain a singature valid. Regards, Loïc > -----Message d'origine----- > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > Envoyé : vendredi 29 avril 2005 11:48 > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > Objet : RE: [ers-02.txt] Questions > > Loic > > This is what I didn't state. You have to distinguish the > level of the two > approaches. ERS deals mainly with providing syntax on (time) > evidence and > evidence on integrity of a data, while RFC3126 provides data > strucutre for > long term validity of a digital signatures. In this case RFC > can rely on ERS > for time and integrity evidence of a signature, so it is a > more low level > syntax. Or in other words, if you equip CMS with accredited > time, you can > ged basic ERS structure (of course ERS is more than that: > e.g. grouping and > hash trees). This is why I said the approaches of LTANS vs. XAdES are > somehow different, while addressing similar problems. > > BR > > Aleksej > > > -----Original Message----- > > From: HOUSSIER Loic RD-MAPS-ISS > > [mailto:loic.houssier@francetelecom.com] > > Sent: 29. april 2005 11:24 > > To: A. Jerman Blazic; ietf-ltans@imc.org > > Subject: RE: [ers-02.txt] Questions > > > > Aleksej, > > Thanks for your reply. > > > > So, to demonstrate the existantce and stability of signature > > on particular, there will be two ways in PKIX community: > > One using rfc3126, one with ERS attribute within a CMS > > signature object. Am I wrong ? > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > vendredi 29 > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > ietf-ltans@imc.org > > > Objet : RE: [ers-02.txt] Questions > > > > > > Dear Loic > > > > > > I would be very careful here. XAdES for example is like the > > name says: > > > syntax for extended signature, which builds on top of a > > signature and > > > includes all needed complementary data to provide long term > > stability > > > of digital signatures. The LTANS position, as I understand it, > > > distances from such approach and deals with long term > stability of > > > data. ERS in this case defines requirements on how to > > demonstrate the > > > existence and stability of data (not signature on > particular) on a > > > timeline. It does not define the data structure nor the > > syntax and at > > > the moment you can freely use any interpretation of an > > evidence record > > > including CMS. But XAdES? I am not so sure.... > > > > > > Best regards > > > > > > Aleksej > > > > > > > -----Original Message----- > > > > From: owner-ietf-ltans@mail.imc.org > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > HOUSSIER Loic > > > > RD-MAPS-ISS > > > > Sent: 29. april 2005 10:46 > > > > To: ietf-ltans@imc.org > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > Hi all, > > > > > > > > Reading ERS_02, I have question : > > > > It s said that ER can be part of the Archive or can be > stored as > > > > another file. What I understand is that we can (using CMS > > or XADES) > > > > do ER as part of the Archive. > > > > But Is it compliant with ERS ? > > > > > > > > Thanks > > > > > > > > Loïc > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > 21:29 À : > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > A New Internet-Draft is available from the on-line > > > Internet-Drafts > > > > > directories. > > > > > This draft is a work item of the Long-Term Archive and > > > > Notary Services > > > > > Working Group of the IETF. > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > Author(s) : R. Brandner, et al. > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > Pages : 25 > > > > > Date : 2005-4-8 > > > > > > > > > > In many scenarios, users need to be able to ensure and > > prove the > > > > > existence and integrity of data, especially digitally > > > > signed data, > > > > > in > > > > > a common and reproducible way over a long and possibly > > > > undetermined > > > > > period of time. This document specifies the syntax and > > > > processing > > > > > of > > > > > an Evidence Record, designed for long-term > > non-repudiation of > > > > > existence of data, which particularly can be used for > > > > conservation > > > > > of > > > > > evidence of digitally signed data. > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > message to > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > the body of > > > > > the message. > > > > > You can also visit > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > to change your subscription settings. > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > Login with the > > > > > username "anonymous" and a password of your e-mail > > address. After > > > > > logging in, type "cd internet-drafts" and then > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > http://www.ietf.org/shadow.html or > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > Send a message to: > > > > > mailserv@ietf.org. > > > > > In the body type: > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > > MIME-encoded form by using the "mpack" utility. > > To use this > > > > > feature, insert the command "ENCODING mime" > > before the "FILE" > > > > > command. To decode the response(s), you will > > need "munpack" or > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > mail readers > > > > > exhibit different behavior, especially when dealing with > > > > > "multipart" MIME messages (i.e. documents which > > have been split > > > > > up into multiple messages), so check your local > > documentation on > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > mail reader > > > > > implementation to automatically retrieve the ASCII > > version of the > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > From owner-ietf-ltans Fri Apr 29 09:11:28 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGBS1i028017; Fri, 29 Apr 2005 09:11:28 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TGBSat028016; Fri, 29 Apr 2005 09:11:28 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mucmx01.ixos.de (mucmx01.ixos.de [149.235.31.98]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGBPWo028004 for ; Fri, 29 Apr 2005 09:11:26 -0700 (PDT) (envelope-from tgondrom@opentext.com) Received: from samxg01.opentext.net (localhost [127.0.0.1]) by mucmx01.ixos.de (8.12.10+Sun/8.12.10) with ESMTP id j3TGBLiA017688; Fri, 29 Apr 2005 18:11:22 +0200 (MEST) Received: from MUCXGC1.opentext.net ([149.235.128.13]) by samxg01.opentext.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 09:11:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 18:11:29 +0200 Message-ID: <3C1BE8610E44734499EF92FB35F5B070CA4C8A@MUCXGC1.opentext.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmAACdYbEA== From: "Tobias Gondrom" To: "HOUSSIER Loic RD-MAPS-ISS" Cc: , "A. Jerman Blazic" X-OriginalArrivalTime: 29 Apr 2005 16:11:20.0703 (UTC) FILETIME=[14E288F0:01C54CD6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TGBQWo028011 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Loïc, Maybe to provide further info: > Well, it's more clear to me now... > ERS just proposes a syntax for EV that can be used by CSM to kepp > electronic signature valid. > But according to RFC-3126, ES-A is a format that reech the same target > than ERS in CMS. Yes. In some way ES-A in RFC3126 is trying to achieve the same. With ES-A you can try to "re-sign" a signed file with a new layer wrapped around it every time a cryptographic algorithm gets weak (respectively before) - the concept is quite obvious and well thought for the use case to store only a limited number of signed documents. As Aleksej already described ERS also enables the possibility for long-term non repudiation and integrity. Second aspect of ERS is that it scales for large volumes of signed documents. With ES-A you have to wrap around every file another layer. With ERS you just create new hashtrees - which is if you think of e.g. about 10^6 to 10^9 documents a lot better concerning performance. (especially if only e.g. a public key algorithm gets weak or a used key length is no longer sufficient.) Concerning RFC3126: From my opinion it is not necessary that ERS will obsolete ES-A. But I surely expect that many big storage, Document Management System and ECM vendors will implement ERS and not ES-A. So in B2B and B2C we will most probably seeing a lot of ERS. The coexistence of ES-A and ERS will be something to discuss when ERS is finally an RFC. Best regards Tobias > > So my question is, if i want to archive signature, i have the choice > between RFC3126 ES-A or ERS in CMS. Am I right ? > > If I am, will ES-A be obsoleted by ERS in CSM (as shown in Appendix A in > [ers-02]) ? > > But be sure that I understand ERS is more than just a way to maintain a > singature valid. > > Regards, > > Loïc > > > > > -----Message d'origine----- > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > > Envoyé : vendredi 29 avril 2005 11:48 > > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > Objet : RE: [ers-02.txt] Questions > > > > Loic > > > > This is what I didn't state. You have to distinguish the > > level of the two > > approaches. ERS deals mainly with providing syntax on (time) > > evidence and > > evidence on integrity of a data, while RFC3126 provides data > > strucutre for > > long term validity of a digital signatures. In this case RFC > > can rely on ERS > > for time and integrity evidence of a signature, so it is a > > more low level > > syntax. Or in other words, if you equip CMS with accredited > > time, you can > > ged basic ERS structure (of course ERS is more than that: > > e.g. grouping and > > hash trees). This is why I said the approaches of LTANS vs. XAdES are > > somehow different, while addressing similar problems. > > > > BR > > > > Aleksej > > > > > -----Original Message----- > > > From: HOUSSIER Loic RD-MAPS-ISS > > > [mailto:loic.houssier@francetelecom.com] > > > Sent: 29. april 2005 11:24 > > > To: A. Jerman Blazic; ietf-ltans@imc.org > > > Subject: RE: [ers-02.txt] Questions > > > > > > Aleksej, > > > Thanks for your reply. > > > > > > So, to demonstrate the existantce and stability of signature > > > on particular, there will be two ways in PKIX community: > > > One using rfc3126, one with ERS attribute within a CMS > > > signature object. Am I wrong ? > > > > > > Loïc > > > > > > > > > > > > > -----Message d'origine----- > > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > > vendredi 29 > > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > > ietf-ltans@imc.org > > > > Objet : RE: [ers-02.txt] Questions > > > > > > > > Dear Loic > > > > > > > > I would be very careful here. XAdES for example is like the > > > name says: > > > > syntax for extended signature, which builds on top of a > > > signature and > > > > includes all needed complementary data to provide long term > > > stability > > > > of digital signatures. The LTANS position, as I understand it, > > > > distances from such approach and deals with long term > > stability of > > > > data. ERS in this case defines requirements on how to > > > demonstrate the > > > > existence and stability of data (not signature on > > particular) on a > > > > timeline. It does not define the data structure nor the > > > syntax and at > > > > the moment you can freely use any interpretation of an > > > evidence record > > > > including CMS. But XAdES? I am not so sure.... > > > > > > > > Best regards > > > > > > > > Aleksej > > > > > > > > > -----Original Message----- > > > > > From: owner-ietf-ltans@mail.imc.org > > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > > HOUSSIER Loic > > > > > RD-MAPS-ISS > > > > > Sent: 29. april 2005 10:46 > > > > > To: ietf-ltans@imc.org > > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > Reading ERS_02, I have question : > > > > > It s said that ER can be part of the Archive or can be > > stored as > > > > > another file. What I understand is that we can (using CMS > > > or XADES) > > > > > do ER as part of the Archive. > > > > > But Is it compliant with ERS ? > > > > > > > > > > Thanks > > > > > > > > > > Loïc > > > > > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > > 21:29 À : > > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > A New Internet-Draft is available from the on-line > > > > Internet-Drafts > > > > > > directories. > > > > > > This draft is a work item of the Long-Term Archive and > > > > > Notary Services > > > > > > Working Group of the IETF. > > > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > > Author(s) : R. Brandner, et al. > > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > > Pages : 25 > > > > > > Date : 2005-4-8 > > > > > > > > > > > > In many scenarios, users need to be able to ensure and > > > prove the > > > > > > existence and integrity of data, especially digitally > > > > > signed data, > > > > > > in > > > > > > a common and reproducible way over a long and possibly > > > > > undetermined > > > > > > period of time. This document specifies the syntax and > > > > > processing > > > > > > of > > > > > > an Evidence Record, designed for long-term > > > non-repudiation of > > > > > > existence of data, which particularly can be used for > > > > > conservation > > > > > > of > > > > > > evidence of digitally signed data. > > > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > > message to > > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > > the body of > > > > > > the message. > > > > > > You can also visit > > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > > to change your subscription settings. > > > > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > > Login with the > > > > > > username "anonymous" and a password of your e-mail > > > address. After > > > > > > logging in, type "cd internet-drafts" and then > > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > > http://www.ietf.org/shadow.html or > > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > > > Send a message to: > > > > > > mailserv@ietf.org. > > > > > > In the body type: > > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > > > MIME-encoded form by using the "mpack" utility. > > > To use this > > > > > > feature, insert the command "ENCODING mime" > > > before the "FILE" > > > > > > command. To decode the response(s), you will > > > need "munpack" or > > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > > mail readers > > > > > > exhibit different behavior, especially when dealing with > > > > > > "multipart" MIME messages (i.e. documents which > > > have been split > > > > > > up into multiple messages), so check your local > > > documentation on > > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > > mail reader > > > > > > implementation to automatically retrieve the ASCII > > > version of the > > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > > > > > > > > From owner-ietf-ltans Fri Apr 29 09:16:34 2005 Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGGYVg028897; Fri, 29 Apr 2005 09:16:34 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TGGYfl028896; Fri, 29 Apr 2005 09:16:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGGXLK028888 for ; Fri, 29 Apr 2005 09:16:33 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 18:16:31 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 18:16:30 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B7929F@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmAACdYbEAAA8sNQ From: "HOUSSIER Loic RD-MAPS-ISS" To: "Tobias Gondrom" Cc: , "A. Jerman Blazic" X-OriginalArrivalTime: 29 Apr 2005 16:16:31.0152 (UTC) FILETIME=[CDED4B00:01C54CD6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TGGYLK028889 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Ok then, it's all clear to me now. Thanks a lot for spending time to explain. Best regards, Loïc > -----Message d'origine----- > De : Tobias Gondrom [mailto:tgondrom@opentext.com] > Envoyé : vendredi 29 avril 2005 18:11 > À : HOUSSIER Loic RD-MAPS-ISS > Cc : ietf-ltans@imc.org; A. Jerman Blazic > Objet : RE: [ers-02.txt] Questions > > Loïc, > > Maybe to provide further info: > > > Well, it's more clear to me now... > > ERS just proposes a syntax for EV that can be used by CSM to kepp > > electronic signature valid. > > But according to RFC-3126, ES-A is a format that reech the > same target > > than ERS in CMS. > > Yes. In some way ES-A in RFC3126 is trying to achieve the same. > With ES-A you can try to "re-sign" a signed file with a new > layer wrapped around it every time a cryptographic algorithm > gets weak (respectively before) - the concept is quite > obvious and well thought for the use case to store only a > limited number of signed documents. > > As Aleksej already described ERS also enables the possibility > for long-term non repudiation and integrity. > Second aspect of ERS is that it scales for large volumes of > signed documents. With ES-A you have to wrap around every > file another layer. > With ERS you just create new hashtrees - which is if you > think of e.g. about 10^6 to 10^9 documents a lot better > concerning performance. (especially if only e.g. a public key > algorithm gets weak or a used key length is no longer sufficient.) > > Concerning RFC3126: From my opinion it is not necessary that > ERS will obsolete ES-A. But I surely expect that many big > storage, Document Management System and ECM vendors will > implement ERS and not ES-A. So in B2B and B2C we will most > probably seeing a lot of ERS. > > The coexistence of ES-A and ERS will be something to discuss > when ERS is finally an RFC. > > Best regards > > Tobias > > > > > > > > > So my question is, if i want to archive signature, i have the choice > > between RFC3126 ES-A or ERS in CMS. Am I right ? > > > > If I am, will ES-A be obsoleted by ERS in CSM (as shown in > Appendix A in > > [ers-02]) ? > > > > But be sure that I understand ERS is more than just a way > to maintain a > > singature valid. > > > > Regards, > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > > > Envoyé : vendredi 29 avril 2005 11:48 > > > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > > Objet : RE: [ers-02.txt] Questions > > > > > > Loic > > > > > > This is what I didn't state. You have to distinguish the > > > level of the two > > > approaches. ERS deals mainly with providing syntax on (time) > > > evidence and > > > evidence on integrity of a data, while RFC3126 provides data > > > strucutre for > > > long term validity of a digital signatures. In this case RFC > > > can rely on ERS > > > for time and integrity evidence of a signature, so it is a > > > more low level > > > syntax. Or in other words, if you equip CMS with accredited > > > time, you can > > > ged basic ERS structure (of course ERS is more than that: > > > e.g. grouping and > > > hash trees). This is why I said the approaches of LTANS > vs. XAdES are > > > somehow different, while addressing similar problems. > > > > > > BR > > > > > > Aleksej > > > > > > > -----Original Message----- > > > > From: HOUSSIER Loic RD-MAPS-ISS > > > > [mailto:loic.houssier@francetelecom.com] > > > > Sent: 29. april 2005 11:24 > > > > To: A. Jerman Blazic; ietf-ltans@imc.org > > > > Subject: RE: [ers-02.txt] Questions > > > > > > > > Aleksej, > > > > Thanks for your reply. > > > > > > > > So, to demonstrate the existantce and stability of signature > > > > on particular, there will be two ways in PKIX community: > > > > One using rfc3126, one with ERS attribute within a CMS > > > > signature object. Am I wrong ? > > > > > > > > Loïc > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > > > vendredi 29 > > > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > > > ietf-ltans@imc.org > > > > > Objet : RE: [ers-02.txt] Questions > > > > > > > > > > Dear Loic > > > > > > > > > > I would be very careful here. XAdES for example is like the > > > > name says: > > > > > syntax for extended signature, which builds on top of a > > > > signature and > > > > > includes all needed complementary data to provide long term > > > > stability > > > > > of digital signatures. The LTANS position, as I understand it, > > > > > distances from such approach and deals with long term > > > stability of > > > > > data. ERS in this case defines requirements on how to > > > > demonstrate the > > > > > existence and stability of data (not signature on > > > particular) on a > > > > > timeline. It does not define the data structure nor the > > > > syntax and at > > > > > the moment you can freely use any interpretation of an > > > > evidence record > > > > > including CMS. But XAdES? I am not so sure.... > > > > > > > > > > Best regards > > > > > > > > > > Aleksej > > > > > > > > > > > -----Original Message----- > > > > > > From: owner-ietf-ltans@mail.imc.org > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > > > HOUSSIER Loic > > > > > > RD-MAPS-ISS > > > > > > Sent: 29. april 2005 10:46 > > > > > > To: ietf-ltans@imc.org > > > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > Reading ERS_02, I have question : > > > > > > It s said that ER can be part of the Archive or can be > > > stored as > > > > > > another file. What I understand is that we can (using CMS > > > > or XADES) > > > > > > do ER as part of the Archive. > > > > > > But Is it compliant with ERS ? > > > > > > > > > > > > Thanks > > > > > > > > > > > > Loïc > > > > > > > > > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > > > 21:29 À : > > > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > > > A New Internet-Draft is available from the on-line > > > > > Internet-Drafts > > > > > > > directories. > > > > > > > This draft is a work item of the Long-Term Archive and > > > > > > Notary Services > > > > > > > Working Group of the IETF. > > > > > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > > > Author(s) : R. Brandner, et al. > > > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > > > Pages : 25 > > > > > > > Date : 2005-4-8 > > > > > > > > > > > > > > In many scenarios, users need to be able to ensure and > > > > prove the > > > > > > > existence and integrity of data, especially digitally > > > > > > signed data, > > > > > > > in > > > > > > > a common and reproducible way over a long and possibly > > > > > > undetermined > > > > > > > period of time. This document specifies the syntax and > > > > > > processing > > > > > > > of > > > > > > > an Evidence Record, designed for long-term > > > > non-repudiation of > > > > > > > existence of data, which particularly can be used for > > > > > > conservation > > > > > > > of > > > > > > > evidence of digitally signed data. > > > > > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > > > message to > > > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > > > the body of > > > > > > > the message. > > > > > > > You can also visit > > > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > > > to change your subscription settings. > > > > > > > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > > > Login with the > > > > > > > username "anonymous" and a password of your e-mail > > > > address. After > > > > > > > logging in, type "cd internet-drafts" and then > > > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > > > http://www.ietf.org/shadow.html or > > > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > > > > > Send a message to: > > > > > > > mailserv@ietf.org. > > > > > > > In the body type: > > > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > > > NOTE: The mail server at ietf.org can return > the document in > > > > > > > MIME-encoded form by using the "mpack" utility. > > > > To use this > > > > > > > feature, insert the command "ENCODING mime" > > > > before the "FILE" > > > > > > > command. To decode the response(s), you will > > > > need "munpack" or > > > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > > > mail readers > > > > > > > exhibit different behavior, especially when dealing with > > > > > > > "multipart" MIME messages (i.e. documents which > > > > have been split > > > > > > > up into multiple messages), so check your local > > > > documentation on > > > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > > > mail reader > > > > > > > implementation to automatically retrieve the ASCII > > > > version of the > > > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGGYVg028897; Fri, 29 Apr 2005 09:16:34 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TGGYfl028896; Fri, 29 Apr 2005 09:16:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGGXLK028888 for ; Fri, 29 Apr 2005 09:16:33 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 18:16:31 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 18:16:30 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B7929F@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmAACdYbEAAA8sNQ From: "HOUSSIER Loic RD-MAPS-ISS" To: "Tobias Gondrom" Cc: , "A. Jerman Blazic" X-OriginalArrivalTime: 29 Apr 2005 16:16:31.0152 (UTC) FILETIME=[CDED4B00:01C54CD6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TGGYLK028889 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Ok then, it's all clear to me now. Thanks a lot for spending time to explain. Best regards, Loïc > -----Message d'origine----- > De : Tobias Gondrom [mailto:tgondrom@opentext.com] > Envoyé : vendredi 29 avril 2005 18:11 > À : HOUSSIER Loic RD-MAPS-ISS > Cc : ietf-ltans@imc.org; A. Jerman Blazic > Objet : RE: [ers-02.txt] Questions > > Loïc, > > Maybe to provide further info: > > > Well, it's more clear to me now... > > ERS just proposes a syntax for EV that can be used by CSM to kepp > > electronic signature valid. > > But according to RFC-3126, ES-A is a format that reech the > same target > > than ERS in CMS. > > Yes. In some way ES-A in RFC3126 is trying to achieve the same. > With ES-A you can try to "re-sign" a signed file with a new > layer wrapped around it every time a cryptographic algorithm > gets weak (respectively before) - the concept is quite > obvious and well thought for the use case to store only a > limited number of signed documents. > > As Aleksej already described ERS also enables the possibility > for long-term non repudiation and integrity. > Second aspect of ERS is that it scales for large volumes of > signed documents. With ES-A you have to wrap around every > file another layer. > With ERS you just create new hashtrees - which is if you > think of e.g. about 10^6 to 10^9 documents a lot better > concerning performance. (especially if only e.g. a public key > algorithm gets weak or a used key length is no longer sufficient.) > > Concerning RFC3126: From my opinion it is not necessary that > ERS will obsolete ES-A. But I surely expect that many big > storage, Document Management System and ECM vendors will > implement ERS and not ES-A. So in B2B and B2C we will most > probably seeing a lot of ERS. > > The coexistence of ES-A and ERS will be something to discuss > when ERS is finally an RFC. > > Best regards > > Tobias > > > > > > > > > So my question is, if i want to archive signature, i have the choice > > between RFC3126 ES-A or ERS in CMS. Am I right ? > > > > If I am, will ES-A be obsoleted by ERS in CSM (as shown in > Appendix A in > > [ers-02]) ? > > > > But be sure that I understand ERS is more than just a way > to maintain a > > singature valid. > > > > Regards, > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > > > Envoyé : vendredi 29 avril 2005 11:48 > > > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > > Objet : RE: [ers-02.txt] Questions > > > > > > Loic > > > > > > This is what I didn't state. You have to distinguish the > > > level of the two > > > approaches. ERS deals mainly with providing syntax on (time) > > > evidence and > > > evidence on integrity of a data, while RFC3126 provides data > > > strucutre for > > > long term validity of a digital signatures. In this case RFC > > > can rely on ERS > > > for time and integrity evidence of a signature, so it is a > > > more low level > > > syntax. Or in other words, if you equip CMS with accredited > > > time, you can > > > ged basic ERS structure (of course ERS is more than that: > > > e.g. grouping and > > > hash trees). This is why I said the approaches of LTANS > vs. XAdES are > > > somehow different, while addressing similar problems. > > > > > > BR > > > > > > Aleksej > > > > > > > -----Original Message----- > > > > From: HOUSSIER Loic RD-MAPS-ISS > > > > [mailto:loic.houssier@francetelecom.com] > > > > Sent: 29. april 2005 11:24 > > > > To: A. Jerman Blazic; ietf-ltans@imc.org > > > > Subject: RE: [ers-02.txt] Questions > > > > > > > > Aleksej, > > > > Thanks for your reply. > > > > > > > > So, to demonstrate the existantce and stability of signature > > > > on particular, there will be two ways in PKIX community: > > > > One using rfc3126, one with ERS attribute within a CMS > > > > signature object. Am I wrong ? > > > > > > > > Loïc > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > > > vendredi 29 > > > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > > > ietf-ltans@imc.org > > > > > Objet : RE: [ers-02.txt] Questions > > > > > > > > > > Dear Loic > > > > > > > > > > I would be very careful here. XAdES for example is like the > > > > name says: > > > > > syntax for extended signature, which builds on top of a > > > > signature and > > > > > includes all needed complementary data to provide long term > > > > stability > > > > > of digital signatures. The LTANS position, as I understand it, > > > > > distances from such approach and deals with long term > > > stability of > > > > > data. ERS in this case defines requirements on how to > > > > demonstrate the > > > > > existence and stability of data (not signature on > > > particular) on a > > > > > timeline. It does not define the data structure nor the > > > > syntax and at > > > > > the moment you can freely use any interpretation of an > > > > evidence record > > > > > including CMS. But XAdES? I am not so sure.... > > > > > > > > > > Best regards > > > > > > > > > > Aleksej > > > > > > > > > > > -----Original Message----- > > > > > > From: owner-ietf-ltans@mail.imc.org > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > > > HOUSSIER Loic > > > > > > RD-MAPS-ISS > > > > > > Sent: 29. april 2005 10:46 > > > > > > To: ietf-ltans@imc.org > > > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > Reading ERS_02, I have question : > > > > > > It s said that ER can be part of the Archive or can be > > > stored as > > > > > > another file. What I understand is that we can (using CMS > > > > or XADES) > > > > > > do ER as part of the Archive. > > > > > > But Is it compliant with ERS ? > > > > > > > > > > > > Thanks > > > > > > > > > > > > Loïc > > > > > > > > > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > > > 21:29 À : > > > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > > > A New Internet-Draft is available from the on-line > > > > > Internet-Drafts > > > > > > > directories. > > > > > > > This draft is a work item of the Long-Term Archive and > > > > > > Notary Services > > > > > > > Working Group of the IETF. > > > > > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > > > Author(s) : R. Brandner, et al. > > > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > > > Pages : 25 > > > > > > > Date : 2005-4-8 > > > > > > > > > > > > > > In many scenarios, users need to be able to ensure and > > > > prove the > > > > > > > existence and integrity of data, especially digitally > > > > > > signed data, > > > > > > > in > > > > > > > a common and reproducible way over a long and possibly > > > > > > undetermined > > > > > > > period of time. This document specifies the syntax and > > > > > > processing > > > > > > > of > > > > > > > an Evidence Record, designed for long-term > > > > non-repudiation of > > > > > > > existence of data, which particularly can be used for > > > > > > conservation > > > > > > > of > > > > > > > evidence of digitally signed data. > > > > > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > > > message to > > > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > > > the body of > > > > > > > the message. > > > > > > > You can also visit > > > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > > > to change your subscription settings. > > > > > > > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > > > Login with the > > > > > > > username "anonymous" and a password of your e-mail > > > > address. After > > > > > > > logging in, type "cd internet-drafts" and then > > > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > > > http://www.ietf.org/shadow.html or > > > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > > > > > Send a message to: > > > > > > > mailserv@ietf.org. > > > > > > > In the body type: > > > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > > > NOTE: The mail server at ietf.org can return > the document in > > > > > > > MIME-encoded form by using the "mpack" utility. > > > > To use this > > > > > > > feature, insert the command "ENCODING mime" > > > > before the "FILE" > > > > > > > command. To decode the response(s), you will > > > > need "munpack" or > > > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > > > mail readers > > > > > > > exhibit different behavior, especially when dealing with > > > > > > > "multipart" MIME messages (i.e. documents which > > > > have been split > > > > > > > up into multiple messages), so check your local > > > > documentation on > > > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > > > mail reader > > > > > > > implementation to automatically retrieve the ASCII > > > > version of the > > > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGBS1i028017; Fri, 29 Apr 2005 09:11:28 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TGBSat028016; Fri, 29 Apr 2005 09:11:28 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mucmx01.ixos.de (mucmx01.ixos.de [149.235.31.98]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TGBPWo028004 for ; Fri, 29 Apr 2005 09:11:26 -0700 (PDT) (envelope-from tgondrom@opentext.com) Received: from samxg01.opentext.net (localhost [127.0.0.1]) by mucmx01.ixos.de (8.12.10+Sun/8.12.10) with ESMTP id j3TGBLiA017688; Fri, 29 Apr 2005 18:11:22 +0200 (MEST) Received: from MUCXGC1.opentext.net ([149.235.128.13]) by samxg01.opentext.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 09:11:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 18:11:29 +0200 Message-ID: <3C1BE8610E44734499EF92FB35F5B070CA4C8A@MUCXGC1.opentext.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmAACdYbEA== From: "Tobias Gondrom" To: "HOUSSIER Loic RD-MAPS-ISS" Cc: , "A. Jerman Blazic" X-OriginalArrivalTime: 29 Apr 2005 16:11:20.0703 (UTC) FILETIME=[14E288F0:01C54CD6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TGBQWo028011 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Loïc, Maybe to provide further info: > Well, it's more clear to me now... > ERS just proposes a syntax for EV that can be used by CSM to kepp > electronic signature valid. > But according to RFC-3126, ES-A is a format that reech the same target > than ERS in CMS. Yes. In some way ES-A in RFC3126 is trying to achieve the same. With ES-A you can try to "re-sign" a signed file with a new layer wrapped around it every time a cryptographic algorithm gets weak (respectively before) - the concept is quite obvious and well thought for the use case to store only a limited number of signed documents. As Aleksej already described ERS also enables the possibility for long-term non repudiation and integrity. Second aspect of ERS is that it scales for large volumes of signed documents. With ES-A you have to wrap around every file another layer. With ERS you just create new hashtrees - which is if you think of e.g. about 10^6 to 10^9 documents a lot better concerning performance. (especially if only e.g. a public key algorithm gets weak or a used key length is no longer sufficient.) Concerning RFC3126: From my opinion it is not necessary that ERS will obsolete ES-A. But I surely expect that many big storage, Document Management System and ECM vendors will implement ERS and not ES-A. So in B2B and B2C we will most probably seeing a lot of ERS. The coexistence of ES-A and ERS will be something to discuss when ERS is finally an RFC. Best regards Tobias > > So my question is, if i want to archive signature, i have the choice > between RFC3126 ES-A or ERS in CMS. Am I right ? > > If I am, will ES-A be obsoleted by ERS in CSM (as shown in Appendix A in > [ers-02]) ? > > But be sure that I understand ERS is more than just a way to maintain a > singature valid. > > Regards, > > Loïc > > > > > -----Message d'origine----- > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > > Envoyé : vendredi 29 avril 2005 11:48 > > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > Objet : RE: [ers-02.txt] Questions > > > > Loic > > > > This is what I didn't state. You have to distinguish the > > level of the two > > approaches. ERS deals mainly with providing syntax on (time) > > evidence and > > evidence on integrity of a data, while RFC3126 provides data > > strucutre for > > long term validity of a digital signatures. In this case RFC > > can rely on ERS > > for time and integrity evidence of a signature, so it is a > > more low level > > syntax. Or in other words, if you equip CMS with accredited > > time, you can > > ged basic ERS structure (of course ERS is more than that: > > e.g. grouping and > > hash trees). This is why I said the approaches of LTANS vs. XAdES are > > somehow different, while addressing similar problems. > > > > BR > > > > Aleksej > > > > > -----Original Message----- > > > From: HOUSSIER Loic RD-MAPS-ISS > > > [mailto:loic.houssier@francetelecom.com] > > > Sent: 29. april 2005 11:24 > > > To: A. Jerman Blazic; ietf-ltans@imc.org > > > Subject: RE: [ers-02.txt] Questions > > > > > > Aleksej, > > > Thanks for your reply. > > > > > > So, to demonstrate the existantce and stability of signature > > > on particular, there will be two ways in PKIX community: > > > One using rfc3126, one with ERS attribute within a CMS > > > signature object. Am I wrong ? > > > > > > Loïc > > > > > > > > > > > > > -----Message d'origine----- > > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > > vendredi 29 > > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > > ietf-ltans@imc.org > > > > Objet : RE: [ers-02.txt] Questions > > > > > > > > Dear Loic > > > > > > > > I would be very careful here. XAdES for example is like the > > > name says: > > > > syntax for extended signature, which builds on top of a > > > signature and > > > > includes all needed complementary data to provide long term > > > stability > > > > of digital signatures. The LTANS position, as I understand it, > > > > distances from such approach and deals with long term > > stability of > > > > data. ERS in this case defines requirements on how to > > > demonstrate the > > > > existence and stability of data (not signature on > > particular) on a > > > > timeline. It does not define the data structure nor the > > > syntax and at > > > > the moment you can freely use any interpretation of an > > > evidence record > > > > including CMS. But XAdES? I am not so sure.... > > > > > > > > Best regards > > > > > > > > Aleksej > > > > > > > > > -----Original Message----- > > > > > From: owner-ietf-ltans@mail.imc.org > > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > > HOUSSIER Loic > > > > > RD-MAPS-ISS > > > > > Sent: 29. april 2005 10:46 > > > > > To: ietf-ltans@imc.org > > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > Reading ERS_02, I have question : > > > > > It s said that ER can be part of the Archive or can be > > stored as > > > > > another file. What I understand is that we can (using CMS > > > or XADES) > > > > > do ER as part of the Archive. > > > > > But Is it compliant with ERS ? > > > > > > > > > > Thanks > > > > > > > > > > Loïc > > > > > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > > 21:29 À : > > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > A New Internet-Draft is available from the on-line > > > > Internet-Drafts > > > > > > directories. > > > > > > This draft is a work item of the Long-Term Archive and > > > > > Notary Services > > > > > > Working Group of the IETF. > > > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > > Author(s) : R. Brandner, et al. > > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > > Pages : 25 > > > > > > Date : 2005-4-8 > > > > > > > > > > > > In many scenarios, users need to be able to ensure and > > > prove the > > > > > > existence and integrity of data, especially digitally > > > > > signed data, > > > > > > in > > > > > > a common and reproducible way over a long and possibly > > > > > undetermined > > > > > > period of time. This document specifies the syntax and > > > > > processing > > > > > > of > > > > > > an Evidence Record, designed for long-term > > > non-repudiation of > > > > > > existence of data, which particularly can be used for > > > > > conservation > > > > > > of > > > > > > evidence of digitally signed data. > > > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > > message to > > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > > the body of > > > > > > the message. > > > > > > You can also visit > > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > > to change your subscription settings. > > > > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > > Login with the > > > > > > username "anonymous" and a password of your e-mail > > > address. After > > > > > > logging in, type "cd internet-drafts" and then > > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > > http://www.ietf.org/shadow.html or > > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > > > Send a message to: > > > > > > mailserv@ietf.org. > > > > > > In the body type: > > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > > > MIME-encoded form by using the "mpack" utility. > > > To use this > > > > > > feature, insert the command "ENCODING mime" > > > before the "FILE" > > > > > > command. To decode the response(s), you will > > > need "munpack" or > > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > > mail readers > > > > > > exhibit different behavior, especially when dealing with > > > > > > "multipart" MIME messages (i.e. documents which > > > have been split > > > > > > up into multiple messages), so check your local > > > documentation on > > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > > mail reader > > > > > > implementation to automatically retrieve the ASCII > > > version of the > > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TBCicG038672; Fri, 29 Apr 2005 04:12:44 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3TBCiTG038671; Fri, 29 Apr 2005 04:12:44 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3TBCdwR038627 for ; Fri, 29 Apr 2005 04:12:42 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 13:12:37 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 13:12:36 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78D10@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQAAMCDmA= From: "HOUSSIER Loic RD-MAPS-ISS" To: "A. Jerman Blazic" , X-OriginalArrivalTime: 29 Apr 2005 11:12:37.0423 (UTC) FILETIME=[59C70BF0:01C54CAC] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3TBChwR038660 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Aleksej, Well, it's more clear to me now... ERS just proposes a syntax for EV that can be used by CSM to kepp electronic signature valid. But according to RFC-3126, ES-A is a format that reech the same target than ERS in CMS. So my question is, if i want to archive signature, i have the choice between RFC3126 ES-A or ERS in CMS. Am I right ? If I am, will ES-A be obsoleted by ERS in CSM (as shown in Appendix A in [ers-02]) ? But be sure that I understand ERS is more than just a way to maintain a singature valid. Regards, Loïc > -----Message d'origine----- > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > Envoyé : vendredi 29 avril 2005 11:48 > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > Objet : RE: [ers-02.txt] Questions > > Loic > > This is what I didn't state. You have to distinguish the > level of the two > approaches. ERS deals mainly with providing syntax on (time) > evidence and > evidence on integrity of a data, while RFC3126 provides data > strucutre for > long term validity of a digital signatures. In this case RFC > can rely on ERS > for time and integrity evidence of a signature, so it is a > more low level > syntax. Or in other words, if you equip CMS with accredited > time, you can > ged basic ERS structure (of course ERS is more than that: > e.g. grouping and > hash trees). This is why I said the approaches of LTANS vs. XAdES are > somehow different, while addressing similar problems. > > BR > > Aleksej > > > -----Original Message----- > > From: HOUSSIER Loic RD-MAPS-ISS > > [mailto:loic.houssier@francetelecom.com] > > Sent: 29. april 2005 11:24 > > To: A. Jerman Blazic; ietf-ltans@imc.org > > Subject: RE: [ers-02.txt] Questions > > > > Aleksej, > > Thanks for your reply. > > > > So, to demonstrate the existantce and stability of signature > > on particular, there will be two ways in PKIX community: > > One using rfc3126, one with ERS attribute within a CMS > > signature object. Am I wrong ? > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > > vendredi 29 > > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; > ietf-ltans@imc.org > > > Objet : RE: [ers-02.txt] Questions > > > > > > Dear Loic > > > > > > I would be very careful here. XAdES for example is like the > > name says: > > > syntax for extended signature, which builds on top of a > > signature and > > > includes all needed complementary data to provide long term > > stability > > > of digital signatures. The LTANS position, as I understand it, > > > distances from such approach and deals with long term > stability of > > > data. ERS in this case defines requirements on how to > > demonstrate the > > > existence and stability of data (not signature on > particular) on a > > > timeline. It does not define the data structure nor the > > syntax and at > > > the moment you can freely use any interpretation of an > > evidence record > > > including CMS. But XAdES? I am not so sure.... > > > > > > Best regards > > > > > > Aleksej > > > > > > > -----Original Message----- > > > > From: owner-ietf-ltans@mail.imc.org > > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of > HOUSSIER Loic > > > > RD-MAPS-ISS > > > > Sent: 29. april 2005 10:46 > > > > To: ietf-ltans@imc.org > > > > Subject: [ers-02.txt] Questions > > > > > > > > > > > > Hi all, > > > > > > > > Reading ERS_02, I have question : > > > > It s said that ER can be part of the Archive or can be > stored as > > > > another file. What I understand is that we can (using CMS > > or XADES) > > > > do ER as part of the Archive. > > > > But Is it compliant with ERS ? > > > > > > > > Thanks > > > > > > > > Loïc > > > > > > > > > > > > > > > > > -----Message d'origine----- > > > > > De : owner-ietf-ltans@mail.imc.org > > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > > 21:29 À : > > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > > > A New Internet-Draft is available from the on-line > > > Internet-Drafts > > > > > directories. > > > > > This draft is a work item of the Long-Term Archive and > > > > Notary Services > > > > > Working Group of the IETF. > > > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > > Author(s) : R. Brandner, et al. > > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > > Pages : 25 > > > > > Date : 2005-4-8 > > > > > > > > > > In many scenarios, users need to be able to ensure and > > prove the > > > > > existence and integrity of data, especially digitally > > > > signed data, > > > > > in > > > > > a common and reproducible way over a long and possibly > > > > undetermined > > > > > period of time. This document specifies the syntax and > > > > processing > > > > > of > > > > > an Evidence Record, designed for long-term > > non-repudiation of > > > > > existence of data, which particularly can be used for > > > > conservation > > > > > of > > > > > evidence of digitally signed data. > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > > message to > > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > > the body of > > > > > the message. > > > > > You can also visit > > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > > to change your subscription settings. > > > > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > > Login with the > > > > > username "anonymous" and a password of your e-mail > > address. After > > > > > logging in, type "cd internet-drafts" and then > > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > > > A list of Internet-Drafts directories can be found in > > > > > http://www.ietf.org/shadow.html or > > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > > > Send a message to: > > > > > mailserv@ietf.org. > > > > > In the body type: > > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > > MIME-encoded form by using the "mpack" utility. > > To use this > > > > > feature, insert the command "ENCODING mime" > > before the "FILE" > > > > > command. To decode the response(s), you will > > need "munpack" or > > > > > a MIME-compliant mail reader. Different MIME-compliant > > > > mail readers > > > > > exhibit different behavior, especially when dealing with > > > > > "multipart" MIME messages (i.e. documents which > > have been split > > > > > up into multiple messages), so check your local > > documentation on > > > > > how to manipulate these messages. > > > > > > > > > > > > > > > Below is the data which will enable a MIME compliant > > mail reader > > > > > implementation to automatically retrieve the ASCII > > version of the > > > > > Internet-Draft. > > > > > > > > > > > > > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9fajR002339; Fri, 29 Apr 2005 02:41:36 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T9fapo002338; Fri, 29 Apr 2005 02:41:36 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from e5.ijs.si (kekec.e5.ijs.si [193.138.1.2]) by above.proper.com (8.12.11/8.12.9) with SMTP id j3T9fZKa002315 for ; Fri, 29 Apr 2005 02:41:35 -0700 (PDT) (envelope-from aljosa@e5.ijs.si) Message-Id: <200504290941.j3T9fZKa002315@above.proper.com> Received: (qmail 20253 invoked from network); 29 Apr 2005 09:41:34 -0000 Received: from localhost (127.0.0.1) by e5.ijs.si with SMTP; 29 Apr 2005 09:41:34 -0000 Received: from e5.ijs.si ([127.0.0.1]) by localhost (kekec.e5.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20126-01 for ; Fri, 29 Apr 2005 11:41:32 +0200 (CEST) Received: (qmail 20244 invoked from network); 29 Apr 2005 09:41:32 -0000 Received: from arthur.e5.ijs.si (HELO Arthur) (193.138.1.27) by e5.ijs.si with SMTP; 29 Apr 2005 09:41:32 -0000 From: "A. Jerman Blazic" To: "'HOUSSIER Loic RD-MAPS-ISS'" , Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:47:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <3418F3471F1CA4409901547349FFAE2E03B78BE4@FTRDMEL2.rd.francetelecom.fr> thread-index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsAABMvAQ X-Virus-Scanned: amavisd-new at e5.ijs.si Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T9faKa002332 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Loic This is what I didn't state. You have to distinguish the level of the two approaches. ERS deals mainly with providing syntax on (time) evidence and evidence on integrity of a data, while RFC3126 provides data strucutre for long term validity of a digital signatures. In this case RFC can rely on ERS for time and integrity evidence of a signature, so it is a more low level syntax. Or in other words, if you equip CMS with accredited time, you can ged basic ERS structure (of course ERS is more than that: e.g. grouping and hash trees). This is why I said the approaches of LTANS vs. XAdES are somehow different, while addressing similar problems. BR Aleksej > -----Original Message----- > From: HOUSSIER Loic RD-MAPS-ISS > [mailto:loic.houssier@francetelecom.com] > Sent: 29. april 2005 11:24 > To: A. Jerman Blazic; ietf-ltans@imc.org > Subject: RE: [ers-02.txt] Questions > > Aleksej, > Thanks for your reply. > > So, to demonstrate the existantce and stability of signature > on particular, there will be two ways in PKIX community: > One using rfc3126, one with ERS attribute within a CMS > signature object. Am I wrong ? > > Loïc > > > > > -----Message d'origine----- > > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] Envoyé : > vendredi 29 > > avril 2005 11:08 À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > > Objet : RE: [ers-02.txt] Questions > > > > Dear Loic > > > > I would be very careful here. XAdES for example is like the > name says: > > syntax for extended signature, which builds on top of a > signature and > > includes all needed complementary data to provide long term > stability > > of digital signatures. The LTANS position, as I understand it, > > distances from such approach and deals with long term stability of > > data. ERS in this case defines requirements on how to > demonstrate the > > existence and stability of data (not signature on particular) on a > > timeline. It does not define the data structure nor the > syntax and at > > the moment you can freely use any interpretation of an > evidence record > > including CMS. But XAdES? I am not so sure.... > > > > Best regards > > > > Aleksej > > > > > -----Original Message----- > > > From: owner-ietf-ltans@mail.imc.org > > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER Loic > > > RD-MAPS-ISS > > > Sent: 29. april 2005 10:46 > > > To: ietf-ltans@imc.org > > > Subject: [ers-02.txt] Questions > > > > > > > > > Hi all, > > > > > > Reading ERS_02, I have question : > > > It s said that ER can be part of the Archive or can be stored as > > > another file. What I understand is that we can (using CMS > or XADES) > > > do ER as part of the Archive. > > > But Is it compliant with ERS ? > > > > > > Thanks > > > > > > Loïc > > > > > > > > > > > > > -----Message d'origine----- > > > > De : owner-ietf-ltans@mail.imc.org > > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 > 21:29 À : > > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts > > > > directories. > > > > This draft is a work item of the Long-Term Archive and > > > Notary Services > > > > Working Group of the IETF. > > > > > > > > Title : Evidence Record Syntax (ERS) > > > > Author(s) : R. Brandner, et al. > > > > Filename : draft-ietf-ltans-ers-02.txt > > > > Pages : 25 > > > > Date : 2005-4-8 > > > > > > > > In many scenarios, users need to be able to ensure and > prove the > > > > existence and integrity of data, especially digitally > > > signed data, > > > > in > > > > a common and reproducible way over a long and possibly > > > undetermined > > > > period of time. This document specifies the syntax and > > > processing > > > > of > > > > an Evidence Record, designed for long-term > non-repudiation of > > > > existence of data, which particularly can be used for > > > conservation > > > > of > > > > evidence of digitally signed data. > > > > > > > > A URL for this Internet-Draft is: > > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > > > To remove yourself from the I-D Announcement list, send a > > > message to > > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > the body of > > > > the message. > > > > You can also visit > > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > > to change your subscription settings. > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > > Login with the > > > > username "anonymous" and a password of your e-mail > address. After > > > > logging in, type "cd internet-drafts" and then > > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > > > A list of Internet-Drafts directories can be found in > > > > http://www.ietf.org/shadow.html or > > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > > > Send a message to: > > > > mailserv@ietf.org. > > > > In the body type: > > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > > > NOTE: The mail server at ietf.org can return the document in > > > > MIME-encoded form by using the "mpack" utility. > To use this > > > > feature, insert the command "ENCODING mime" > before the "FILE" > > > > command. To decode the response(s), you will > need "munpack" or > > > > a MIME-compliant mail reader. Different MIME-compliant > > > mail readers > > > > exhibit different behavior, especially when dealing with > > > > "multipart" MIME messages (i.e. documents which > have been split > > > > up into multiple messages), so check your local > documentation on > > > > how to manipulate these messages. > > > > > > > > > > > > Below is the data which will enable a MIME compliant > mail reader > > > > implementation to automatically retrieve the ASCII > version of the > > > > Internet-Draft. > > > > > > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9OYwo096343; Fri, 29 Apr 2005 02:24:34 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T9OYj6096342; Fri, 29 Apr 2005 02:24:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T9OW8i096327 for ; Fri, 29 Apr 2005 02:24:33 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 11:24:30 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:24:28 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78BE4@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIAAABYXsA== From: "HOUSSIER Loic RD-MAPS-ISS" To: "A. Jerman Blazic" , X-OriginalArrivalTime: 29 Apr 2005 09:24:30.0358 (UTC) FILETIME=[3F2F7B60:01C54C9D] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T9OX8i096335 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Aleksej, Thanks for your reply. So, to demonstrate the existantce and stability of signature on particular, there will be two ways in PKIX community: One using rfc3126, one with ERS attribute within a CMS signature object. Am I wrong ? Loïc > -----Message d'origine----- > De : A. Jerman Blazic [mailto:aljosa@e5.ijs.si] > Envoyé : vendredi 29 avril 2005 11:08 > À : HOUSSIER Loic RD-MAPS-ISS; ietf-ltans@imc.org > Objet : RE: [ers-02.txt] Questions > > Dear Loic > > I would be very careful here. XAdES for example is like the name says: > syntax for extended signature, which builds on top of a signature and > includes all needed complementary data to provide long term > stability of > digital signatures. The LTANS position, as I understand it, > distances from > such approach and deals with long term stability of data. ERS > in this case > defines requirements on how to demonstrate the existence and > stability of > data (not signature on particular) on a timeline. It does not > define the > data structure nor the syntax and at the moment you can freely use any > interpretation of an evidence record including CMS. But > XAdES? I am not so > sure.... > > Best regards > > Aleksej > > > -----Original Message----- > > From: owner-ietf-ltans@mail.imc.org > > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER > > Loic RD-MAPS-ISS > > Sent: 29. april 2005 10:46 > > To: ietf-ltans@imc.org > > Subject: [ers-02.txt] Questions > > > > > > Hi all, > > > > Reading ERS_02, I have question : > > It s said that ER can be part of the Archive or can be stored > > as another file. What I understand is that we can (using CMS > > or XADES) do ER as part of the Archive. > > But Is it compliant with ERS ? > > > > Thanks > > > > Loïc > > > > > > > > > -----Message d'origine----- > > > De : owner-ietf-ltans@mail.imc.org > > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 21:29 À : > > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > > ACTION:draft-ietf-ltans-ers-02.txt > > > > > > A New Internet-Draft is available from the on-line > Internet-Drafts > > > directories. > > > This draft is a work item of the Long-Term Archive and > > Notary Services > > > Working Group of the IETF. > > > > > > Title : Evidence Record Syntax (ERS) > > > Author(s) : R. Brandner, et al. > > > Filename : draft-ietf-ltans-ers-02.txt > > > Pages : 25 > > > Date : 2005-4-8 > > > > > > In many scenarios, users need to be able to ensure and prove the > > > existence and integrity of data, especially digitally > > signed data, > > > in > > > a common and reproducible way over a long and possibly > > undetermined > > > period of time. This document specifies the syntax and > > processing > > > of > > > an Evidence Record, designed for long-term non-repudiation of > > > existence of data, which particularly can be used for > > conservation > > > of > > > evidence of digitally signed data. > > > > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > > > To remove yourself from the I-D Announcement list, send a > > message to > > > i-d-announce-request@ietf.org with the word unsubscribe in > > the body of > > > the message. > > > You can also visit > > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > to change your subscription settings. > > > > > > > > > Internet-Drafts are also available by anonymous FTP. > Login with the > > > username "anonymous" and a password of your e-mail address. After > > > logging in, type "cd internet-drafts" and then > > > "get draft-ietf-ltans-ers-02.txt". > > > > > > A list of Internet-Drafts directories can be found in > > > http://www.ietf.org/shadow.html or > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > Send a message to: > > > mailserv@ietf.org. > > > In the body type: > > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > > > NOTE: The mail server at ietf.org can return the document in > > > MIME-encoded form by using the "mpack" utility. To use this > > > feature, insert the command "ENCODING mime" before the "FILE" > > > command. To decode the response(s), you will need "munpack" or > > > a MIME-compliant mail reader. Different MIME-compliant > > mail readers > > > exhibit different behavior, especially when dealing with > > > "multipart" MIME messages (i.e. documents which have been split > > > up into multiple messages), so check your local documentation on > > > how to manipulate these messages. > > > > > > > > > Below is the data which will enable a MIME compliant mail reader > > > implementation to automatically retrieve the ASCII version of the > > > Internet-Draft. > > > > > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T92JnY086777; Fri, 29 Apr 2005 02:02:19 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T92JVH086774; Fri, 29 Apr 2005 02:02:19 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from e5.ijs.si (kekec.e5.ijs.si [193.138.1.2]) by above.proper.com (8.12.11/8.12.9) with SMTP id j3T92Gif086725 for ; Fri, 29 Apr 2005 02:02:17 -0700 (PDT) (envelope-from aljosa@e5.ijs.si) Message-Id: <200504290902.j3T92Gif086725@above.proper.com> Received: (qmail 17514 invoked from network); 29 Apr 2005 09:02:15 -0000 Received: from localhost (127.0.0.1) by e5.ijs.si with SMTP; 29 Apr 2005 09:02:15 -0000 Received: from e5.ijs.si ([127.0.0.1]) by localhost (kekec.e5.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15929-06 for ; Fri, 29 Apr 2005 11:02:13 +0200 (CEST) Received: (qmail 17507 invoked from network); 29 Apr 2005 09:02:13 -0000 Received: from arthur.e5.ijs.si (HELO Arthur) (193.138.1.27) by e5.ijs.si with SMTP; 29 Apr 2005 09:02:13 -0000 From: "A. Jerman Blazic" To: "'HOUSSIER Loic RD-MAPS-ISS'" , Subject: RE: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 11:08:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <3418F3471F1CA4409901547349FFAE2E03B78B08@FTRDMEL2.rd.francetelecom.fr> thread-index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPAAADDBIA= X-Virus-Scanned: amavisd-new at e5.ijs.si Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T92Iif086763 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Dear Loic I would be very careful here. XAdES for example is like the name says: syntax for extended signature, which builds on top of a signature and includes all needed complementary data to provide long term stability of digital signatures. The LTANS position, as I understand it, distances from such approach and deals with long term stability of data. ERS in this case defines requirements on how to demonstrate the existence and stability of data (not signature on particular) on a timeline. It does not define the data structure nor the syntax and at the moment you can freely use any interpretation of an evidence record including CMS. But XAdES? I am not so sure.... Best regards Aleksej > -----Original Message----- > From: owner-ietf-ltans@mail.imc.org > [mailto:owner-ietf-ltans@mail.imc.org] On Behalf Of HOUSSIER > Loic RD-MAPS-ISS > Sent: 29. april 2005 10:46 > To: ietf-ltans@imc.org > Subject: [ers-02.txt] Questions > > > Hi all, > > Reading ERS_02, I have question : > It s said that ER can be part of the Archive or can be stored > as another file. What I understand is that we can (using CMS > or XADES) do ER as part of the Archive. > But Is it compliant with ERS ? > > Thanks > > Loïc > > > > > -----Message d'origine----- > > De : owner-ietf-ltans@mail.imc.org > > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > > Internet-Drafts@ietf.org Envoyé : vendredi 8 avril 2005 21:29 À : > > i-d-announce@ietf.org Cc : ietf-ltans@imc.org Objet : I-D > > ACTION:draft-ietf-ltans-ers-02.txt > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > This draft is a work item of the Long-Term Archive and > Notary Services > > Working Group of the IETF. > > > > Title : Evidence Record Syntax (ERS) > > Author(s) : R. Brandner, et al. > > Filename : draft-ietf-ltans-ers-02.txt > > Pages : 25 > > Date : 2005-4-8 > > > > In many scenarios, users need to be able to ensure and prove the > > existence and integrity of data, especially digitally > signed data, > > in > > a common and reproducible way over a long and possibly > undetermined > > period of time. This document specifies the syntax and > processing > > of > > an Evidence Record, designed for long-term non-repudiation of > > existence of data, which particularly can be used for > conservation > > of > > evidence of digitally signed data. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > > > To remove yourself from the I-D Announcement list, send a > message to > > i-d-announce-request@ietf.org with the word unsubscribe in > the body of > > the message. > > You can also visit > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > > > > > > Internet-Drafts are also available by anonymous FTP. Login with the > > username "anonymous" and a password of your e-mail address. After > > logging in, type "cd internet-drafts" and then > > "get draft-ietf-ltans-ers-02.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html or > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant > mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T8kCvf079756; Fri, 29 Apr 2005 01:46:12 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3T8kCUf079755; Fri, 29 Apr 2005 01:46:12 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3T8kA2W079717 for ; Fri, 29 Apr 2005 01:46:11 -0700 (PDT) (envelope-from loic.houssier@francetelecom.com) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Apr 2005 10:46:07 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [ers-02.txt] Questions Date: Fri, 29 Apr 2005 10:46:06 +0200 Message-ID: <3418F3471F1CA4409901547349FFAE2E03B78B08@FTRDMEL2.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ers-02.txt] Questions Thread-Index: AcU8cirkQNLI0JAjS/OL6krY3bGA7AQJPDPA From: "HOUSSIER Loic RD-MAPS-ISS" To: X-OriginalArrivalTime: 29 Apr 2005 08:46:07.0710 (UTC) FILETIME=[E2B347E0:01C54C97] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j3T8kB2W079741 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Hi all, Reading ERS_02, I have question : It s said that ER can be part of the Archive or can be stored as another file. What I understand is that we can (using CMS or XADES) do ER as part of the Archive. But Is it compliant with ERS ? Thanks Loïc > -----Message d'origine----- > De : owner-ietf-ltans@mail.imc.org > [mailto:owner-ietf-ltans@mail.imc.org] De la part de > Internet-Drafts@ietf.org > Envoyé : vendredi 8 avril 2005 21:29 > À : i-d-announce@ietf.org > Cc : ietf-ltans@imc.org > Objet : I-D ACTION:draft-ietf-ltans-ers-02.txt > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Long-Term Archive and Notary > Services Working Group of the IETF. > > Title : Evidence Record Syntax (ERS) > Author(s) : R. Brandner, et al. > Filename : draft-ietf-ltans-ers-02.txt > Pages : 25 > Date : 2005-4-8 > > In many scenarios, users need to be able to ensure and prove the > existence and integrity of data, especially digitally > signed data, in > a common and reproducible way over a long and possibly > undetermined > period of time. This document specifies the syntax and > processing of > an Evidence Record, designed for long-term non-repudiation of > existence of data, which particularly can be used for > conservation of > evidence of digitally signed data. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in > the body of the message. > You can also visit > https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login > with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-ltans-ers-02.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j38JTPvZ091697; Fri, 8 Apr 2005 12:29:25 -0700 (PDT) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j38JTPts091696; Fri, 8 Apr 2005 12:29:25 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j38JTON4091689 for ; Fri, 8 Apr 2005 12:29:24 -0700 (PDT) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26828; Fri, 8 Apr 2005 15:29:22 -0400 (EDT) Message-Id: <200504081929.PAA26828@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ietf-ltans@imc.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ltans-ers-02.txt Date: Fri, 08 Apr 2005 15:29:22 -0400 Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Long-Term Archive and Notary Services Working Group of the IETF. Title : Evidence Record Syntax (ERS) Author(s) : R. Brandner, et al. Filename : draft-ietf-ltans-ers-02.txt Pages : 25 Date : 2005-4-8 In many scenarios, users need to be able to ensure and prove the existence and integrity of data, especially digitally signed data, in a common and reproducible way over a long and possibly undetermined period of time. This document specifies the syntax and processing of an Evidence Record, designed for long-term non-repudiation of existence of data, which particularly can be used for conservation of evidence of digitally signed data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ltans-ers-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ltans-ers-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-4-8155957.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ltans-ers-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ltans-ers-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-4-8155957.I-D@ietf.org> --OtherAccess-- --NextPart--