RE: [dss] TSTInfoType

["Dimitri Andivahis" <dimitri@surety.com>]

Nick, 
My original message included descriptive text that was consistent 
with the format followed in the spec:
===
  <xs:attribute name="TSA" type="xs:anyURI" use="optional"/>

  TSA [Optional]
  This attribute SHALL identify the TSA that issued the token.
===

In the WD03 version of the spec (line 595), 
the <ds:KeyInfo> element within a <ds:Signature> identifies 
a TSA issuing tokens of type <ds:SignatureType>.  Maybe some 
additional language would be necessary there, either 
constraining the values for the TSA attribute I'm proposing 
for the <TstInfo> element (a la rfc3161), or specifying that 
it be omitted.

Dimitri

> -----Original Message-----
> From: Nick Pope [mailto:pope@secstan.com]
> Sent: Monday, October 20, 2003 3:00 PM
> To: Dimitri Andivahis; dss@lists.oasis-open.org
> Subject: RE: [dss] TSTInfoType
> 
> 
> Can you provide some descriptive text that Trevor can include in the spec?
> 
> Also, do we want to allocate a URN for the type that we are fully 
> defining.
> 
> Nick
> 
> 
> 
> > -----Original Message-----
> > From: Dimitri Andivahis [mailto:dimitri@surety.com]
> > Sent: 20 October 2003 19:45
> > To: dss@lists.oasis-open.org
> > Subject: RE: [dss] TSTInfoType
> >
> >
> > Nick,
> > I had in mind cases where the TSA uses means
> > other than simply signing the TSTInfo object.
> > For example, when the TSA uses linking methods
> > to generate the token, and the token itself
> > is not an object of type <ds:SignatureType>.
> >
> > Dimitri
> >
> > > -----Original Message-----
> > > From: Nick Pope [mailto:pope@secstan.com]
> > > Sent: Monday, October 20, 2003 2:26 PM
> > > To: Dimitri Andivahis; dss@lists.oasis-open.org
> > > Subject: RE: [dss] TSTInfoType
> > >
> > >
> > > Dimitri
> > >
> > > Can you provide some explanation of what you mean by type.  
> Do you mean
> > > whether the TSA key is certified by X.509 or managed by some
> > > other way?  If
> > > this is so in the case of an XML timestamp why can't this be 
> covered by
> > > different KeyInfo.
> > >
> > > Or do you rather mean that the TSA uses mechanisms other than simple
> > > digitally signed time-stamp info (equivalent to 3161), such as chained
> > > certificates?
> > >
> > > Nick
> > >
> > > > -----Original Message-----
> > > > From: Dimitri Andivahis [mailto:dimitri@surety.com]
> > > > Sent: 20 October 2003 18:50
> > > > To: dss@lists.oasis-open.org
> > > > Subject: [dss] TSTInfoType
> > > >
> > > >
> > > > I propose adding the following optional attribute to
> > > > the TstInfoType complex type:
> > > >
> > > >   <xs:attribute name="TSA" type="xs:anyURI" use="optional"/>
> > > >
> > > >   TSA [Optional]
> > > >   This attribute SHALL identify the TSA that issued the token.
> > > >
> > > > This will facilitate future extensions of the protocols
> > > > to TSAs using mechanisms other than X.509 certificates.
> > > >
> > > > Dimitri
> > > >
> > > >
> > > ...
> > >
> > >
> > >
> > >
> > > To unsubscribe from this mailing list (and be removed from the
> > > roster of the OASIS TC), go to
> > http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_wor
> kgroup.php.
> 
> 
> To unsubscribe from this mailing list (and be removed from the 
> roster of the
> OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_wor
kgroup.php
.





To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_workgroup.php.