RE: Question regarding SNACK and bidi transfers

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

Eddy,

In fact 2.2.2.3 contains:

For bidirectional commands, the target uses the DataSN/R2TSN to sequence Data-In and R2T PDUs in one continuous sequence (undifferentiated). 

Do you think I should repeat this in 9.8.1 and 9.7 ?

Julo

Eddy Quicksall <eddy_quicksall@ivivity.com> 06/19/2002 01:11 PM Please respond to Eddy Quicksall

To:        Julian Satran/Haifa/IBM@IBMIL         cc:        ips@ece.cmu.edu, Bill Studenmund <wrstuden@wasabisystems.com>         Subject:        RE: Question regarding SNACK and bidi transfers

Julo,

Since the answer to the 2nd question is "yes" (see your EMAIL with subject
"Emailing: msg10874.txt"), then I think the spec should make that more clear
in sections 9.8.1 and 9.7.

Perhaps in section 9.8.1, it should say something like "Except, when used
with a bidirectional command and SNACK is being supported, the R2TSN must
start with a number that couples the R2TSN and DataSN together as one
continuous sequence". And a similar statement added to 9.7.

Eddy

-----Original Message-----
From: Bill Studenmund [mailto:wrstuden@wasabisystems.com]
Sent: Tuesday, June 18, 2002 7:56 PM
To: ips@ece.cmu.edu
Subject: Question regarding SNACK and bidi transfers


I have a question about SNACK type 0 requests. In the text, they are
described as being for Data-In PDUs or R2T PDUs.

For a bidi command, how do you know which? Does this mean that for a bidi
command, data-in and R2TSNs have to be mutually-unique (i.e. drawn from
the same pool)?

Take care,

Bill