Congratulations to everyone. Thanks to the hardwork of everyone we have
just now gone CR. Thanks Jose for all the help.
Now we need for folks to send in more test cases and work towards interop.
Cheers
Shivaram & Stephen
_____________________________________________________________________
Shivaram H. Mysore <shivaram.mysore@sun.com>
JavaSoft, Sun Microsystems Inc. Co-Chair, W3C's XKMS WG
http://www.w3.org/2001/XKMS
Direct: (408)276-7524
Fax: (408)276-7674
_____________________________________________________________________
Forwarded message 1
Dear Advisory Committee Representative,
W3C is pleased to announce the following W3C Candidate Recommendations:
XML Key Management Specification (XKMS)
http://www.w3.org/TR/2004/CR-xkms2-20040405/
and
XML Key Management Specification (XKMS) Bindings
http://www.w3.org/TR/2004/CR-xkms2-bindings-20040405/
The XKMS Working Group requested Candidate Recommendation status on 08 January 2003:
http://lists.w3.org/Archives/Member/chairs/2004JanMar/0000.html
The request summarizes the outcome of the Last Call review, which confirmed that
the specification meets the charter and requirements. The XKMS Working Group
made no substantive changes to the documents as a result of Last Call comments.
The Working Group has resolved and responded to all comments received during
the Last Call review. See the Disposition of Comments:
http://www.w3.org/2001/XKMS/Drafts/last-call-issues/issues.html
Proposed Recommendation Entrance Criteria
-----------------------------------------
In order to exit the Candidate Recommendation phase, the following criteria
must be satisfied:
* Message processing mechanisms
For each of the services defined by X-KISS and X-KRSS:
o A minimum of two complete implementations for all the
REQUIRED message processing mechanisms (Synchronous response)
o A minimum of one complete implementation for all the
RECOMMENDED and OPTIONAL message processing mechanisms
(Asynchronous response, Two-Phase protocol)
* Message syntax
o For each of the supported message processing mechanisms, a
minimum of two complete implementations for all the REQUIRED
and OPTIONAL elements and attributes defined in Section 3 for
the Request and Response messages as well as for the Compound
and Status requests (i.e, if an implementation doesn't
support Asynchronous processing of messages, it doesn't need
to support the Status request elements either, but it does
have to return a Result code such as Receiver.Refused)
* X-KISS protocol set
o A minimum of two complete implementations for each of the
following X-KISS Services: Locate and Validate
o A minimum of two complete implementations for all the
REQUIRED elements and attributes described in X-KISS message
set
o A minimum of one complete implementation for all the OPTIONAL
elements and attributes described in the X-KISS message set
* X-KRSS protocol set
o A minimum of two complete implementations for each of the
following X-KRSS services: Register, Reissue, Revoke, and
Recover
o A minimum of two complete implementations for all the
REQUIRED elements and attributes described in X-KRSS message
set
o A minimum of one complete implementation for all the OPTIONAL
elements and attributes described in the X-KRSS message set
* Bindings
o A minimum of two complete implementations supporting HTTP
Transport and Soap 1.2 encapsulation
o A minimum of two complete implementations supporting
Exclusive Canonicalization together with XML Signature
o A minimum of one complete implementation supporting of each
of the following security enhancements: Payload
Authentication (levels I and II), TLS Bindings (levels I-III)
* Interoperability Matrix
o The WG will create an interoperability matrix with test cases
and document how implementations satisfy those tests. The
role of this matrix will be to enumerate each feature of the
XKMS protocol and specify which features exist in which
implementations and whether interoperability has been
demonstrated or not, as proof that we are satisfying the exit
criteria.
A test suite for these specifications will be created during the CR period.
The implementation report is available at:
http://www.w3.org/2001/XKMS/xkms-implementations/
Status of Patent Issues
-----------------------
We know of no new Patent issues specifically relating to XKMS and XKMS Binding.
Patent disclosures relevant to these specifications can be found on the Working
Group's patent disclosure page at:
http://www.w3.org/2001/XKMS/Disclosures.html
From "Status of This Document"
------------------------------
Quoting From the Specifications
-------------------------------
XML Key Management Specification (XKMS 2.0)
Version 2.0
W3C Candidate Recommendation 05 April 2004
This version:
http://www.w3.org/TR/2004/CR-xkms2-20040405/
Latest version:
http://www.w3.org/TR/xkms2/
Previous version:
http://www.w3.org/TR/2002/WD-xkms2-20020318
Editor:
Phillip Hallam-Baker VeriSign
Abstract
This document specifies protocols for distributing and registering public keys,
suitable for use in conjunction with the W3C Recommendations for XML Signature
[XML-SIG] and XML Encryption [XML-Enc]. The XML Key Management Specification
(XKMS) comprises two parts — the XML Key Information Service Specification
(X-KISS) and the XML Key Registration Service Specification (X-KRSS).
------------------------------------------
XML Key Management Specification (XKMS 2.0) Bindings
W3C Candidate Recommendation 05 April 2004
This version:
http://www.w3.org/TR/2004/CR-xkms2-bindings-20040405/
Latest version:
http://www.w3.org/TR/xkms2-bindings/
Previous version:
http://www.w3.org/TR/2002/WD-xkms2-20020318/
Editor:
Phillip Hallam-Baker VeriSign
Abstract
This document specifies protocol bindings with security characteristics for the
XML Key Management Specification (XKMS).
What Candidate Recommendation Means
-----------------------------------
Excerpted from the W3C Process Document section 7.11:
"A Candidate Recommendation is a document that W3C believes has
been widely reviewed and satisfies the Working Group's technical
requirements. W3C publishes a Candidate Recommendation to gather
implementation experience."
http://www.w3.org/2004/02/Process-20040205/tr.html#RecsCR
For Tim Berners-Lee, W3C Director; and
Daniel Weitzner, Technology & Society Domain Leader; and
Jose Kahan, XML Key Management Activity Lead;
Ivan Herman, W3C Communications Team
--
Ivan Herman
W3C Head of Offices
C/o W3C Benelux Office at CWI, Kruislaan 413
1098SJ Amsterdam, The Netherlands
tel: +31-20-5924163; mobile: +31-641044153;
URL: http://www.w3.org/People/all?pictures=yes#ivan