RE: iSCSI: reference for CRC32C?

[pat_thaler@agilent.com]

Jonathan, 

That informative reference is already in the draft. It has been in the draft since at least draft 10. Probably an informative reference to draft-sheinwald-iscsi-crc-02.txt which has been submitted to the RFC process would also be enlightening about why we chose to use a CRC and this particular CRC.

I thought Margorie's question was whether a normative reference was needed to fully define the algorithm.

Regards,
Pat

-----Original Message-----
From: Jonathan Stone [mailto:jonathan@DSG.Stanford.EDU]
Sent: Monday, July 29, 2002 4:51 PM
To: pat_thaler@agilent.com
Cc: marjorie_krueger@hp.com; ips@ece.cmu.edu
Subject: Re: iSCSI: reference for CRC32C? 


In message <1BEBA5E8600DD4119A50009027AF54A00D373802@axcs04.cos.agilent.com>pat_thaler@agilent.com writes
>Margorie,
>
>The text in 11.1 suffices to fully define the algorithm. 

Agreed, It does specify the algorithm. But IMHO the spec should still
cite the original source --- Castagnoli et al. --- because that is the
original source.  And because that's where to start looking, for anyone
who cares about the ins and outs of the specific choice of algorithm.

The citation i have  handy is:
@Article{castagnoli-crc,
  author =       { Guy Castagnoli and Stefan Braeuer and Martin Herrman},
  title =        {{Optimization of Cyclic Redundancy-Check Codes with 24
                  and 32 Parity Bits}},
  journal =      IEEE Transactions on Communication,
  year =         {1993},
  volume =       {41},
  number =       {6},
  pages =        {},
  month =        {June},
}

(I have a hardcopy, with page numbers, if I can find it.)