Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-P1619] Fwd: IEEE Security in Storage Working Group: Questions regarding P1619-D19



Hi Folks,

I can request editorial changes, but I need a concise list of all the changes required.  For now, I've created an FAQ as a copy of this thread (see https://siswg.net/index.php?option=com_content&task=view&id=38&Itemid=73).

Is there anyone who could create such a list?  We'll need this soon, otherwise we'll miss the NIST XTS submission window.

Thanks!
-Matt

On Wed, Apr 30, 2008 at 1:05 PM, Landon Curt Noll <p1619.0-mail@asthe.com> wrote:
On 2008-Apr-30, at 11:47, Joachim Schneider wrote:

.Q: " In the formula: Cq 1 XTS-AES-blockEnc(Key, Pj, i, q)  Pj can be replaced by Pq, correct?"

A: I think you're right. Any C(q) would be derived from a P(q) and the tweak. I think j is a typo and should be replaced with q as j is a loop invariant. Same goes for the decryption formula on page 7.

Do we need to amend the published draft to fix this typo?  If we do, then some additional explanatory text around this question:

Q: "-In line 30 and 31 page 3 there is statement says that the size of a data-unit is 2^128-2 128 bit block. On the next sentence it says that the size of the data-unit is 2^20 128 bit block. This seems to be a contradiction."

A: I think the key is in the words preceding the numbers - namely "shall not" (meaning may not without grave consequences) and "should not" which isn't quite as restrictive. No contradiction there

should be added as I have seen that same question raised by more than one person.

chongo () /\oo/\




--
Thanks!
Matt Ball, IEEE P1619.x SISWG Chair
M.V. Ball Technical Consulting, Inc.
Phone: 303-469-2469, Cell: 303-717-2717
http://www.mvballtech.com
http://www.linkedin.com/in/matthewvball