RE: iSCSI - Range of values can be negotiated for integers?

["Julian Satran" <Julian_Satran@il.ibm.com>]

Kevin,

You have a good point. I have observed myself that I created this problem when introducing ranges and I fixed it - but too late (yesterday :-)) The section 4 text will read:

The value offered can be an integer, a range defined by lower and upper value - both integers separated by a comma, a single literal constant a Boolean value (Yes or No), or a list of comma separated, literal constant values. A range MAY ONLY be offered only if it is explicitly allowed for a key. A selected value can be an integer, a single literal constant or a Boolean value.

Regards,
Julo

"LEMAY,KEVIN (A-Roseville,ex1)" <kevin_lemay@agilent.com> Sent by: owner-ips@ece.cmu.edu 06-03-02 18:10 Please respond to "LEMAY,KEVIN (A-Roseville,ex1)"

To:        "'Robert D. Russell'" <rdr@io.iol.unh.edu>         cc:        ips@ece.cmu.edu, "'Satran, Julian'" <julian_satran@hotmail.com>         Subject:        RE: iSCSI - Range of values can be negotiated for integers?

One could take the most liberal interpretation and offer:

MaxConnections=1,15
MaxBurstSize=8192,64456
FirstBurstSize=8192,64456
....

Where in the spec does it say which integer keys are allowed to use ranges
in the negotiation?

Kevin Lemay

-----Original Message-----
From: Robert D. Russell [mailto:rdr@io.iol.unh.edu]
Sent: Wednesday, March 06, 2002 8:02 AM
To: LEMAY,KEVIN (A-Roseville,ex1)
Cc: ips@ece.cmu.edu; 'Satran, Julian'
Subject: Re: iSCSI - Range of values can be negotiated for integers?


Kevin:

I believe that the sentence you quote should be prefaced as
follows:

"Depending on the key, the value offered can be an integer,
a range defined by a lower and upper value, ..."

This makes it clear that it does NOT apply to all numeric keys.

Julian, if you agree would you please add the "Depending on the key,"
prefix to the sentence in question?

Thanks,
Bob Russell


On Tue, 5 Mar 2002, LEMAY,KEVIN (A-Roseville,ex1) wrote:

> On page 60 of iSCSI v11 says that:
>
> "The value can be an integer, a range defined by a lower and upper
> value...."
>
> I must assume that any numeric key may use this feature?
>
> I don't see any reference to this new capabilty anywhere else in the
> document. I am sure that we are going to have problems at plugfest if this
> is not cleared up now.
>
> Thanks,
>
> Kevin Lemay
> Agilent Technologies
>