Re: iSCSI: Sequence Reception TimeOut for Response PDUs

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

Praveen,

I intend to add to 6.12.2 the following text:

- An initiator may also recognize a lost iSCSI numbered response by an iSCSI timeout. In this case, error handling is done as specified in Section 6.6 Sequence Errors, using the option of a SNACK. However since SCSI command response is highly command dependent the SNACK may result in a Reject with an "invalid PDU field" reason code if the response was not issued.
That should solve the issue.

Julo

"Praveen Kumar" <praveen@basilnet.com> 06/26/2002 10:05 PM Please respond to "Praveen Kumar"

To:        Julian Satran/Haifa/IBM@IBMIL         cc:                 Subject:        iSCSI: Sequence Reception TimeOut for Response PDUs

Julian,
 
In Section 6.12.2, under the Paragraph "-Lost iSCSI Numbered Response" , is there any reason for NOT including "Sequence Reception TimeOut" as one of the mechanisms for detecting a "Lost iSCSI Numbered Response"? 
If a Numbered iSCSI response PDU is dropped (owing to header digest errors) , the Initiator could TimeOut waiting for the appropriate StatSN (assuming that the target implementation does Not support the issue of Nop-In, when Status is Not acknowledged for a long time).
Section 6.12.1 does mention this, but that section only deals with Lost Data or R2T PDUs, NOT Lost Response PDUs.
I would have expected this section (6.12.2) to mention this (Sequence Reception TimeOut) as a possibility (especially since the other sections explicitly mention this).
 
Thanks in Advance
Praveen