RE: is TargetName always mandatory or not?

["John Hufferd" <hufferd@us.ibm.com>]

Julian,
I agree with Jim Hafner on this issue.  The Draft should say:

"The TargetName is required on the first login message on every connection
(in all cases, new session or adding connections to existing sessions)."

Also I think we need to change section 3.12.9, which currently says:

"The TSID is the target assigned tag for a session with a specific named
initiator that, together with the ISID uniquely identifies a session with
that initiator".

Should be changed to:

"The TSID is the target assigned tag for a session with a specific named
initiator that, together with the ISID uniquely identifies a session from
that specific target to that specific initiator. That is, the TSID is a
unique value within the scope of a specific Target (Not necessarily Unique
within the iSCSI Target Network Entity)."

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136
Internet address: hufferd@us.ibm.com


Jim Hafner/Almaden/IBM@IBMUS@ece.cmu.edu on 11/02/2001 08:04:03 AM

Sent by:  owner-ips@ece.cmu.edu


To:   ips@ece.cmu.edu
cc:
Subject:  RE: is TargetName always mandatory or not?




Folks,

I think this thread may be exposing either an ambiguity in the draft or
perhaps a gap.

I think it's possible to interpret the requirement that TargetName be
supplied (for normal sessions) only on the *first login message on the
first connection of a new session* and is not required on the *first login
message of subsequent connections intended for the same session". My
personal interpretation is that the TargetName is required on the *first
login message on every connection (in all cases, new session or adding
connections to existing sessions)*.  I also think Andre's example of a
network entity containing many iSCSI targets with shared network portals
(and the scoping of portal group tags and TSIDs by iSCSI target) points out
the need for the more restrictive requirement (and the rest of my response
to Andre assumed this).

But I've heard other comments that can be interpreted as the less
restrictive requirement is what is intended.

So, I suggest (and I don't think this is asking much) that the requirement
be that TargetName be supplied on the first Login message of every
connection (not just the leading one).

Jim Hafner