|
CRC Use of CRC to protect header and data Resolution (mailing list – July 9, 2003) (A) MUST implement CRC support (B) CRC usage is all-or-nothing on header + data Note: One vs. two CRC issue is still open (C) CRC usage is bidirectional: both or neither (D) CRC omission requires consent of both ends of connection – i.e., either end can force CRC usage (E) CRC usage is OPTIONAL [but, c.f. (D)] (E’) CRC usage is admin. config, not visible to protocols ULP design discussion in applicability statement draft |