W3C home > Mailing lists > Public > xml-encryption@w3.org > January 2002

Re: xenc:EncryptedKey/@Type

From: Joseph Reagle <reagle@w3.org>
Date: Tue, 15 Jan 2002 15:44:06 -0500
Message-Id: <200201152044.PAA06251@tux.w3.org>
To: "Takeshi Imamura" <IMAMU@jp.ibm.com>
Cc: Blair Dillaway <blaird@microsoft.com>, xml-encryption@w3.org
On Tuesday 15 January 2002 02:45, Takeshi Imamura wrote:
> I believe the spec does not have to care whether the resulting octets is
> a literal key or not.  As Blair illustrated in [1], the key may be
> encoded in a structure.  That is because the key should be processed not
> by the implementation of the spec but by that of the algorithm for the
> key, optionally by consulting the Type attribute of the EncryptedKey
> element.
> [1] http://lists.w3.org/Archives/Public/xml-encryption/2002Jan/0075.htmle

Ok, sounds good. I've tweaked 3.4.1 to have the following two sentences now:

"When EncryptedKey is decrypted the resulting octets are made available to 
the EncryptionMethod algorithm without any additional processing."

"The Type attribute inheritted from EncryptedType can be used to further 
specify the type of the encrypted key if the EncryptionMethod Algorithm 
does not define a unambigous encoding/representation. (Note, all the 
algorithms in this specifications have an unambigous representation for 
their associated key structures.)"


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 Tuesday, 15 January 2002 15:44:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:13:07 UTC