[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: iSCSI: key negotiation - Unrecognized value?
Eddy,
This thread took way too much list space. I made it clear from the outset that I'll fix the text.
Julo
|
| Eddy Quicksall <Eddy_Quicksall@ivivity.com>
21-02-02 20:24
|
To: Julian Satran/Haifa/IBM@IBMIL
cc: "KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie_krueger@hp.com>, "ips@ece. cmu. edu (E-mail)" <ips@ece.cmu.edu>
Subject: RE: iSCSI: key negotiation - Unrecognized value?
|
Julian,
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:
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".
That is in the discussion of list negotiations. And an EMAIL you sent on 2/6 (RE: iSCSI: Boolean value (yes, no) negotiation) said:
--snip--
> Eddy is right - reject is not intended/valid for booleans.
>
> Julo
Eddy
-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
Sent: Thursday, February 21, 2002 1:18 AM
To: Luben Tuikov
Cc: Ips Reflector (E-mail); KRUEGER,MARJORIE (HP-Roseville,ex1); owner-ips@ece.cmu.edu
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 negotiations.
Julo
|
| Luben Tuikov <luben@splentec.com>
Sent by: owner-ips@ece.cmu.edu
20-02-02 22:21
|
To: "KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie_krueger@hp.com>
cc: "Ips Reflector (E-mail)" <ips@ece.cmu.edu>, Julian Satran/Haifa/IBM@IBMIL
Subject: Re: iSCSI: key negotiation - Unrecognized value?
|
"KRUEGER,MARJORIE (HP-Roseville,ex1)" wrote:
>
> What is the proper response if you recognize a key, but are offered a value
> that you don't recognize? For instance, what if MaxConnections=yes is
> offered?
>
> 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
key=NotUnderstood.
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".
Comments?
--
Luben Tuikov, Senior Software Engineer, Splentec Ltd.
Bus: +1-905-707-1954x112, 9-5 EST. Fax: +1-905-707-1974.
