RE: iSCSI: Question on login min/Max

[pat_thaler@agilent.com]

Kevin,

I don't think the text changed the meaning of the draft. The following was in draft 10 under 2.2.4 Text mode negotiation:
For numerical and single literal negotiations, the responding party
MUST respond with the required key. The value it selects, based on the
selection rule specific to the key, becomes the negotiation result.
The selection of a value not admissible under the selection rules is
considered a protocol error and is handled accordingly.

Your example:
Init   -> DefaultTime2Wait=2 (func is Max)
Target -> DefaultTime2Wait=1
would have been a protocol error and closed the connection under the draft 10 rules and later. (I think this was in earlier drafts as well. I just didn't bother to look farther back.)

The impact of the new text is just editorial.

Regards,
Pat


-----Original Message-----
From: kevin_lemay@agilent.com [mailto:kevin_lemay@agilent.com]
Sent: Monday, July 01, 2002 8:17 AM
To: Julian_Satran@il.ibm.com
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