RE: [dss] Re: TSTInfoType

["Nick Pope" <pope@secstan.com>]

Dimitry, Trevor

1) I agree to adding TSA to the TSTInfo so that it is equivalent to the RFC
3161 timestamp

2) I suggest that TSTInfo has an extension field where other information can
be added.

3) Instead of trying to extend the RFC 3161 equivalent structure to support
linked time-stamps, I suggest that this needs a different structure around
the TSTInfo.

4) I suggest that the core defines a generic structure for a time-stamp
which includes a choice between:
 - the currest TST structure providing equivalent to RFC 3161 time-stamps
 - base64 encoded RFC 3161 time-stamp
 - ANY other profile specific time-stamp structure

Nick


From: "Dimitri Andivahis" <dimitri@surety.com>
To: <dss@lists.oasis-open.org>
Date: Mon, 10 Nov 2003 18:49:18 -0500
Subject: RE: [dss] Re: TSTInfoType


I guess it's standard practice to have a catch-all element
for schema extensibility, so something like:
  <xs:element name="Extensions" type=dss:AnyType minOccurs="0"/>
is a good idea, and could be used in different ways by
different profiles.

Having said that, I would prefer <LinkingInfo> in its
own separate element of type "any"

<xs:element name="Tst">
     <xs:complexType>
       <xs:sequence>
         <xs:element name="TstInfo" type="tst:TstInfoType" />
         <xs:element name="Extensions" type=dss:AnyType minOccurs="0"/>
         <xs:element name="LinkingInfo" type=dss:AnyType minOccurs="0"/>
         <xs:element ref="ds:Signature" minOccurs="0"/>
       </xs:sequence>
     </xs:complexType>
</xs:element>

so that humans can easily see that either the <ds:Signature> or
the <LinkingInfo> element or both (if both are present)
provide a crypto-binding between the timestamped data
and the token.

Dimitri

> -----Original Message-----
> From: Trevor Perrin [mailto:trevp@trevp.net]
> Sent: Friday, November 07, 2003 6:12 PM
> To: Dimitri Andivahis; dss@lists.oasis-open.org
> Subject: RE: [dss] Re: TSTInfoType
>
>
>
>
> At 05:04 PM 11/7/2003 -0500, Dimitri Andivahis wrote:
> [...]
> >2. Proposed definition for the time stamp token <Tst>
> >
> >In place of the one in WD-04
> >   <xs:element name="Tst" type="ds:SignatureType">
> >that comes with the added requirement that a <TstInfo>
> >element MUST be included in the <Tst> element as
> >a <ds:Signature/Object> element, I propose the following:
> >
> ><xs:element name="Tst">
> >     <xs:complexType>
> >       <xs:sequence>
> >         <xs:element name="TstInfo" type="tst:TstInfoType" />
> >         <xs:element name="LinkingInfo" type=dss:AnyType minOccurs="0"/>
> >         <xs:element ref="ds:Signature" minOccurs="0"/>
> >       </xs:sequence>
> >     </xs:complexType>
> ></xs:element>
>
> Could <LinkingInfo> be renamed something more generic? (I dunno, like
> <Extensions>?).
>
> It would seem better to me if this format was generically extensible,
> without being tied to linking info.
>
>
> Trevor
>