If we can
use “reject” when it is not a list, can you please make that clear? Also can we
allow it for boolean’s too just for completeness?
The rev 10
spec currently says:
responder does not support or is not allowed to use
the offered options with a specific originator, it
the constant "Reject".
That is in
the discussion of list negotiations. And an EMAIL you sent on 2/6 (RE: iSCSI:
Boolean value (yes, no) negotiation) said:
> Eddy is right - reject is not intended/valid for booleans.
From: Julian Satran
Sent: Thursday, February 21, 2002
To: Luben Tuikov
Cc: Ips Reflector (E-mail);
KRUEGER,MARJORIE (HP-Roseville,ex1); email@example.com
Subject: Re: iSCSI: key
negotiation - Unrecognized value?
Marjorie is correct - the text is
(quite) explicit about requiring reject.
As for you example - the value to be
answered by the target is the maximum acceptable - see the rules for numeric
cc: "Ips Reflector (E-mail)"
<firstname.lastname@example.org>, Julian Satran/Haifa/IBM@IBMIL
Subject: Re: iSCSI: key negotiation -
> What is the proper response if you recognize a key, but are offered a
> that you don't recognize? For instance, what if MaxConnections=yes
> Where is that specified in the document?
v10, pg 34, top:
Any other key not understood by the responder may be ignored
by the responder without affecting the basic function. However,
the Text Response for a key not understood MUST be
v10, pg 33, middle:
If a responder does not support or is not allowed to use
all of the offered options with a specific originator,
it may use the constant "Reject".
Luben Tuikov, Senior Software Engineer, Splentec Ltd.
Bus: +1-905-707-1954x112, 9-5 EST. Fax: +1-905-707-1974.