W3C home > Mailing lists > Public > www-xkms@w3.org > July 2003

Communication to other groups

From: Hallam-Baker, Phillip <pbaker@verisign.com>
Date: Wed, 23 Jul 2003 10:36:50 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E8A92C6@mou1wnexm02.verisign.com>
To: "Www-Xkms (E-mail)" <www-xkms@w3.org>

The following issues need to be communicated to other groups. We cannot fix
them in the XKMS spec because of the rules on normative references. The
solution in both cases is simply to specify a URI for the protocol.



Issue 302 - To be addressed in DSS spec

The issue concerns the use of delgated signatures. Is this a different
cryptographic key usage? I don't see this as being the case, the key storage
is irrelevant to the external applications in most cases. If the key storage
is relevant then it would seem to be a protocol issue.
This would appear to suggest that the correct approach is to address this
issue through the UseKeyWith mechanism as suggested. This leaves open the
issue of where the corresponding URI is defined. In this case it would
appear that this is an issue for the DSS protocol WG since it is not at the
appropriate standards status level for a normative reverence from XKMS.
Issue 303 - Denis 24. 
The text under [180] identifies various protocols. To this list, XAdE>S 

(XML Advanced Electronic Signature) which is a W3C Note issued on Februar>y 

20, 2003 should be added (see:   <http://www.w3.org/TR/XAdES/>
http://www.w3.org/TR/XAdES/). The 

"identifier" type is such a case is a SigningCertificate element, i.e.

a DN.

This is a status issue. A standard should not make a normative reference to
a note. However the XKMS group can request that the group in question amend
their draft to specify a URI to be employed in conjunction with

In addition a note to state the default rules for constructing identifiers.

Resolution - Communicate issue to the group. Editorial
Received on Wednesday, 23 July 2003 13:36:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:41 UTC