- From: Joseph M. Reagle Jr. <reagle@w3.org>
- Date: Mon, 26 Mar 2001 17:44:49 -0500
- To: Blair Dillaway <blaird@microsoft.com>
- Cc: "XML Encryption WG " <xml-encryption@w3.org>
I'd like to publish the requirements ASAP. Is anyone opposed to publishing the content of [1] as a representation of the WGs "very rough consensus and intended direction." ? If so, please say so before Thursday March 29. [1] http://www.w3.org/Encryption/2001/03/21-xml-encryption-req.html ___ I've further collapsed the requirements on Encrypted Keys that were in Objects to similar text in section 2. 2.2 Now reads: http://www.w3.org/Encryption/2001/03/07-xml-encryption-req.html#sec-design-principles-scope 2. The specification must provide a mechanism for conveying encryption key information to a recipient. The structure must be flexible so as to meet a variety of application requirements including: + Carrying an encrypted key value that is encrypted to the recipient with an asymmetric or symmetric cipher. + Providing a name or URI reference to a known key It must be possible (though it is not necessary) to include key information as part of an XML encrypted data representation or referenced externally. Additionally, keys must be able to (though it is not necessary) to identify the data that they encrypt. __ Joseph Reagle Jr. http://www.w3.org/People/Reagle/ W3C Policy Analyst mailto:reagle@w3.org IETF/W3C XML-Signature Co-Chair http://www.w3.org/Signature W3C XML Encryption Chair http://www.w3.org/Encryption/2001/
Received on Monday, 26 March 2001 17:57:48 UTC