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

Re: Nonce Handling

From: Donald E. Eastlake 3rd <dee3@torque.pothole.com>
Date: Tue, 06 Nov 2001 08:37:00 -0500
Message-Id: <200111061337.IAA0000092875@torque.pothole.com>
To: "Dournaee, Blake" <bdournaee@rsasecurity.com>
cc: XML Encryption WG <xml-encryption@w3.org>
I think the Schema is left over from when the actual nonce value was
present in the attribute. It should probably be of type "integer". And,
yes, the nonce needs to be prepended to the plaintext.


From:  "Dournaee, Blake" <bdournaee@rsasecurity.com>
Message-ID:  <E7B6CB80230AD31185AD0008C7EBC4D202A1B67D@exrsa01.rsa.com>
To:  XML Encryption WG <xml-encryption@w3.org>
Date:  Sun, 4 Nov 2001 17:09:05 -0800 

>Hello All,
>I am still unclear on how the nonce value is dealt with in <CipherData>. The
>schema definition says that the attribute value is supposed to be Base-64
>encoded binary value, but there is no mention of the actual value itself. Is
>it just an integer length of the nonce? If so, why even bother with encoding
>Also, this sentence is confusing (Section 3.2):
>"The optional Nonce attribute specifies the presence and length of a nonce
>value that is prepended to the CipherValue or data identified by the
>This isn't exactly correct - the nonce is prepended to the plain-text, not
>the cipher text, correct? (Maybe I am wrong.)
>Blake Dournaee
>Toolkit Applications Engineer
>RSA Security
>"The only thing I know is that I know nothing" - Socrates
Received on Tuesday, 6 November 2001 08:39:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:13:05 UTC