RE: QUESTIONS ?
"Apvrille, Axelle" <[email protected]> Wed, 17 Jul 2002 08:36:11 +0100
| Newsgroups | gmane.ietf.xmldsig |
|---|---|
| Message-ID | <182AA61AC50CD4118E8400805F0DF6290261ECEF@tou-msg01.europe.stortek.com> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C22D64.9F66F720 Content-Type: text/plain; charset="iso-8859-1" > > 2-Where is the time-stamp "horodatage" ,it exist? > > I've got the same question - how to include, in a standard > way, a time > stamp in the CMS format? As a SignatureProperty, or what? > Actually, timestamping is outside the scope of XML Signatures. It suggests timestamps will be set in the signature properties in an example, but that's "all". As others have already answered, you should have a look at ETSI's XML Advanced Electronic Signatures. XAdES defines XML signatures for documents that are meant to be kept over years. Their special format XAdES-T talks about time stamping. In that format, signer is requested to mention time stamping date (SigningTime) and may add an external time stamp (retrieved from a proper time stamping authority). The problem if you do so is that, currently, the time stamp is an ASN.1 dump (Base64 encoded) of structures defined in RFC 3161. So you fall again into ASN.1... >Or > maybe there > is some XML time-stamp specification? Consequently, we're working on one currently. It should be an "all" XML timestamping protocol, using XML Signatures to secure the time stamp token. A paper's to appear at ISSE'02 (www.isse.org) conference in October. Regards, --------------------- Axelle APVRILLE - mailto: [email protected] Storage Technology European Operations Toulouse Research and Development Center ------_=_NextPart_001_01C22D64.9F66F720 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>RE: QUESTIONS ?</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>> > 2-Where is the time-stamp = "horodatage" ,it exist?</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> I've got the same question - how to include, in = a standard </FONT> <BR><FONT SIZE=3D2>> way, a time </FONT> <BR><FONT SIZE=3D2>> stamp in the CMS format? As a = SignatureProperty, or what? </FONT> <BR><FONT SIZE=3D2>> </FONT> </P> <P><FONT SIZE=3D2>Actually, timestamping is outside the scope of XML = Signatures.</FONT> <BR><FONT SIZE=3D2>It suggests timestamps will be set in the signature = properties in an example, but that's "all".</FONT> <BR><FONT SIZE=3D2>As others have already answered, you should have a = look at ETSI's XML Advanced Electronic Signatures. XAdES defines XML = signatures for documents that are meant to be kept over years. Their = special format XAdES-T talks about time stamping. In that format, = signer is requested to mention time stamping date (SigningTime) and may = add an external time stamp (retrieved from a proper time stamping = authority). The problem if you do so is that, currently, the time stamp = is an ASN.1 dump (Base64 encoded) of structures defined in RFC 3161. So = you fall again into ASN.1...</FONT></P> <P><FONT SIZE=3D2>>Or </FONT> <BR><FONT SIZE=3D2>> maybe there </FONT> <BR><FONT SIZE=3D2>> is some XML time-stamp specification?</FONT> </P> <P><FONT SIZE=3D2>Consequently, we're working on one currently. It = should be an "all" XML timestamping protocol, using XML = Signatures to secure the time stamp token.</FONT></P> <P><FONT SIZE=3D2>A paper's to appear at ISSE'02 (www.isse.org) = conference in October.</FONT> </P> <P><FONT SIZE=3D2>Regards, </FONT> <BR><FONT SIZE=3D2>---------------------</FONT> <BR><FONT SIZE=3D2>Axelle APVRILLE - mailto: = [email protected]</FONT> <BR><FONT SIZE=3D2>Storage Technology European Operations </FONT> <BR><FONT SIZE=3D2>Toulouse Research and Development Center</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C22D64.9F66F720--