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

Re: 5.1.1 Table of Algorithms in Encryption 1.1 ( LC-2542)

From: <frederick.hirsch@nokia.com>
Date: Fri, 19 Aug 2011 13:35:05 +0000
To: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
Cc: public-xmlsec@w3.org
Message-Id: <E1QuPE1-0002Xe-EF@jessica.w3.org>

 Dear MURATA Makoto ,

The XML Security Working Group has reviewed the comments you sent [1] on
the Last Call Working Draft [2] of the XML Encryption Syntax and Processing
Version 1.1 published on 13 May 2010. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-xmlsec@w3.org if you agree with it or not before 26 August 2011. In
case of disagreement, you are requested to provide a specific solution for
or a path to a consensus with the Working Group. If such a consensus cannot
be achieved, you will be given the opportunity to raise a formal objection
which will then be reviewed by the Director during the transition of this
document to the next stage in the W3C Recommendation Track.

Thanks,

For the XML Security Working Group,
Thomas Roessler
W3C Staff Contact

 1.
http://www.w3.org/mid/CALvn5ECb9p65xvXf2o+2phoYAX72R0CtdbJsnWg_f2pFPst=CQ@mail.gmail.com
 2. http://www.w3.org/TR/2010/WD-xmlenc-core1-20100513/


=====

Your comment on 5.1.1 Table of Algorithms The table below lists the
categor...:
> I do not understand the 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)."
> 
> 
> in XML Encryption 1.1.
> 
> The CipherValue element does not have the Algorithm attribute.
> Why can the URI http://www.w3.org/2000/09/xmldsig#base64
> be used for encoding?


Working Group Resolution (LC-2542):
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)
]]

to

[[
*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>).
]]

http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core-11/Overview.html#base64note

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)

http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core-11/Overview.html#sec-EncryptedType

see http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0066.html

----
Received on Friday, 19 August 2011 13:35:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:16 UTC