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 h0H0j9F12788
	for ips-outgoing; Thu, 16 Jan 2003 19:45:09 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from web13704.mail.yahoo.com (web13704.mail.yahoo.com [216.136.175.137])
	by ece.cmu.edu (8.11.0/8.10.2) with SMTP id h0H0j6W12783
	for <ips@ece.cmu.edu>; Thu, 16 Jan 2003 19:45:06 -0500 (EST)
Message-ID: <20030117004505.29713.qmail@web13704.mail.yahoo.com>
Received: from [192.52.57.33] by web13704.mail.yahoo.com via HTTP; Thu, 16 Jan 2003 16:45:05 PST
Date: Thu, 16 Jan 2003 16:45:05 -0800 (PST)
From: Martins Krikis <mkrikis@yahoo.com>
Subject: Re: iSCSI: using the C bit
To: Eddy Quicksall <eddy_quicksall@ivivity.com>, ips@ece.cmu.edu
In-Reply-To: <AEC4671C8179D61194DE0002B328BDD20B96@ATLOPS>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ips@ece.cmu.edu
Precedence: bulk


--- Eddy Quicksall <eddy_quicksall@ivivity.com> wrote:

> If this is done, the target will not process the
> partial key and may send
> his own key saying "ImmediateData=no". But, the
> initiator has already
> constructed the negotiation and request A+1 would
> violate the protocol
> because ImmediateData has already been negotiated.

Avoiding this kind of a scenario
is exactly why the C-bit got introduced.
One cannot send any data (DataSegmentLength must be 0)
until the other side clears the C-bit, thus allowing
it. C-bit basically says "let me finish speaking".

Martins Krikis, Intel Corp.





__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
