Re: checking immediate data

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

The reason beyond this was that a 'highly optimized target may have 
prepared already the R2T. I guess that you are objecting to the second 
MUST in the sentence  and I guess that except for recovery it is a bit too 
strong. For recovery however you might end up having a different sequence 
in recovery vs. original.

Regards,
Julo



Eddy Quicksall <eddy_quicksall@ivivity.com> 
Sent by: owner-ips@ece.cmu.edu
07/08/2003 19:34

To
"Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>
cc

Subject
checking immediate data






Section 12.11 says:
 
If ImmediateData is set to No and InitialR2T is set to Yes, then the
initiator MUST NOT send unsolicited data and the target MUST reject
unsolicited data with the corresponding response code.
 
 
If the initiator says ImmediateData=No and the target has the capability 
of taking immediate data BUT the initiator sends immediate data anyway, 
why should the target be responsible to make that check (as long as it 
isn't going to break the target)? 
 
Eddy