XML Key Management Services WG

Last revised by $Author: smysore $ $Date: 2003/12/18 17:28:24 $

Participants

Close the Last Call open issue - Blair has sent the example for this to PHB, is the Spec updated?
WG Consensus on exit criteria/features at risk
Xades paragraph - Confirm that this is resolved
Id vs ID - When will this be fixed?
XKMS and SOAP Message Security tokens - Frederick Hirsch
Fix missing link in spec- PHB
AOB

F. Hirsch: How the key is conveyed in WSS header is the main issue. XKMS should be made usable in this context. If KeyInfo is sent to the server which includes a SecruityToken reference, then how can this be done. WS-I is profiling work on WSS where they are saying just include WS-I SecurityToken reference in WSS. XKMS does only Public Key, so at this time, answer to questions

Client of XKMS code must do the necessary translation to present it to the XKMS Server
2nd point is moot because of the answer to the first one.
Frederick also sent this resolution to the list

Should there be request to W3C to include support for extending XML DSig - specifically KeyInfo. Jose answered stating that W3C is working on addressing this issue.
AI: PHB editorial fix the missing links in schema
AI: PHB editorial fix on id vs ID
AI: PHB create an errata between the last release and this new version created so that it is easier for developers implementing
AI: PHB to include text regarding Xades from Stephen
AI: PHB to fix the spec regarding the Open Issue
AI: Jose to create a xkms-editor mailing list which includes PHB + www-xkms email ids.
Poll: Anyone objects to the exisitng "Exit Criteria" - concensus - everyone agreed that the exit criteria is reasonable. If anyone has any objection, they will have to post a message to the list by December 19, 2003. If there are no objections on the list, then the issue shall be considered closed and exit criteria is frozen.
AI: Jose to propose on the list issue on use of hashes - RDF ??
Entrust will plan to release a public version of the XKMS client.
AI: Shivaram, Stephen, Jose: Update Specs with fixes for PHB's AI and upload to web site - soon.
6 months for the implementation period. If we finish earlier, we can close earlier.