RE: [Tsvwg] SCTP Checksum Change to the IESG

Scott,

I see the hardware implementation notes added in
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpcsum-06.txt

A check that 'logically' zeros content of the checksum field during a
checksum calculation and then compares the result to an unaltered field is
robust.  Passing an unaltered packet to a software stack provides a complete
diagnostic should there be a suspected problem with checksum hardware and
allows an unmodified software implementation to take over.  It is clumsy to
alter the packet and then require a means to expose this prior value.  Would
it be possible to suggest presenting an unaltered packet in the event of an
error as an alternative?  Exposing the unaltered CRC is common practice as a
diagnostic.  The CRC field in the header over a hidden zero value is an
unusual case with respect to CRC.  Imposing a read/write/read operation on
this field as opposed to just a read is more prone to error and adds
complexity within the circuit and interface.

 -Doug

On May 1, 2002 5:51 AM Scott Bradner (sob@harvard.edu) wrote:
>
>
> fyi - the revised version of the SCTP checksum chnage will be
> posted today as draft-ietf-tsvwg-sctpcsum-06.txt - this is the
> version that the IESG will consider for publication as a Proposed
> Standard RFC updating RFC 2960.
>
> Scott

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg