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

Re: xenc:EncryptedKey/@Type

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Wed, 16 Jan 2002 14:24:30 +0900
To: reagle@w3.org
Cc: Blair Dillaway <blaird@microsoft.com>, xml-encryption@w3.org
Message-ID: <OF37C85568.C4B8B77E-ON49256B43.001D403B@LocalDomain>


>> 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.)"

These look good to me.  I don't see any problem.

Thanks,
Takeshi IMAMURA
Tokyo Research Laboratory
IBM Research
imamu@jp.ibm.com
Received on Wednesday, 16 January 2002 00:24:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:20 GMT