Edit comment LC-2387 for XML Security Working Group

Quick access to

Previous: LC-2420 Next: LC-2543

Comment LC-2387
Commenter: Taki Kamiya <tkamiya@us.fujitsu.com> on behalf of EXI Working Group

Resolution status:

Section 4.2 "Well-known Type parameter values" defines a reserved value for EXI. It also states that: "Encryptors and Decryptors should handle unknown or empty Type attribute values as a signal that the cleartext is to be handled as an opaque octet-stream, whose specific processing is up to the invoking application. In this case, the
Type, MimeType and Encoding parameters should be treated as opaque data whose appropriate processing is up to the application."

It is not clear to me what is expected of a processor that does not implement EXI have encountered Type value of "http://www.w3.org/2009/xmlenc11#EXI". Since the value "http://www.w3.org/2009/xmlenc11#EXI" is well-known, the quoted paragraph does not seem to apply to the value.

When I think that the encryption of EXI stream as a whole is covered by section 2.1.4, I start to wonder what the mention of EXI in section 4.2 would add beyond that in terms of function. It appears as though the two mechanisms are functionally same with regards to how they relate to EXI, since both provide ways to encrypt and contain EXI streams within XML.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 2387.html,v 1.1 2017/08/11 06:45:29 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org