dss message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [dss] Comments to the minutes of 16 December meeting.
- From: Juan Carlos Cruellas <cruellas@ac.upc.es>
- To: dss@lists.oasis-open.org
- Date: Tue, 07 Jan 2003 12:13:30 +0100
Dear Robert and all
Sorry for sending these comments so late,...
The minutes say:
2. XML security timestamping protocol (Juan Carlos Cruellas)
This document is similar to the Entrust submission discussed last week in that both deal with
timestamping protocols, though this may be expressed as OID's rather than
URN's.
Different models of timestamping use cases contained in the document may be
useful to this TC.
Well, most of the text is right, but I would suggest to change in the following
way:
2. XML security timestamping protocol (Juan Carlos Cruellas)
This document is similar to the Entrust submission discussed last week in that both deal with
timestamping protocols. Both of them use URI as a way to identify
policies. However, these policies could also be identified by OIDs.
It is commented that the TS 101903 contains a XML schema definition for an
element able to deal with both ways of identification. This element was defined
when envisaging the issue of identifying signature policies.
Different models of timestamping use cases contained in the document may be
useful to this TC.
I think that this clarifies the issue: initially both documents Entrust and the
paper by Axelle Apvrille and Vincent Girier propose to identify the Signature Policies
by use of URI. In ETSI TS 101 903, when facing this problem, we proposed a new
XML element able to also identify them by bot, URI or OID expressed as an URN....
Regards
Juan Carlos
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC