Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h15Nrlr24388
	for ips-outgoing; Wed, 5 Feb 2003 18:53:47 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [194.196.100.234])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h15NriW24381;
	Wed, 5 Feb 2003 18:53:44 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate.de.ibm.com (8.12.3/8.12.3) with ESMTP id h15NrXTQ055060;
	Thu, 6 Feb 2003 00:53:33 +0100
Received: from d10ml001.telaviv.ibm.com (d10ml001.telaviv.ibm.com [9.148.216.55])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h15NrXOb016240;
	Thu, 6 Feb 2003 00:53:33 +0100
In-Reply-To: <CFD808D1D39ACB47ABFF586D484CC52EDD68CB@hqmailnode1.commstor.crossroads.com>
To: "Buck Landry" <blandry@crossroads.com>
Cc: ips@ece.cmu.edu, owner-ips@ece.cmu.edu
Subject: Re: iSCSI: numeric-range format question (pedantic)
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF79B3516B.DAEE50D5-ONC2256CC4.00832DE1-C2256CC4.00833DB6@telaviv.ibm.com>
Date: Thu, 6 Feb 2003 01:53:29 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 06/02/2003 01:53:33,
	Serialize complete at 06/02/2003 01:53:33
Content-Type: multipart/alternative; boundary="=_alternative 0083374DC2256CC4_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This is a multipart message in MIME format.
--=_alternative 0083374DC2256CC4_=
Content-Type: text/plain; charset="US-ASCII"

Yes the safe assumption is c. Julo



"Buck Landry" <blandry@crossroads.com> 
Sent by: owner-ips@ece.cmu.edu
06/02/03 01:34

To
<ips@ece.cmu.edu>
cc

Subject
iSCSI: numeric-range format question (pedantic)






Is it draft 20's intent that any numeric-range may be represented by a 
single numerical-value, if that value is the only one acceptable?

I ask because:
-- the definition for numeric-range does not mention this (5.1)
-- OFMarkInt and IFMarkInt are defined as <numeric-range> for offers 
(A.3.2)
-- .. but the description for these keys says "In case it only wants a 
specific value, only a single value has to be specified".

There are three conclusions I might make:
a) When the draft says "only a single value has to be specified", it means 
only that (for instance) 4096~4096 might be specified.
b) x is valid shorthand for x~x, but only for OFMarkInt and IFMarkInt
c) x is valid shorthand for x~x, for any theoretical numeric-range

The safest choice is obviously c).  If the intent was actually a), would 
somebody please speak up.

Thanks, --buck


--=_alternative 0083374DC2256CC4_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Yes the safe assumption is c. Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Buck Landry&quot;
&lt;blandry@crossroads.com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: owner-ips@ece.cmu.edu</font>
<p><font size=1 face="sans-serif">06/02/03 01:34</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&lt;ips@ece.cmu.edu&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">iSCSI: numeric-range format
question (pedantic)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Is it draft 20's intent that any numeric-range may
be represented by a single numerical-value, if that value is the only one
acceptable?<br>
<br>
I ask because:<br>
-- the definition for numeric-range does not mention this (5.1)<br>
-- OFMarkInt and IFMarkInt are defined as &lt;numeric-range&gt; for offers
(A.3.2)<br>
-- .. but the description for these keys says &quot;In case it only wants
a specific value, only a single value has to be specified&quot;.<br>
<br>
There are three conclusions I might make:<br>
a) When the draft says &quot;only a single value has to be specified&quot;,
it means only that (for instance) 4096~4096 might be specified.<br>
b) x is valid shorthand for x~x, but only for OFMarkInt and IFMarkInt<br>
c) x is valid shorthand for x~x, for any theoretical numeric-range<br>
<br>
The safest choice is obviously c). &nbsp;If the intent was actually a),
would somebody please speak up.<br>
<br>
Thanks, --buck<br>
</tt></font>
<br>
--=_alternative 0083374DC2256CC4_=--