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 h046LeV27667
	for ips-outgoing; Sat, 4 Jan 2003 01:21:40 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from d12lmsgate-3.de.ibm.com (d12lmsgate-3.de.ibm.com [194.196.100.236])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h046LYW27662;
	Sat, 4 Jan 2003 01:21:34 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-3.de.ibm.com (8.12.3/8.12.3) with ESMTP id h046LSMP014434;
	Sat, 4 Jan 2003 07:21:28 +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 h046LQL9273846;
	Sat, 4 Jan 2003 07:21:26 +0100
In-Reply-To: <OFA32A39BB.62B687D4-ON87256CA2.006D8820-07256CA2.00715F56@us.ibm.com>
To: "Russell Lewis" <russelll@us.ibm.com>
Cc: ips@ece.cmu.edu, owner-ips@ece.cmu.edu
Subject: Re: iSCSI: Extension Keys in Discovery Mode
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OFAA6B7847.40C55F27-ONC2256CA4.002178CE-C2256CA4.0022EB82@telaviv.ibm.com>
Date: Sat, 4 Jan 2003 08:21:24 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 04/01/2003 08:21:27,
	Serialize complete at 04/01/2003 08:21:27
Content-Type: multipart/alternative; boundary="=_alternative 0021CA69C2256CA4_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

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

Yes it means what it says.
We wanted to limit the number of keys that can be used during discovery 
and to limit discovery to a minimum.
Many of us also felt that "discover" in the management sense should be 
approached with a different mechanism and
leverage commonality with other service discovery mechanisms.

Julo



Russell Lewis/Tucson/IBM@IBMUS 
Sent by: owner-ips@ece.cmu.edu
02/01/03 22:50

To
ips@ece.cmu.edu
cc

Subject
iSCSI: Extension Keys in Discovery Mode










I'm looking at spec 0.19, section 12.22, and it says "Vendor specific keys
MUST ONLY be used in normal sessions."

1) Am I correct that it means that it is also illegal to pass vendor
specific keys during LOGIN if the session is going to be Discovery?
2) Does anybody know why this requirement is in the spec?

Thanks,
Russ Lewis



--=_alternative 0021CA69C2256CA4_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Yes it means what it says.</font>
<br><font size=2 face="sans-serif">We wanted to limit the number of keys
that can be used during discovery and to limit discovery to a minimum.</font>
<br><font size=2 face="sans-serif">Many of us also felt that &quot;discover&quot;
in the management sense should be approached with a different mechanism
and</font>
<br><font size=2 face="sans-serif">leverage commonality with other service
discovery mechanisms.</font>
<br>
<br><font size=2 face="sans-serif">Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Russell Lewis/Tucson/IBM@IBMUS</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-ips@ece.cmu.edu</font>
<p><font size=1 face="sans-serif">02/01/03 22:50</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">ips@ece.cmu.edu</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: Extension Keys in
Discovery Mode</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
<br>
<br>
I'm looking at spec 0.19, section 12.22, and it says &quot;Vendor specific
keys<br>
MUST ONLY be used in normal sessions.&quot;<br>
<br>
1) Am I correct that it means that it is also illegal to pass vendor<br>
specific keys during LOGIN if the session is going to be Discovery?<br>
2) Does anybody know why this requirement is in the spec?<br>
<br>
Thanks,<br>
Russ Lewis<br>
<br>
</tt></font>
<br>
--=_alternative 0021CA69C2256CA4_=--