Pending R2T's at the initiator and initiator issuing "abort task"

RFC 3720, Section 10.5.1 says:
 
"For ABORT TASK SET and CLEAR TASK SET, the issuing initiator MUST
continue to respond to all valid target transfer tags (received via
R2T, Text Response, NOP-In, or SCSI Data-In PDUs) related to the
affected task set, even after issuing the task management request.
The issuing initiator SHOULD however terminate (i.e., by setting the
F-bit to 1) these response sequences as quickly as possible. The
target on its part MUST wait for responses on all affected target
transfer tags before acting on either of these two task management
requests. In case all or part of the response sequence is not
received (due to digest errors) for a valid TTT, the target MAY treat
it as a case of within-command error recovery class (see Section
6.1.4.1 Recovery Within-command) if it is supporting
ErrorRecoveryLevel >= 1, or alternatively may drop the connection to
complete the requested task set function."

What is expected of the initiators in case of "abort task"?. Does the
responding to "all valid target tags" apply to "abort task" also?.



_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips