W3C home > Mailing lists > Public > public-xmlsec@w3.org > August 2011

XML Encryption 1.1 update for base64 clarity

From: <Frederick.Hirsch@nokia.com>
Date: Thu, 18 Aug 2011 14:21:36 +0000
To: <public-xmlsec@w3.org>
CC: <Frederick.Hirsch@nokia.com>, <eb2m-mrt@asahi-net.or.jp>
Message-ID: <C683CAFC-37B2-4B65-AC90-D3BD95DE6E40@nokia.com>
I have revised the XML Encryption 1.1 editors draft to clarify the note and text related to base64 encoding.

I have changed the base64 note in the algorithms section (section 5) from

*note: Note that the same URI is used to identify base64 both in "encoding" context (e.g. when needed within a CipherValue element) as well as in "transform" context (when identifying a base64 transform)


*note: The same URI is used to identify base64 both in "encoding" context (e.g. when used with the Encoding attribute of an EncryptedKey element, see section 3.1 The EncryptedType Element<file:///Materials/Builds/xmlsec2/Drafts/xmlenc-core-11/Overview.src.html#sec-EncryptedType>) as well as in "transform" context (when identifying a base64 transform for a CipherReference, see section 3.3.1 The CipherReference Element<file:///Materials/Builds/xmlsec2/Drafts/xmlenc-core-11/Overview.src.html#sec-CipherReference>).


For visibility I also added the following to the end of section 3.1:


Encoding is an optional (advisory) attribute which describes the transfer encoding of the data that has been encrypted.


(the previous MimeType paragraph outlines its use in conjunction with MimeType and gives base64 as an example)


This should resolve LC-2542

Please indicate any correction or comment on the public list.

(By the way I double checked and the original (current) XML Encryption Recommendation has the same text regarding Encoding and base64 as well as use in the transform).

regards, Frederick

Frederick Hirsch
Received on Thursday, 18 August 2011 14:22:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:26 UTC