The following are some proposed wording changes. In our opinion, these would make the document easier to follow and understand.
Page iv: Annex C should be marked as "informative" (it is not normative)
Page 6: Add "data unit size" to the glossary. Proposed wording:
3.2.3 data unit size: The size of a unit of data to be processed as one piece (e.g. a sector). Typical sizes might include 512 bytes, 520 bytes, 528 bytes, and 4096 bytes.
Page 7: Change "i is a 128-bit tweak" to "i is a 128-bit tweak value"
Page 9: Same change. "i is a 128-bit tweak" to "i is a 128-bit tweak value"
Page 8: Change 4.2.2 title from "More Than 128 Bits" to "128 Bits Or More"
Page 10: Change 4.3.2 title from "More Than 128 Bits" to "128 Bits Or More"
(To be consistent with the next sentence)
Page 8 and 10. Sections 4.2.2 and 4.3.2 add a sentence to indicate this is optional, proposed wording:
Replace "The LRW-AES" with
"Implementations are not required to support data unit sizes that are not multiples of 128 bits. For those that choose to support such sizes, the LRW-AES"
The term "logical" in "logical position" adds nothing and suggests that physical position is incorrect. Recommend that "logical" be stricken from all occurrences, and "position" left open to the implementor. In particular, this recommends the following changes:
Page 2, Introduction: change "logical position" to "position"
Page 6, 3.2.5: change "logical position" to "position"
Page 7, 4.2.1: change "representing logical position" to "representing the position"
Page 8, 4.2.2: change "representing logical position" to "representing the position"
Page 9, 4.3.1: change "representing logical position" to "representing the position"
Page 10, 4.3.2: change "representing logical position" to "representing the position"
Page 12, 5.2: change "logical position" to "position"
Page 14, Table 5: change "logical block addres 0" to "block address 0"
Page 16, XML example: change "a logical single key" to "a single key"
… Garry McCracken / Rob Ewan
