Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h5OJkQY26827
	for <ipsml@ece.cmu.edu>; Tue, 24 Jun 2003 15:46:26 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 1B13D79; Tue, 24 Jun 2003 15:46:26 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP
	id 175DE70; Tue, 24 Jun 2003 15:46:24 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 355D489EB; Tue, 24 Jun 2003 15:46:11 -0400 (EDT)
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 215F089EA
	for <ips-outgoing@sos.ece.cmu.edu>; Tue, 24 Jun 2003 15:46:11 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id E0E1F6E; Tue, 24 Jun 2003 15:46:10 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id B628B7A; Tue, 24 Jun 2003 15:46:10 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id D54BF6E
	for <ips-outgoing@ece.cmu.edu>; Tue, 24 Jun 2003 15:46:08 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id AA56A89EC; Tue, 24 Jun 2003 15:46:08 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id DACFA89EA
	for <ips@sos.ece.cmu.edu>; Tue, 24 Jun 2003 15:46:06 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 5044B7C; Tue, 24 Jun 2003 15:46:06 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id 2C04784; Tue, 24 Jun 2003 15:46:06 -0400 (EDT)
Received: from mononoke.wasabisystems.com (saway.wasabisystems.com [151.199.66.145])
	by bache.ece.cmu.edu (Postfix) with ESMTP id E9DBB7C
	for <ips@ece.cmu.edu>; Tue, 24 Jun 2003 15:46:00 -0400 (EDT)
Received: by mononoke.wasabisystems.com (Postfix, from userid 1021)
	id 940DC40136; Tue, 24 Jun 2003 15:46:00 -0400 (EDT)
Date: Tue, 24 Jun 2003 12:45:41 -0700 (PDT)
From: wrstuden@wasabisystems.com
X-X-Sender: wrstuden@neverwinter.home-net.icnt.net
To: Abhijit Lahiri <abhijit_lahiri@yahoo.com>
Cc: ips@ece.cmu.edu, supriyo_p2003@yahoo.com
Subject: Re: Clarification requested on iscsi-draft-20 w.r.t target behavior
 on error conditions
In-Reply-To: <20030624141213.59998.qmail@web41409.mail.yahoo.com>
Message-ID: <Pine.NEB.4.53.0306241240100.796@neverwinter.home-net.icnt.net>
References: <20030624141213.59998.qmail@web41409.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-33.8 required=5.0
	tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,NO_REAL_NAME,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE
	autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

On Tue, 24 Jun 2003, Abhijit Lahiri wrote:

> The draft does not seem to be explicit about an ISCSI
> target's behavior on encountering the following error
> conditions.

[snip]

> 6. If NOP-Out ping request is sent in response to a
>    a NOP-In ping request

?? What do you have in mind with this one? From my read, it is legitemate
for a NOP-OUT to have both a TTT (indicating it is in response to a
NOP-IN) and an ITT (indicating that the targt is to send a NOP-IN in
response to the NOP-OUT). Though since it'd be in response to a NOP-IN, I
think there should be no data payload (as the initial NOP-IN had no data
payload :-)

Take care,

Bill
