Re: iSCSI: Question on login min/Max

["Julian Satran" <Julian_Satran@il.ibm.com>]

Kevin,

That part has some history.

Several drafts ago the selection was "by rule" - i.e., each of the parties stated what it wanted and the result was based on the rule (that both know).
This scheme, although simple, was felt as unnatural by many readers (implementers?) and we changed it to the selection by the responder - i.e., the responder selects the "right" value - respecting some rules. Obviously then the rule can't be "the maximum/minimum/other  of two values" as there are no two values on the wire and I felt that the best way to express this is to state the constraint the responder has to respect. This was the text you found in draft 13.

Bob Russell felt that a succinct statement stating this restriction in line with the Scope, Default etc. will be  simpler to follow and I think he is right..
The new text is the one you see in draft 14.  Except for one rule that was stated wrong (a typo) and is now corrected there is no difference between 13 and 14.

And yes your interpretation of the rule is correct - at the sequence you show the initiator is supposed to close (protocol error).

Again - we did not have two offered numbers for a long time.

Julo

kevin_lemay@agilent.com 07/01/2002 06:16 PM Please respond to kevin_lemay

To:        Julian Satran/Haifa/IBM@IBMIL         cc:        ips@ece.cmu.edu         Subject:        iSCSI: Question on login min/Max

Julian,
 
In draft v14, page 210, The following text was added:
 
"Result function wherever mentioned states the function that can be applied to check the validity of the responder selection. Minimum means that the selected value cannot exceed the offered value. Maximum means that the selected value cannot be lower than the offered value."
 
What drove this change? This is a departure from what it was previously where we could just take the min/max of the two offered numbers.
 
So if I interpret this correctly, if:
 
Init   -> DefaultTime2Wait=2 (func is Max)
Target -> DefaultTime2Wait=1
 
Init detects an error and closes the TCP connection.
 
Correct?
 
Kevin