ITT has to be I_T unique. TTT
has to be just I_T_L unique (TTT is mostly a "target convenience"
artifact). Julo
<Jacob_Cherian@xxxxxxxx>
19/09/06 19:12
To
<ips@xxxxxxxx>
cc
Subject
Initiator Task Tag
Should the Initiator task tag be unique for an I_T
nexus or for an I_T_L
nexus?
Section 3.2.1 says:
Initiator identifying elements, such as the Initiator Task Tag, are
global across the session regardless of the connection on which they are
sent or received.
and
Sections 10.2.1.8 says:
While a task exists, this tag MUST uniquely identify the task
session-wide.
SCSI may also use the initiator task tag as part of the SCSI task
identifier when the timespan during which an iSCSI initiator task tag
must be unique extends over the timespan during which a SCSI task tag
must be unique.
(which seems to imply I_T nexus wide uniqueness)
Section 3.5.1.1 says:
IN arguments such as task attributes, Expected Data Transfer Length for
one or both transfer directions (the latter for bidirectional commands),
and Task Tag (as part of the I_T_L_x nexus).
(which seems to follow the broadest definition allowed by SAM)
What was the intention of the designers?
Thanks,
Jacob
_______________________________________________
Ips mailing list
Ips@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ips
