ADI - Suggested checksum text for ADT
Erich R. Oetting
oettier at stamps.stortek.com
Tue Feb 25 12:19:54 PST 2003
* From the T10 Reflector (t10 at t10.org), posted by:
* "Erich R. Oetting" <oettier at stamps.stortek.com>
>From what I understand, ADT needs a checksum mostly to catch gross errors. The
transport layer should be fairly robust. A simple bitwise parity over the
entire frame should do the job. It should also be easy to implement in software
or hardware. In earlier meetings, we decided not to use a CRC.
An XOR of all header and payload bytes has the disadvantage of making all zeros
with a zero checksum a valid packet. To avoid this I added one more term, in
effect changing even parity to odd parity.
The following words can be dropped into ADT rev 2:
The CHECKSUM field shall be one byte. The value of this field shall be the XOR
of the following bytes:
a) all bytes in the ADT header field,
b) all bytes (if any) in the ADT payload field,
c) one byte of value 0xff.
The CHECKSUM value shall be calculated before the encoding operation specified
We might consider adding a note stating that the XOR of all header byte, packet
bytes and the checksum byte should be 0xff.
... Erich Oetting
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10