RE: iSCSI: scope of keys

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

Eddy,
you read to much into my reply.  The Requirement is stated elsewhere, I do
not think all commentary can be included in that appendix.  The important
thing is it is consistent with the rest of the Draft.

I understand your point, but I do not know what the right trade off is
here.  Each time we repeat, in a different way, what is said elsewhere, we
increase the possibility of document errors and continue to extend the
length of the document.  As we push for Last Call, unless it is wrong, I
say leave it alone.

.
.
.
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, Cell: (408) 499-9702
Internet address: hufferd@us.ibm.com


"Eddy Quicksall" <Eddy_Quicksall@ivivity.com>@ece.cmu.edu on 12/21/2001
06:13:29 AM

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


To:    John Hufferd/San Jose/IBM@IBMUS
cc:    Julian Satran/Haifa/IBM@IBMIL, <ips@ece.cmu.edu>
Subject:    RE: iSCSI: scope of keys



John,

I think my point was missed. Now you have possibly pointed out another
angle
to my point.

My point is that "use" does not contain enough information. In your
response
below, you have implied that IO now means "required" ... but it does not.

I think that "use" has been overloaded and I think each key should have a
list of properties (use is one, scope is another and now maybe required
should be a third).

Eddy

-----Original Message-----
From: John Hufferd [mailto:hufferd@us.ibm.com]
Sent: Friday, December 21, 2001 1:05 AM
To: Eddy Quicksall
Cc: Julian Satran; ips@ece.cmu.edu
Subject: RE: iSCSI: scope of keys


Eddy,
It not only OK, it is required.

.
.
.
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, Cell: (408) 499-9702
Internet address: hufferd@us.ibm.com


"Eddy Quicksall" <Eddy_Quicksall@ivivity.com>@ece.cmu.edu on 12/18/2001
07:25:44 AM

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


To:    Julian Satran/Haifa/IBM@IBMIL, <ips@ece.cmu.edu>
cc:
Subject:    RE: iSCSI: scope of keys



IO means "only during login". It does not mean "connection only".

 13 TargetName

 Use: IO by initiator ALL by target, Declarative

 This key must be provided by the initiator of the TCP connection to
 the remote endpoint in the first login request ...

So, here is a case where it is session wide ... so IO cannot mean
"connection only" (I assume that since TargetName is not LO, then it
must
be
ok to send this key for each connection).


Eddy

-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
Sent: Friday, December 14, 2001 3:50 PM
To: ips@ece.cmu.edu
Subject: Re: iSCSI: scope of keys


Eddy,

I think the text says it - but if people love headers better I can add
it (some voices needed).

Julo



        "Eddy Quicksall" <Eddy_Quicksall@ivivity.com>
Sent by: owner-ips@ece.cmu.edu


14-12-01 22:12

        To:        "ips@ece. cmu. edu \(E-mail\)" <ips@ece.cmu.edu>
        cc:
        Subject:        iSCSI: scope of keys






Would it make sense to add a "scope" to each key definition? The IO and
LO "use:" labels almost do that but not in all cases. For example:





 SW = Session wide


 CO = Connection only





 Use: IO


 Who can send: Initiator


 Scope: SW





 Key=<value>





Eddy