RE: iSCSI: Boolean value (yes, no) negotiation

["Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>]

So that means, if the target needs to use ONLY immediate data,
it has to fail the login because the initiator said NO to ImmediateData?

thanks!
 -lakshmi

-----Original Message-----
From: Rahul Bhagwat [mailto:rahulb@veritas.com] 
Sent: Wednesday, February 06, 2002 10:07 AM
To: Lakshmi Ramasubramanian; ips@ece.cmu.edu
Subject: Re: iSCSI: Boolean value (yes, no) negotiation


I believe a key is not negotiated thrice as you have pointed out. That
is a sender offers a value, receiver offers it's own and that's it. (I
think specs has a mention that a key cannot be negotiated twice. This
example falls into that category.) The result of the negotiation is key
dependent. For example, in this particular key, when initiator sends 
ImmediateData=no, the negotiation is over as this is an
AND function. However it is not an error to send back a response. In any
case, the outcome of the result was decided for the initiator when it
sent the key first and for the target when it received the key.

Regards,
Rahul
----- Original Message ----- 
From: "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>
To: <ips@ece.cmu.edu>
Sent: Wednesday, February 06, 2002 10:56 PM
Subject: iSCSI: Boolean value (yes, no) negotiation


> Could someone please clarify Boolean key=value usage
> (such as "ImmediateData=yes", etc)?
> 
> For example, the initiator sends to target "ImmediateData=no".
> But the target wants ImmediateData. So, it sends back
> "ImmediateData=yes".
> The initiator, being able to handle it, sends back "ImmediateData=no".
> Now, they use immediate data in the PDUs. 
> 
> Is this valid? Or, in the above case if the target can't handle
> non-immediate data it has to reject the login ?
> 
> thanks!
>  -lakshmi
>