W3C home > Mailing lists > Public > www-xkms@w3.org > June 2004

Re: RSAKeyPair/RSAKeyValue issue

From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Wed, 30 Jun 2004 12:47:39 +0100
Message-ID: <40E2A85B.7000506@cs.tcd.ie>
To: tommy lindberg <lindberg_tommy@hotmail.com>
Cc: www-xkms@w3.org


Good catch Tommy,

There is also a ds:RSAKeyValue in dsig so we don't want to
reuse that element name either. I'd agree that we should
change to properly use RSAKeyPair in the spec and schema,
which is, as you point out, a substantive, though v. small,
change to the schema.

Barring objections/comments I suggest that this be treated
as a resolved issue.

There're associated changes required in the examples at the
end of section 6.4 and in C.3.1, C.3.2 and C.3.3. Those
should get caught as part of our "PR spec will contain samples
actually used in interop" approach.

Regards,
Stephen.

tommy lindberg wrote:

> 
> 
> Section 8.2.1 of Part 1 of the XKMS spec covers an element <RSAKeyPair> 
> intended
> to carry public and private parameters of an RSA key pair.
> 
> However, the adjoining schema fragment (as well as the complete XKMS 
> schema) does not define this element. Instead it defines another 
> element, <RSAKeyValue>.
> 
> RSAKeyPair appears more appropriate for the intended purpose, so I'd 
> favor a schema update, assuming this is not too late.
> 
> Regards
> Tommy
> 
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 
Received on Wednesday, 30 June 2004 07:47:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:22 GMT