RE: Coverage of Data Digest when using Header Digests

["Barry Reinhold" <bbrtrebia@mediaone.net>]

Ok,
	So if the bidi-read length and ADDCDB fields are not in the data digest
then I assume we have to figure them into the header digest even though they
are located past the header digets. Is that the expected behavior?

-----Original Message-----
From: mbakke@cisco.com [mailto:mbakke@cisco.com]
Sent: Monday, January 22, 2001 10:22 AM
To: julian_satran@il.ibm.com
Cc: ips@ece.cmu.edu; Barry Reinhold
Subject: Re: Coverage of Data Digest when using Header Digests



Barry-

In particular, the data digest covers only the SCSI Data part of an
iSCSI message; the header digest covers everything else.  This means
that in an 8k write, the data digest will cover only the 8k, and the
header digest will cover everything else.

Hope this helps,

Mark

julian_satran@il.ibm.com wrote:
>
> Barry,
>
> Considering that one of the reasons to have a separate header and data
> digest was to enable data
> to carried through proxies, virtualizers etc. the current thinking is that
> the data digest will cover only the data and the header (including
> extensions) will be covered by the header digest.
>
> Julo
>
> "Barry Reinhold" <bbrtrebia@mediaone.net> on 21/01/2001 21:50:04
>
> Please respond to "Barry Reinhold" <bbrtrebia@mediaone.net>
>
> To:   Julian Satran/Haifa/IBM@IBMIL
> cc:
> Subject:  Coverage of Data Digest when using Header Digests
>
> Julian,
>      Is the Data Digest intended to cover whatever follows the 48 byte
> iSCSI
> header? In particular in a command frame which has a CDB > 16 bytes, uses
> bidi, has immediate data, and is using both header and data digests - what
> would the data digest cover?
>                                                              - barry
> reinhold

--
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054