Mona,

The term was mislabeled as a result of an error in the 07-424 proposal. That proposal corrected the state machine argument by changing the name of the argument from  'Requested Offset Xfer_Rdy state machine argument' to the 'Requested Write Data Length Xfer_Rdy state machine argument'. The error was that the term 'requested' should also have been deleted. The correct name should have been 'Write Data Length Xfer_Rdy state machine argument'.

Rob,
Do you consider that editorial or will it take a proposal to delete the offending word?

Bye for now,
George Penokie

Dept 9A8 030-3 A410
E-Mail:    gop@us.ibm.com
Internal:  553-5208
External: 507-253-5208



Mona <monika.talwar@nsysinc.com>
Sent by: owner-t10@t10.org

12/03/2007 06:12 AM
Please respond to
monika.talwar@nsysinc.com

To
t10@t10.org
cc
Subject
SAS Initiator XFER_RDY frame handling






Hi All,

Please refer to the last line of of Section 9.2.6.2.3.3.1 (sas2r13, Page#466)

--------------------------------
c) set the Previous Write Data Length state machine variable to the Requested Write Data Length
Xfer_Rdy state machine argument.
--------------------------------


I am not able to find the defination of Requested Write Data Length Xfer_Rdy state machine ardument. Is this the 'write data length' refered in bullet (e) of second last para in section 9.2.6.2.2.3(pasted below)

-------------------------------- second last para in section 9.2.6.2.2.3, Page#460

If this state machine receives an ACK Transmitted confirmation for an XFER_RDY frame, then this state
machine shall send an XFER_RDY Arrived message to ST_ITS state machine specified by the tag. The
message shall include the following Xfer_Rdy arguments:
a) retry data frames;
b) retransmit bit;
c) target port transfer tag;
d) requested offset; and
e) write data length


-------------------------------- second last para in section 9.2.6.2.2.3


Please Suggest.

Thanks and best Regards
Mona