Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h1LFMpI29943 for ips-outgoing; Fri, 21 Feb 2003 10:22:51 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from mx01.netapp.com (mx01.netapp.com [198.95.226.53]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h1KMMhW02051 for ; Thu, 20 Feb 2003 17:22:43 -0500 (EST) Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01.netapp.com (8.12.6/8.12.6/NTAP-1.4) with ESMTP id h1KMMaeZ006616; Thu, 20 Feb 2003 14:22:36 -0800 (PST) Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.10.22.171]) by frejya.corp.netapp.com (8.12.6/8.12.6/NTAP-1.4) with ESMTP id h1KMMZM6023908; Thu, 20 Feb 2003 14:22:36 -0800 (PST) Received: from rtpexc01.hq.netapp.com ([10.60.4.46]) by svlexc01.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 20 Feb 2003 14:22:35 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2D92E.90B75AC3" Subject: Re: iSCSI: version number Date: Thu, 20 Feb 2003 17:22:33 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: iSCSI: version number Thread-Index: AcLZLpDDfNXLy0UkRhKZk9f4XaSzzA== From: "Sankar, Ranga" To: Cc: , "Wysochanski, David" X-OriginalArrivalTime: 20 Feb 2003 22:22:35.0162 (UTC) FILETIME=[9170FFA0:01C2D92E] Sender: owner-ips@ece.cmu.edu Precedence: bulk This is a multi-part message in MIME format. ------_=_NextPart_001_01C2D92E.90B75AC3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 Could we leave the version number as 0? Is there a strong reason to make = this 1? -ranga "Robert D. Russell" =20 20/02/03 16:59=20 To Julian Satran/Haifa/IBM@IBMIL =20 cc ips@ece.cmu.edu =20 Subject iSCSI: version number=20 =20 =20 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 ------_=_NextPart_001_01C2D92E.90B75AC3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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

------_=_NextPart_001_01C2D92E.90B75AC3--