Re: iSCSI: draft 7: iSCSI response and SCSI sense data

["Julian Satran" <Julian_Satran@il.ibm.com>]

That is the current situation - statuse are generated (and responses) are
generated at the target.

Sorry - Steph - I am wrong and the right guy to blame for anything :-)

Julo

Stephen Bailey <steph@cs.uchicago.edu> on 02-08-2001 16:48:34

Please respond to Stephen Bailey <steph@cs.uchicago.edu>

To:   Julian Satran/Haifa/IBM@IBMIL
cc:
Subject:  Re: iSCSI: draft 7: iSCSI response and SCSI sense data




> You change opinions faster than draft changes :-)

Actually, I think I do a bad job of explaining myself.

You already chastised me for a `reversal' on this topic.

My position, stated the last time you claimed I reversed (just a few
weeks ago, I think), is:
  1) target should report ALL forms of task completion using SCSI status
  2) the initiator should NOT synthesize SCSI status.

My originally stated opinion had to do with 2).  I never argued with
the target `synthesizing' SCSI status, because the target is NOT
synthesizing SCSI status, it's generating it.

I agree that I have been confused about the role of target-generated
response codes WRT to request protocol errors (that's FCP data length
& invalid FCP_CMND response codes).  I have decided that the FCP
approach is wrong and the ||SCSI approach is right.  The FCP targets
that I like use the ||SCSI approach anyway.

How many more times can I say uncle?  I said it on the list (check the
archive).  I'm saying it here.  You want me to say it on the list
again?

Are you ever wrong about anything?

Steph