Inconsistent wording in transport and link layer error descriptions

George Penokie gop at us.ibm.com
Thu Jul 28 13:45:05 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* George Penokie <gop at us.ibm.com>
*
This is a multipart message in MIME format.
--=_alternative 0071D0D58625704C_=
Content-Type: text/plain; charset="US-ASCII"


Rob, 

This should be considered as an IBM letter ballot comment on SAS 1.1. 

There is some wording that is leftover in the summary error descriptions
|from when there were no frame level retries. The wording in error is: 

9.2.5.2 SSP initiator port transport layer error handling summary 
.... 
If an SSP initiator port receives a read DATA frame with a data offset
that was not expected, the ST_ITS state machine discards that frame and
any subsequent read DATA frames received for that command (see
9.2.6.2.3.3) and the application client aborts the command (see 10.2.2).
The SSP initiator port may receive a RESPONSE for the command before
being able to abort the command. 

9.2.5.3 SSP target port transport layer error handling summary 
.... 
If an SSP target port receives a write DATA frame with a data offset
that was not expected, the ST_TTS state machine discards the frame (see
9.2.6.3.3.6.1) and the device server terminates the command with CHECK
CONDITION status with the sense key set to ABORTED COMMAND and the
additional sense code set to DATA OFFSET ERROR (see 10.2.3). 

Both of the above paragraphs conflict with the information presented in
section 9.2.4.5 DATA frame - handling of link layer errors not to
mention the state machine descriptions. I recommend the following
replace those paragraphs: 

9.2.5.2 SSP initiator port transport layer error handling summary 
.... 
If an SSP initiator port receives a read DATA frame with a data offset
that was not expected see 9.2.4.5.. 

9.2.5.3 SSP target port transport layer error handling summary 
.... 
If an SSP target port receives a write DATA frame with a data offset
that was not expected see 9.2.4.5. 

Bye for now,
George Penokie

Dept 2C6  114-2 N212
E-Mail:    gop at us.ibm.com
Internal:  553-5208
External: 507-253-5208   FAX: 507-253-2880



--=_alternative 0071D0D58625704C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Rob,</font>
<br>
<br><font size=2 face="sans-serif">This should be considered as an IBM
letter ballot comment on SAS 1.1.</font>
<br>
<br><font size=2 face="sans-serif">There is some wording that is leftover
in the summary error descriptions from when there were no frame level retries.
The wording in error is:</font>
<br>
<br><font size=2 face="sans-serif">9.2.5.2 SSP initiator port transport
layer error handling summary</font>
<br><font size=2 face="sans-serif">....</font>
<br><font size=2 face="sans-serif">If an SSP initiator port receives a
read DATA frame with a data offset that was not expected, the ST_ITS state
machine discards that frame and any subsequent read DATA frames received
for that command (see 9.2.6.2.3.3) and the application client aborts the
command (see 10.2.2). The SSP initiator port may receive a RESPONSE for
the command before being able to abort the command.</font>
<br>
<br><font size=2 face="sans-serif">9.2.5.3 SSP target port transport layer
error handling summary</font>
<br><font size=2 face="sans-serif">....</font>
<br><font size=2 face="sans-serif">If an SSP target port receives a write
DATA frame with a data offset that was not expected, the ST_TTS state machine
discards the frame (see 9.2.6.3.3.6.1) and the device server terminates
the command with CHECK CONDITION status with the sense key set to ABORTED
COMMAND and the additional sense code set to DATA OFFSET ERROR (see 10.2.3).</font>
<br>
<br><font size=2 face="sans-serif">Both of the above paragraphs conflict
with the information presented in section 9.2.4.5 DATA frame - handling
of link layer errors not to mention the state machine descriptions. I recommend
the following replace those paragraphs:</font>
<br>
<br><font size=2 face="sans-serif">9.2.5.2 SSP initiator port transport
layer error handling summary</font>
<br><font size=2 face="sans-serif">....</font>
<br><font size=2 face="sans-serif">If an SSP initiator port receives a
read DATA frame with a data offset that was not expected see 9.2.4.5..</font>
<br>
<br><font size=2 face="sans-serif">9.2.5.3 SSP target port transport layer
error handling summary</font>
<br><font size=2 face="sans-serif">....</font>
<br><font size=2 face="sans-serif">If an SSP target port receives a write
DATA frame with a data offset that was not expected see 9.2.4.5.</font>
<br><font size=2 face="sans-serif"><br>
Bye for now,<br>
George Penokie<br>
<br>
Dept 2C6 &nbsp;114-2 N212<br>
E-Mail: &nbsp; &nbsp;gop at us.ibm.com<br>
Internal: &nbsp;553-5208<br>
External: 507-253-5208 &nbsp; FAX: 507-253-2880<br>
<br>
</font>
--=_alternative 0071D0D58625704C_=--





More information about the T10 mailing list