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

Re: Last call comments on XML Encryption specs

From: John Cowan <jcowan@reutershealth.com>
Date: Wed, 09 Jan 2002 12:42:21 -0500
Message-ID: <3C3C80FD.6070509@reutershealth.com>
To: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de>
CC: John Cowan <cowan@mercury.ccil.org>, reagle@w3.org, Martin Duerst <duerst@w3.org>, w3c-i18n-ig@w3.org, xml-encryption@w3.org
Christian Geuer-Pollmann wrote:


> If you transcode an (partially) encrypted Document, you transcode the 
> encrypted form only (the envelope). If the intended recipient decrypts 
> the encrypted Contents, he gets octets which are a UTF-8 sequence which 
> must be transcoded into the actual document encoding.

Okay.  So a transcoder must be able to notice what is and what is not
encrypted, and a decryptor must (in the general case) be able to
transcode from UTF-8.

This seems bizarre.  A partially encrypted document on this view is not
XML at all, but XML-with-interruptions: a sequence of characters,
then raw octets, then more characters.

Or are the encrypted octets themselves represented as characters
in the XML (which is then represented as octets)?

-- 
Not to perambulate             || John Cowan <jcowan@reutershealth.com>
    the corridors               || http://www.reutershealth.com
during the hours of repose     || http://www.ccil.org/~cowan
    in the boots of ascension.  \\ Sign in Austrian ski-resort hotel
Received on Wednesday, 9 January 2002 12:38:18 GMT

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