SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    RE: iscsi : numerical negotiation wording is ambiguous



    How about applying the "responder must send the result" rule to
    Boolean negotiations?  The new text could then be:
     
    For Boolean negotiations (keys taking the values yes or no), the
    responding party MUST respond with the required key and the result
    of the negotiation when the received value does not determine that
    result by itself.  The last value transmitted becomes the
    negotiation result.  The rules for selecting the value to respond
    with are expressed as Boolean functions of the value received and
    the value that the responding party would select in the absence
    of knowledge of the received value.
     
    Specifically, the two cases in which responses are OPTIONAL are:
    - The Boolean function is "AND" and the value "no" is received.
        The outcome of the negotiation is "no".
    - The Boolean function is "OR" and the value "yes" is received.
        The outcome of the negotiation is "yes".
    Responses are REQUIRED in all other cases, and the value chosen
    and sent by the responder becomes the outcome of the negotiation.
     
     
     
    --David

    ---------------------------------------------------
    David L. Black, Senior Technologist
    EMC Corporation, 42 South St., Hopkinton, MA  01748
    +1 (508) 435-1000 x75140     FAX: +1 (508) 497-8500
    black_david@emc.com       Mobile: +1 (978) 394-7754
    ---------------------------------------------------

     
    -----Original Message-----
    From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
    Sent: Thursday, October 04, 2001 1:57 PM
    To: ips@ece.cmu.edu
    Subject: RE: iscsi : numerical negotiation wording is ambiguous


    Well - even I got fed-up with this long thread.

    Here the new text I am suggesting for the negotiations ("vox populi"):

    In numerical negotiations, the offering and responding party state a numerical value. The result of the negotiation is key dependent; frequently the lower or the higher of the two values is used.

    For numerical negotiations, the responding party MUST respond with the required key and the value it selects, based on the selection rule specific to the key, becomes the negotiation result.  Selection of a value not admissible under the selection rules is considered a protocol error and handled accordingly.

    For Boolean negotiations (keys taking the values yes or no), the result is a key dependent Boolean function of the two inputs. The negotiation MAY proceed only up to the point where both parties can unequivocally compute the result; continuing beyond this point is OPTIONAL (e.g., if the function is AND and one of the parties says "no" then this may end the negotiation). Both requestor and responder MUST to compute the negotiated value based on the new value(s) exchanged

    The value "?" with any key has the meaning of enquiry and should be answered with the current value or "NotUnderstood".

    The target may offer key=value pairs of its own. Target requests are not limited to matching key=value pairs as offered by the initiator.  However, only the initiator can initiate the negotiation start (through the first Text request) and completion (by setting to 1 and keeping to 1 the F bit in a Text request).

    Unless specified otherwise the negotiation process is stateless (based only on newly presented values).


    Comments?
    Julo




Home

Last updated: Thu Oct 04 20:17:24 2001
7051 messages in chronological order