W3C home > Mailing lists > Public > xml-encryption@w3.org > August 2000

Re: Encrypted Node URI and NodeType

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Thu, 31 Aug 2000 11:02:50 +0900
To: "Joseph M. Reagle Jr." <reagle@w3.org>
cc: Ed Simon <ed.simon@entrust.com>, "Public XML Encryption List" <xml-encryption@w3.org>
Message-ID: <4925694C.000B6197.00@d22mta13.yamato.ibm.com>



Joseph,

Ed's proposal also targets a whole attribute (i.e., name and value pair) and
only a value of an attribute.  How does your idea work for them?

Thanks,
Takeshi IMAMURA
Tokyo Research Laboratory
IBM Japan, Ltd.
E-mail: imamu@jp.ibm.com



From: "Joseph M. Reagle Jr." <reagle@w3.org> on 2000/08/31 02:25 AM

To:   Ed Simon <ed.simon@entrust.com>
cc:   "Public XML Encryption List" <xml-encryption@w3.org>, swick@w3.org, Dan
      Connolly <connolly@w3.org> (bcc: Takeshi Imamura/Japan/IBM)
Subject:  Encrypted Node URI and NodeType




Ed,

As stated after the Crypto BoF, in your proposal [1] I recommend you break
up your NodeType into a location (location of the EncryptedNode's encrypted
serialization -- if not present in the element content) and NodeType (the
URIs of the Information Set item provided by [2]). Instead of

<EncryptedNode xmlns="http://www.w3.org/2001/03/Encryption"
    NodeType="."  <!-- "." indicates the <EncryptedNode> element is right
                         where the original unencrypted element was -->
    EncryptionInfo="#encryptionInfo23">
    (Base64 of encrypted Element node)
</EncryptedNode>

this:

<EncryptedNode xmlns="http://www.w3.org/2001/03/Encryption"
    Location="."
    InformationSetItem="http://www.w3.org/2000/07/infoset#Element"
    EncryptionInfo="#encryptionInfo23">
    (Base64 of encrypted Element node)
</EncryptedNode>

Futhermore, if Location is intended to be a URI the "." hack/syntax for the
present node will probably be problematic. I'm presently scratching my head
about the best structure/relation of these things to each other (describing
Information Set Items/Nodes in the context of a serialized Information Set
Items/Nodes where both instances have a relationship to each other...)
Hopefully I'll post more within the week.

[1]
http://lists.w3.org/Archives/Public/xml-encryption/2000Aug/att-0001/01-xmlenc
overview.html
[2] http://www.w3.org/TR/2000/WD-xml-infoset-20000726

_________________________________________________________
Joseph Reagle Jr.
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Wednesday, 30 August 2000 22:03:08 GMT

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