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 h0967Rg21070
	for ips-outgoing; Thu, 9 Jan 2003 01:07:27 -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 h0967OW21065;
	Thu, 9 Jan 2003 01:07:24 -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 h0967Ibd018110;
	Thu, 9 Jan 2003 07:07:18 +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 h0967HTL022398;
	Thu, 9 Jan 2003 07:07:17 +0100
X-Priority: 1 (High)
In-Reply-To: <277DD60FB639D511AC0400B0D068B71E0564C713@corpmx14.us.dg.com>
To: Black_David@emc.com
Cc: Black_David@emc.com, ips@ece.cmu.edu, Nick.Martin@hp.com,
   owner-ips@ece.cmu.edu
Subject: RE: iSCSI extension algorithms (was no subject)
MIME-Version: 1.0
Importance: High
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF886CE3AA.8A5FC802-ONC2256CA9.00200069-C2256CA9.0021A089@telaviv.ibm.com>
Date: Thu, 9 Jan 2003 08:07:16 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 09/01/2003 08:07:17,
	Serialize complete at 09/01/2003 08:07:17
Content-Type: multipart/alternative; boundary="=_alternative 0020FB7AC2256CA9_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This is a multipart message in MIME format.
--=_alternative 0020FB7AC2256CA9_=
Content-Type: text/plain; charset="US-ASCII"

Steve and David,

I think that Nick has a valid point.   The intent was to avoid having a 
new player forcing either the new thing or nothing.
But I think that the same can be achieved by saying "MUST be able to 
offer" which says that an administrator MAY configure it with an 
additional
authentication.

It looks like being a bit stronger than MUST IMPLEMENT because MUST 
IMPLEMENT does not require an implementation to offer two authentication 
methods together.

I would like to drive this to a conclusion (draft) by the end of this 
week.

Thanks,
Julo



Black_David@emc.com 
Sent by: owner-ips@ece.cmu.edu
09/01/03 00:25

To
Nick.Martin@hp.com, Black_David@emc.com
cc
ips@ece.cmu.edu
Subject
RE: iSCSI extension algorithms (was no subject)






Nick,

> I agree that an implementation which implements or includes only
> proprietary extension algorithm Z should be unacceptable.
> I am only questioning whether this paragraph acomplishes that goal.
> I am reading "offer" in the negotiation sense, not in the implemented
> feature set sense.

You're correct.  The "MUST implement" requirement for CHAP is elsewhere,
and applies no matter what; this paragraph is about negotiation when a
proprietary algorithm is involved.

> Although it makes little sense to me for the target which is configured
> with no CHAP secrets to "offer" CHAP during negotiation, I can accept it
> in this situation.  I would prefer to see implementation of CHAP listed
> as the requirement, rather than offering CHAP when it is not configured
> to work.

We'll keep that in mind in working out the final text.
 
> It seems now that it is not intended that to "offer" CHAP in negotiation 

> should be interpreted as an indication that CHAP is configured work.
> 
> I hope an implementation which can "offer" CHAP but does not implement
> CHAP, or one which can "offer" CHAP but does not allow CHAP to be
> configured by an administrator will also be unacceptable.

The former is definitely unacceptable, the latter should be - as far
as I'm concerned if the code is present but can't be used, it doesn't
count as implemented because I can't see evidence of the implementation
on the wire.

Thanks,
--David


--=_alternative 0020FB7AC2256CA9_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Steve and David,</font>
<br>
<br><font size=2 face="sans-serif">I think that Nick has a valid point.
&nbsp; The intent was to avoid having a new player forcing either the new
thing or nothing.</font>
<br><font size=2 face="sans-serif">But I think that the same can be achieved
by saying &quot;MUST be able to offer&quot; which says that an administrator
MAY configure it with an additional</font>
<br><font size=2 face="sans-serif">authentication.</font>
<br>
<br><font size=2 face="sans-serif">It looks like being a bit stronger than
MUST IMPLEMENT because MUST IMPLEMENT does not require an implementation
to offer two authentication methods together.</font>
<br>
<br><font size=2 face="sans-serif">I would like to drive this to a conclusion
(draft) by the end of this week.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<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>Black_David@emc.com</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-ips@ece.cmu.edu</font>
<p><font size=1 face="sans-serif">09/01/03 00: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">Nick.Martin@hp.com, Black_David@emc.com</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</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">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: iSCSI extension algorithms
(was no subject)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Nick,<br>
<br>
&gt; I agree that an implementation which implements or includes only<br>
&gt; proprietary extension algorithm Z should be unacceptable.<br>
&gt; I am only questioning whether this paragraph acomplishes that goal.<br>
&gt; I am reading &quot;offer&quot; in the negotiation sense, not in the
implemented<br>
&gt; feature set sense.<br>
<br>
You're correct. &nbsp;The &quot;MUST implement&quot; requirement for CHAP
is elsewhere,<br>
and applies no matter what; this paragraph is about negotiation when a<br>
proprietary algorithm is involved.<br>
<br>
&gt; Although it makes little sense to me for the target which is configured<br>
&gt; with no CHAP secrets to &quot;offer&quot; CHAP during negotiation,
I can accept it<br>
&gt; in this situation. &nbsp;I would prefer to see implementation of CHAP
listed<br>
&gt; as the requirement, rather than offering CHAP when it is not configured<br>
&gt; to work.<br>
<br>
We'll keep that in mind in working out the final text.<br>
 <br>
&gt; It seems now that it is not intended that to &quot;offer&quot; CHAP
in negotiation <br>
&gt; should be interpreted as an indication that CHAP is configured work.<br>
&gt; <br>
&gt; I hope an implementation which can &quot;offer&quot; CHAP but does
not implement<br>
&gt; CHAP, or one which can &quot;offer&quot; CHAP but does not allow CHAP
to be<br>
&gt; configured by an administrator will also be unacceptable.<br>
<br>
The former is definitely unacceptable, the latter should be - as far<br>
as I'm concerned if the code is present but can't be used, it doesn't<br>
count as implemented because I can't see evidence of the implementation<br>
on the wire.<br>
<br>
Thanks,<br>
--David<br>
</tt></font>
<br>
--=_alternative 0020FB7AC2256CA9_=--
