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 h15Nmem24052
	for ips-outgoing; Wed, 5 Feb 2003 18:48:40 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h15NmdW24044
	for <ips@ece.cmu.edu>; Wed, 5 Feb 2003 18:48:39 -0500 (EST)
Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237])
	by msgbas2x.cos.agilent.com (Postfix) with ESMTP
	id CD5824618; Wed,  5 Feb 2003 16:48:37 -0700 (MST)
Received: from axcsbh4.cos.agilent.com (axcsbh4.cos.agilent.com [130.29.152.145])
	by relcos2.cos.agilent.com (Postfix) with SMTP
	id 9B7281A; Wed,  5 Feb 2003 16:48:37 -0700 (MST)
Received: from 130.29.152.145 by axcsbh4.cos.agilent.com (InterScan E-Mail VirusWall NT); Wed, 05 Feb 2003 16:48:36 -0700
Received: by axcsbh4.cos.agilent.com with Internet Mail Service (5.5.2653.19)
	id <DGCDMWRV>; Wed, 5 Feb 2003 16:48:36 -0700
Message-ID: <1BEBA5E8600DD4119A50009027AF54A00ECB3D73@axcs04.cos.agilent.com>
From: kevin_lemay@agilent.com
To: blandry@crossroads.com, ips@ece.cmu.edu
Subject: RE: iSCSI: numeric-range format question (pedantic)
Date: Wed, 5 Feb 2003 16:48:35 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Buck,

I coded it this way....

OFMarkInt=4096

If you don't fine the "~" delimiter then it is a single value.

I would interpret 4096~4096 as a range with only one acceptable value.

Kevin

-----Original Message-----
From: Buck Landry [mailto:blandry@crossroads.com]
Sent: Wednesday, February 05, 2003 3:35 PM
To: ips@ece.cmu.edu
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
