RE: iSCSI: CRC description

Bill Studenmund <wrstuden@wasabisystems.com> Wed, 12 June 2002 20:59 UTC

Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12796 for <ips-archive@odin.ietf.org>; Wed, 12 Jun 2002 16:59:40 -0400 (EDT)
Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id g5CKoG926953 for ips-outgoing; Wed, 12 Jun 2002 16:50:16 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from lion.ninthwonder.com (lion.ninthwonder.com [151.199.66.147]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id g5CKoFw26946 for <ips@ece.cmu.edu>; Wed, 12 Jun 2002 16:50:15 -0400 (EDT)
Received: by lion.ninthwonder.com (Postfix, from userid 1021) id 3756530706; Wed, 12 Jun 2002 16:50:10 -0400 (EDT)
Date: Wed, 12 Jun 2002 13:48:01 -0700
From: Bill Studenmund <wrstuden@wasabisystems.com>
X-X-Sender: <wrstuden@candlekeep.home-net.internetconnect.net>
To: Julian Satran <Julian_Satran@il.ibm.com>
Cc: ips@ece.cmu.edu
Subject: RE: iSCSI: CRC description
In-Reply-To: <OFCE99D338.40171C47-ONC2256BD6.0065D177@telaviv.ibm.com>
Message-ID: <Pine.NEB.4.33.0206121327450.422-100000@candlekeep.home-net.internetconnect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

On Wed, 12 Jun 2002, Julian Satran wrote:

> The thing about this text that is going on and on is very frustrating.
> First Vince insisted on emphasis.
> Now you find it confusing.
>
> I gave it as a quiz to a undergraduate class and no one made a mistake.
>
> How much effort do you think I will spend on it? And who are the people
> that are confused?

I'm not sure how much effort you need to spend on this. I'll admit I was
one of the people confused, but that was more about CRC methods and the
bit reflection we have happening than anything else.

The only thing I might suggest would be to include parameters appropriate
for one of the CRC libraries. For instance including settings for Ross
Williams's CRC discussion could be quite useful, and remove much
ambiguity.

If there still is confusion and size becomes a concern, perhaps we should
generate an ID covering the CRC process. Something like
draft-ietf-tsvwg-sctpcsum-07.txt but for iSCSI.

> pat_thaler@agilent.com
> 06/12/2002 09:24 PM
> Please respond to pat_thaler
>
>
>         To:     Julian Satran/Haifa/IBM@IBMIL
>         cc:     ips@ece.cmu.edu, owner-ips@ece.cmu.edu
>         Subject:        RE: iSCSI: CRC description
>
>
>
> Julian,
>
> The changes to the text on CRC are a step down rather than up in clarity.
>
> In particular:
>  " - In the bit stream mentioned above the CRC bits are appended   to the message bits with x^31 first followed by x^30 etc. In   the examples provided in Appendix B.4 - CRC Examples, the   value is outlined as a word sent or received and therefore   the CRC bits are mapped into the CRC word according to Section   1.3.4 Bit Rule - i.e., the x^31 coefficient in bit 7 of   the first byte of the digest continuing to through the byte the x^24
> coefficient in bit 0 of the first byte, continuing with the x^23
> coefficient in bit 7 of second byte through x^0 in bit 7 of the last byte.

Shouldn't that be "x^0 in bit 0 of the last byte"?

> Replace, "The CRC should be calculated as follows:" with "The CRC MUST be
> calculated using a method that produces the same result as the following
> process:"
> Regards,
> Pat

Take care,

Bill