Re: Initiator Task Tag
William Studenmund <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sep 19, 2006, at 9:12 AM, <[email protected]> <[email protected]> wrote: > Should the Initiator task tag be unique for an I_T nexus or for an > I_T_L > nexus? They are session-unique. The difference is that they have meaning for iSCSI operations in addition to SCSI ones. > 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) That definition is good-enough. :-) > 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). I don't see how this disagrees. The I_T_L_x nexus is the task. The specific value of the ITT is an attribute of the task. That it (the ITT) is an attribute of the task doesn't mean that it is only scoped to the I_T_L level. Take care, Bill -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFEFwfDJT2Egh26K0RAuKdAKCcbJt6Otbgemjyf6K2nHf9bcZD0wCgk/pN z9vUHQImWhti0ldTtq2VIk4= =tfDc -----END PGP SIGNATURE----- _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips