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

FW: Additional fixes

From: Hallam-Baker, Phillip <pbaker@verisign.com>
Date: Wed, 23 Jul 2003 12:00:31 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D233F@mou1wnexm02.verisign.com>
To: "Www-Xkms (E-mail)" <www-xkms@w3.org>
The following have also been fixed: 

 305 Joseph Reagle

Document doesn't flow as smoothly as it might: 

1.	Section 1 says there are two "service specifications" but doesn't
say where they are more fully described or specified. Forward references? 

2.	The sections in section 1.7 do not correspond to the sections of the
table of contents. 

3.	Section 1.5 has the same title as Section 4 (except that it has
"specification"). How to make this flow better, or at least use the term (r
not) "specification" consistently. 

4.	Generally, I don't distinguish between a "message format" and a
"message syntax." What do these section do differently? 

309 Yasir Khan

1.	In section 2.5.2 it is described:
..........
Service generation of the Pending Response Message RequestID is set to the
value of Id in the Pending request message Nonce is not present ResponseID
is set to a randomly generated unique value 
..........
  

2.	Corresponding example the values are not given correctly: In 2.5.3.5
Response the value of RequestId should be
"#I4294d3993de300c1ef54d49bd0903b2d" according to the specification. 

3.	Clarify use of "#" before the Id values in XKMS Response  

Fixed 1 & 2.  3 appears to be related to Chopra's issue 11 for discussion.
 
 
308 fixed
 
 
This leaves the following to be fixed in the code
 
1)     Extract the private keys corresponding to the certs from the cert
store
2)     Use the Exclusive C14N for the signature.
Received on Wednesday, 23 July 2003 15:00:33 GMT

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