Re: iSCSI : Digest Error Problems & CmdSN/ExpCmdSN window issues

["Eddy Quicksall" <ESQuicksall@hotmail.com>]

Unfortunatly, I must agree with this issue. You should never rely on
anything within the scope of a CRC error. So, there would be no way to
verify the tag.

Eddy

----- Original Message -----
From: <julian_satran@il.ibm.com>
To: <ips@ece.cmu.edu>
Sent: Thursday, January 25, 2001 12:40 PM
Subject: Re: iSCSI : Digest Error Problems & CmdSN/ExpCmdSN window issues


>
>
> answers in text - Julo
>
> Santosh Rao <santoshr@cup.hp.com> on 25/01/2001 04:06:59
>
> Please respond to Santosh Rao <santoshr@cup.hp.com>
>
> To:   IPS Reflector <ips@ece.cmu.edu>
> cc:
> Subject:  iSCSI : Digest Error Problems & CmdSN/ExpCmdSN window issues
>
>
>
>
> Julian & All,
>
> There's a number of problems with the current iSCSI handling of digest
> errors (Section 5.5) :
>
> "When an initiator receives an iSCSI data PDU with a digest error or any
> other PDU with a header or data digest error, it must discard and
> re-start the task -provided it can recognize the Initiator Task Tag".
>
> 1) The initiator task tag cannot be trusted when a header digest error
> is seen. What does the phrase "provided it can recognize the initiator
> task tag" mean ?
> How can an initiator reliably claim that the initiator task tag is
> trustworthy ?
>
> <js> an initiator may choose to provide some redundancy in the tag itself
> </js>
>
[ rest of original message deleted here]
> Regards,
> Santosh
>
>  - santoshr.vcf
>
>
>
>