ips-1----Page:4
1 2 3 4 5 6 7 8 9
|
Handling of Unidirectional NOP-out PDUs at the Initiator For a unidirectional NOP-out PDU from the initiator with ITT = TTT = 0xffffffff, CmdSN is not advanced To retire a unidirectional NOP-out PDU, needs confirmation from the target that the PDU has been processed A unidirectional NOP-out PDU is outstanding until the target responds with a control-type PDU with ExpCmdSN set to at least x + 1 where x is the CmdSN of the PDU with the immediate flag set For a session with multiple connections, a PDU with no immediate flag and CmdSN=x sent in a different connection could trigger a control-type PDU with ExpCmdSN=x+1 from the target To avoid ambiguity, the control-type PDU from the target with ExpCmdSN=x+1 (or larger) must be received on the same connection as the unidirectional NOP-out PDU in order to retire the NOP-out PDU An implementation note was also added which recommended that “To avoid complexity, a NOP-out PDU with ITT /= 0xffffffff can be used instead” |