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 h0SJM6m04955
	for ips-outgoing; Tue, 28 Jan 2003 14:22:06 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from lion.ninthwonder.com (lion.ninthwonder.com [151.199.66.147])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0SJM1W04947
	for <ips@ece.cmu.edu>; Tue, 28 Jan 2003 14:22:01 -0500 (EST)
Received: by lion.ninthwonder.com (Postfix, from userid 1021)
	id CC78330706; Tue, 28 Jan 2003 14:21:41 -0500 (EST)
Date: Tue, 28 Jan 2003 11:15:40 -0800 (PST)
From: Bill Studenmund <wrstuden@wasabisystems.com>
X-X-Sender:  <wrstuden@candlekeep.home-net.internetconnect.net>
To: Steve Senum <ssenum@cisco.com>
Cc: "Robert D. Russell" <rdr@io.iol.unh.edu>,
   Julian Satran <Julian_Satran@il.ibm.com>, <ips@ece.cmu.edu>
Subject: Re: iSCSI: keys/parameter dependence
In-Reply-To: <3E36A7B0.98D52B8D@cisco.com>
Message-ID: <Pine.NEB.4.33.0301281053480.642-100000@candlekeep.home-net.internetconnect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

On Tue, 28 Jan 2003, Steve Senum wrote:

> Bob Russell,
>
> I think allowing keys to be distributed over several PDUs
> breaks the curent CHAP authentication sequence.  Consider:
>
>     I->T: CHAP_A=<A1,A2...>
>
>     T->I: CHAP_A=<A> CHAP_I=<I> CHAP_C=<C>
>
>     I->T: CHAP_N=<N> CHAP_R=<R>
>     OR
>     I->T: CHAP_N=<N> CHAP_R=<R> CHAP_I=<I> CHAP_C=<C>
>
> The target does not know how many keys to expect,
> so it would not know when the step is complete.
>
> I don't really see the point of allowing this anyway,
> as the user can already spread keys out over several PDUs
> with the C (Continue) bit.

Note that for CHAP we shouldn't need the C bit, since even with
CHAP_[ICNR] in one PDU, it should be less than 8k.

I also agree that we should not relax security negotiations here. Keeping
them rigid helps them complete quickly and clearly.

> I would however like to the see the key ordering issue
> clarified in the final edit, if possible.

That would be good.

Take care,

Bill

