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 h1O6WjT20993
	for ips-outgoing; Mon, 24 Feb 2003 01:32:45 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from d12lmsgate-2.de.ibm.com (d12lmsgate-2.de.ibm.com [194.196.100.235])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h1O6WgW20988
	for <ips@ece.cmu.edu>; Mon, 24 Feb 2003 01:32:42 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-2.de.ibm.com (8.12.3/8.12.3) with ESMTP id h1O6VkWT063664;
	Mon, 24 Feb 2003 07:31:46 +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.5) with ESMTP id h1O6Vg6C081420;
	Mon, 24 Feb 2003 07:31:44 +0100
In-Reply-To: <B80BB115B1994D4BABC1B81FFFA1CAC71A8595@rtpexc01.hq.netapp.com>
To: "Sankar, Ranga" <Ranga.Sankar@netapp.com>
Cc: "Andre Hedrick" <andre@linux-ide.org>,
   "Wysochanski, David" <David.Wysochanski@netapp.com>,
   "dl-iscsi-eng" <dl-iscsi-eng@netapp.com>, ips@ece.cmu.edu,
   owner-ips@ece.cmu.edu
Subject: RE: iSCSI: version number
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF68CE1D39.D5FBD17E-ONC2256CD7.00205507-C2256CD7.0023DD3F@telaviv.ibm.com>
Date: Mon, 24 Feb 2003 08:31:41 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 24/02/2003 08:31:45,
	Serialize complete at 24/02/2003 08:31:45
Content-Type: multipart/alternative; boundary="=_alternative 00206FC8C2256CD7_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This is a multipart message in MIME format.
--=_alternative 00206FC8C2256CD7_=
Content-Type: text/plain; charset="US-ASCII"

I think we have spent enough bits on this. I heard you all clear and it 
will stay 0. Julo



"Sankar, Ranga" <Ranga.Sankar@netapp.com> 
Sent by: owner-ips@ece.cmu.edu
22/02/03 15:25

To
"Andre Hedrick" <andre@linux-ide.org>, Julian Satran/Haifa/IBM@IBMIL
cc
"Wysochanski, David" <David.Wysochanski@netapp.com>, <ips@ece.cmu.edu>, 
<owner-ips@ece.cmu.edu>, "dl-iscsi-eng" <dl-iscsi-eng@netapp.com>
Subject
RE: iSCSI: version number






The RFC to be, still has not decided to go with version 1.
Also i believe that the IETF does not have a rule that requires 
the version to start with 1 after ratification. It is left
to the working group to decide on the version number.

Having gone thru the Interoperability issues in  the Plugfests,
i feel we should not change the version without a strong reason.

-ranga


-----Original Message-----
From: Andre Hedrick [mailto:andre@linux-ide.org]
Sent: Saturday, February 22, 2003 2:39 AM
To: Julian Satran
Cc: Sankar, Ranga; Wysochanski, David; ips@ece.cmu.edu;
owner-ips@ece.cmu.edu
Subject: Re: iSCSI: version number



Those who are locked into version 0 will have issues with those who are
properly reporting and following the RFC, to be.  Those who chose not to
support dynamic loading of the version as a config option, fell short of
seeing the history here in IPS-Refecltor.  Those who are capable of
adjusting this reporting will be capable of forward and backwards
compatability.

Also, what is IETF rules for version numbers and the requirements imposed
upon formal ratification?

If those rules require a version number > 0, then there is no choice but
to follow and comply with the rules according to the supervisory body that
initiated the original ad-hoc and transformed to a formal WG.

Just my nickle of noise.


Andre Hedrick
LAD Storage Consulting Group

On Fri, 21 Feb 2003, Julian Satran wrote:

> There is no strong reason - it is only that all the people that have 
asked 
> for this vocally in the past are now silent.
> And if they keep being silent then it will stay at 0.
> 
> Julo
> 
> 
> 
> "Sankar, Ranga" <Ranga.Sankar@netapp.com> 
> Sent by: owner-ips@ece.cmu.edu
> 21/02/03 00:22
> 
> To
> <ips@ece.cmu.edu>
> cc
> Julian Satran/Haifa/IBM@IBMIL, "Wysochanski, David" 
> <David.Wysochanski@netapp.com>
> Subject
> Re: iSCSI: version number
> 
> 
> 
> 
> 
> 
> 
> Could we leave the version number as 0? Is there a strong reason to make 

> this 1? 
> -ranga 
> "Robert D. Russell" <rdr@io.iol.unh.edu> 
> 20/02/03 16:59 
>  To Julian Satran/Haifa/IBM@IBMIL 
> cc ips@ece.cmu.edu 
> Subject iSCSI: version number 
> 
> 
> 
> 
> Julian: 
> Now that draft 20 has been accepted as an IETF standard, 
> shouldn't the version number in section 10.12.4 be changed 
> to 0x01? 
> Thanks 
> Bob Russell 
> InterOperability Lab 
> University of New Hampshire 
> rdr@iol.unh.edu 
> 603-862-3774 
> 


--=_alternative 00206FC8C2256CD7_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">I think we have spent enough bits on
this. I heard you all clear and it will stay 0. Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Sankar, Ranga&quot;
&lt;Ranga.Sankar@netapp.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">22/02/03 15:25</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">&quot;Andre Hedrick&quot;
&lt;andre@linux-ide.org&gt;, Julian Satran/Haifa/IBM@IBMIL</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">&quot;Wysochanski, David&quot;
&lt;David.Wysochanski@netapp.com&gt;, &lt;ips@ece.cmu.edu&gt;, &lt;owner-ips@ece.cmu.edu&gt;,
&quot;dl-iscsi-eng&quot; &lt;dl-iscsi-eng@netapp.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: iSCSI: version number</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>The RFC to be, still has not decided to go with version
1.<br>
Also i believe that the IETF does not have a rule that requires <br>
the version to start with 1 after ratification. It is left<br>
to the working group to decide on the version number.<br>
<br>
Having gone thru the Interoperability issues in &nbsp;the Plugfests,<br>
i feel we should not change the version without a strong reason.<br>
<br>
-ranga<br>
<br>
<br>
-----Original Message-----<br>
From: Andre Hedrick [mailto:andre@linux-ide.org]<br>
Sent: Saturday, February 22, 2003 2:39 AM<br>
To: Julian Satran<br>
Cc: Sankar, Ranga; Wysochanski, David; ips@ece.cmu.edu;<br>
owner-ips@ece.cmu.edu<br>
Subject: Re: iSCSI: version number<br>
<br>
<br>
<br>
Those who are locked into version 0 will have issues with those who are<br>
properly reporting and following the RFC, to be. &nbsp;Those who chose
not to<br>
support dynamic loading of the version as a config option, fell short of<br>
seeing the history here in IPS-Refecltor. &nbsp;Those who are capable of<br>
adjusting this reporting will be capable of forward and backwards<br>
compatability.<br>
<br>
Also, what is IETF rules for version numbers and the requirements imposed<br>
upon formal ratification?<br>
<br>
If those rules require a version number &gt; 0, then there is no choice
but<br>
to follow and comply with the rules according to the supervisory body that<br>
initiated the original ad-hoc and transformed to a formal WG.<br>
<br>
Just my nickle of noise.<br>
<br>
<br>
Andre Hedrick<br>
LAD Storage Consulting Group<br>
<br>
On Fri, 21 Feb 2003, Julian Satran wrote:<br>
<br>
&gt; There is no strong reason - it is only that all the people that have
asked <br>
&gt; for this vocally in the past are now silent.<br>
&gt; And if they keep being silent then it will stay at 0.<br>
&gt; <br>
&gt; Julo<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; &quot;Sankar, Ranga&quot; &lt;Ranga.Sankar@netapp.com&gt; <br>
&gt; Sent by: owner-ips@ece.cmu.edu<br>
&gt; 21/02/03 00:22<br>
&gt; <br>
&gt; To<br>
&gt; &lt;ips@ece.cmu.edu&gt;<br>
&gt; cc<br>
&gt; Julian Satran/Haifa/IBM@IBMIL, &quot;Wysochanski, David&quot; <br>
&gt; &lt;David.Wysochanski@netapp.com&gt;<br>
&gt; Subject<br>
&gt; Re: iSCSI: version number<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; &nbsp; <br>
&gt; Could we leave the version number as 0? Is there a strong reason to
make <br>
&gt; this 1? <br>
&gt; -ranga <br>
&gt; &quot;Robert D. Russell&quot; &lt;rdr@io.iol.unh.edu&gt; <br>
&gt; 20/02/03 16:59 <br>
&gt; &nbsp;To Julian Satran/Haifa/IBM@IBMIL <br>
&gt; cc ips@ece.cmu.edu <br>
&gt; Subject iSCSI: version number <br>
&gt; &nbsp;<br>
&gt; &nbsp; <br>
&gt; <br>
&gt; <br>
&gt; Julian: <br>
&gt; Now that draft 20 has been accepted as an IETF standard, <br>
&gt; shouldn't the version number in section 10.12.4 be changed <br>
&gt; to 0x01? <br>
&gt; Thanks <br>
&gt; Bob Russell <br>
&gt; InterOperability Lab <br>
&gt; University of New Hampshire <br>
&gt; rdr@iol.unh.edu <br>
&gt; 603-862-3774 <br>
&gt; <br>
</tt></font>
<br>
--=_alternative 00206FC8C2256CD7_=--
