XKMS Implementation Report
This implementation report will document the interoperability of multiple
implementations of the features of XKMS
Candidate Recommendation. It will be created by the XKMS
Working Group during the Candidate Recommendation phase. A pre-CR implementation report is available.
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:
- A minimum of two complete implementations for all the REQUIRED
message processing mechanisms (Synchronous response)
- A minimum of one complete implementation for all the RECOMMENDED
and OPTIONAL message processing mechanisms (Asynchronous response,
Two-Phase protocol)
- Message syntax
- 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
- A minimum of two complete implementations for each of the following
X-KISS Services: Locate and Validate
- A minimum of two complete implementations for all the REQUIRED
elements and attributes described in X-KISS message set
- A minimum of one complete implementation for all the OPTIONAL
elements and attributes described in the X-KISS message set
- X-KRSS protocol set
- A minimum of two complete implementations for each of the following
X-KRSS services: Register, Reissue, Revoke, and Recover
- A minimum of two complete implementations for all the REQUIRED
elements and attributes described in X-KRSS message set
- A minimum of one complete implementation for all the OPTIONAL
elements and attributes described in the X-KRSS message set
- Bindings
- A minimum of two complete implementations supporting HTTP Transport
and Soap 1.2 encapsulation
- A minimum of two complete implementations supporting Exclusive
Canonicalization together with XML Signature
- 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)
- The WG will create an interoperability matrix for documenting which
implementations support which XKMS features. The matrix will ennumerate
each feature of the XKMS protocol, provide test cases and document
whether implementations satisfy those tests. The resulting matrix will
provide proof of satisfaction of the exit criteria.
- A minimum of six months (October 1, 2004) of the CR period must be
elapsed to ensure that enough time is given for providing implementation
feedback.
Copyright
© 2004 W3C® (MIT, ERCIM,
Keio), All Rights Reserved. W3C liability,
trademark,
document
use and software
licensing rules apply.
Jose Kahan, W3C Team Contact for the XKMS
Working Group
Last updated: $Date: 2004/04/05 17:21:45 $