W3C home > Mailing lists > Public > xml-encryption@w3.org > April 2001

Re: Latest Rough Draft

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Mon, 16 Apr 2001 19:06:18 +0900
To: "Joseph M. Reagle Jr." <reagle@w3.org>
Cc: "XML Encryption WG " <xml-encryption@w3.org>
Message-ID: <OFF0270540.86604424-ON49256A30.002B76E8@LocalDomain>


Joseph,

I have some comments on [1]:

2.1.3 Super-Encryption: Encrypting EncryptedData

>A valid super-encryption of //EncryptedData/@Id='ED1' would be:
This XPath would be "//EncryptedData[@Id='ED1']".


3.2 The CipherData Element

>       <choice>
>         <element ref="ds:Transforms" minOccurs="0"/>
>       </choice>
Why <choice> is used here?


3.4 Extensions to enc:KeyInfo Element

>1. The EncryptedData or EncryptedKey element specifies the associated key material:
The key value may be indicated by specifying the X509Data element for the
corresponding public key.


>            <element name="EncryptedKey" minOccurs='0'/>
The EncryptedKey element may occur zero or more times within a KeyInfo element, so this would be:
<element ref='enc:EncryptedKey' minOccurs='0' maxOccurs='unbounded'/>


3.4.2 The KeyRetrievalMethod Element

>The KeyRetrievalMethod element provides a way to express a link from an EncryptedData element to the EncryptedKey element containing the key used
needed to decrypt it.
Does this mean the KeyRetrievalMethod element must not occur within the
KeyInfo element of an EncryptedKey element?


4.1 Encryption

>2. If the data being encrypted is an external octet sequence, create an EncryptedData structure referencing the encrypted data ...
The EncryptedData structure may contain the encrypted data.

[1] http://www.w3.org/Encryption/2001/04/06-proposal.html

Thanks,
Takeshi IMAMURA
Tokyo Research Laboratory
IBM Research
imamu@jp.ibm.com



From: "Joseph M. Reagle Jr." <reagle@w3.org>@w3.org on 2001/04/10 07:57 AM

Please respond to "Joseph M. Reagle Jr." <reagle@w3.org>

Sent by:  xml-encryption-request@w3.org


To:   "XML Encryption WG " <xml-encryption@w3.org>
cc:
Subject:  Latest Rough Draft




I'm sure it has many errors, and clumsy feet, but hopefully a few steps in
the right direction.
         http://www.w3.org/Encryption/2001/04/06-proposal.html

__
Joseph Reagle Jr.                 http://www.w3.org/People/Reagle/
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/Signature
W3C XML Encryption Chair          http://www.w3.org/Encryption/2001/
Received on Monday, 16 April 2001 06:06:35 GMT

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