RE: [Tsvwg] sctp error check

Lyndon,

We can do this one issue at a time or attempt to do a few things in
parallel.

I would prefer the (1) CRC-32c, (2) all one's initialization of the CRC, and
(3) non-inverted store.

The other issue that remains open would be the (4) byte order the reflected
CRC value is stored.  To put this information into the normal order, a
routine such as flip_ntohl() would need to be added to the library and would
benefit little endian processors.

Doug

> I have no preference on the particular CRC, but I agree with
> Andreas that we should try to settle this issue.
>
> Cheers,
>
> Lyndon
>
> At 03:26 PM 8/29/2001 +0200, Andreas Jungmaier wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Dear all, hi Randy,
> >
> > > We, as of now, only need to pick the poly.... for the
> > > most part I think the only issue is
> > >
> > > CRC-32/ITU or CRC-32c
> > >
> >
> >Randy, would you take on another straw poll, in order to
> >get this (overlong) thread finally settled now ?!
> >
> >For the reasons given in the draft
> >http://www.ietf.org/internet-drafts/draft-sheinwald-iscsi-crc-00.txt
> >please count me in favor of *CRC-32-C*
> >
> >Best regards,
> >Andreas
> >- --

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