- From: Jose Kahan <jose.kahan@w3.org>
- Date: Wed, 22 Jun 2005 15:15:34 +0200
- To: www-xkms@w3.org
- Message-ID: <20050622131534.GA10122@rakahanga.inrialpes.fr>
Hi folks, In preparation for the XKMS press release, could you help check for accuracy and complete my answers to the following questions? Many thanks! -jose > To what extent does XMLS 2.0 fulfill the charter requirements, stated > here: http://www.w3.org/2001/XKMS/2001/01/xkms-charter.html#_Mission I think that we fulfill all of those requirements. > What makes XKMS 2.0 different from 1.0? Are there any new features? I think that XKMS 1.0 was the original XKMS submission. I can try to go thru the submission and make a list of changes. If you have a quick answer at hand, it would be gladly accepted. Are there any practical application examples of XMLS 2.0 that I can cite > in plain language for the reporter? The only one I've in mind is motivate the creation of local PKI networks. Traditionally, the common PKI operations (public key certificate management, localization, parsing, and validation operations) are difficult to integrate into existing applications because they add overhead and must be hard-coded for a given PKI. An XKMS contribution to PKI deployment is to delegate those operations to a server by means of low overhead protocols, while being open enough to be able to be used with any public certificate certificate format. To make an application PKI aware in XKMS, one needs only to implement the XKMS protocols that are interesting to that application. All decisions as to the type of public key certificate format, revocation, and so on can be handled directly at the server and transparently to the applications themselves. This will help not only third parties provide PKI operations in an interoperable way, but will also allow companies to install their own XKMS servers for applications pertaining to local intranets.
Received on Wednesday, 22 June 2005 13:15:42 UTC