- From: Donald E. Eastlake 3rd <dee3@torque.pothole.com>
- Date: Wed, 02 Jan 2002 09:23:58 -0500
- To: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de>
- cc: xml-encryption@w3.org, reagle@w3.org
Hi, Yes, the Nonce was moved to EncryptedData and I guess those references were missed... And I agree on the AgreementMethod Nonce :-) Unless someone objects, its name should be changed to AMNonce or the like (it's not Diffie-Hellman specific so I don't really like DHNonce). Thanks, Donald From: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de> Date: Wed, 02 Jan 2002 14:51:05 +0100 To: xml-encryption@w3.org Cc: reagle@w3.org Message-id: <665750514.1009983065@crypto> >Hi, > >in [1], section "3.3 The EncryptedData Element" tells me the existence of >the Nonce attribute being child of the EncryptedData element: > > xenc:EncryptedData/@Nonce > >Section 4.1 bullet 3.3 tells me that "The encryptor MUST specify the >nonce's length in CipherData's Nonce attribute. " which would mean: > > xenc:CipherData/@Nonce > > >I assume that these both attributes are the same and one of the both is a >typo. Which one? > >And to make this all a little more obfuscated, we even have an xenc:Nonce >ELEMENT as child of the xenc:AgreementMethod element. I would suggest to >give this element babe another name like xenc:DHNonce because an attribute >and an element with the same name doesn't look very clear. > >Christian > > > > > > > >[1] http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/ > revision 1.92 > >
Received on Wednesday, 2 January 2002 09:48:57 UTC