Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from newbox.ece.cmu.edu (localhost [127.0.0.1])
	by newbox.ece.cmu.edu (Cyrus v2.1.14) with LMTP; Thu, 07 Aug 2003 15:16:30 -0400
X-Sieve: CMU Sieve 2.2
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by newbox.ece.cmu.edu (Postfix) with ESMTP id 4B28432AA
	for <ipsml@ece.cmu.edu>; Thu,  7 Aug 2003 15:16:30 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id F16D086; Thu,  7 Aug 2003 15:16:29 -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 28CE993; Thu,  7 Aug 2003 15:16:25 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id D9D0C89DE; Thu,  7 Aug 2003 15:16:07 -0400 (EDT)
Delivered-To: ips-outgoing@sos.ece.cmu.edu
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id B9AB789DD
	for <ips-outgoing@sos.ece.cmu.edu>; Thu,  7 Aug 2003 15:16:07 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 75B7A8F; Thu,  7 Aug 2003 15:16:07 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 3948B91; Thu,  7 Aug 2003 15:16:07 -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 B080486
	for <ips-outgoing@ece.cmu.edu>; Thu,  7 Aug 2003 15:16:04 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 7818789DF; Thu,  7 Aug 2003 15:16:04 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 6FB4089DD
	for <ips@sos.ece.cmu.edu>; Thu,  7 Aug 2003 15:16:02 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 93BF2FD; Thu,  7 Aug 2003 15:16:01 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 67472FF; Thu,  7 Aug 2003 15:16:01 -0400 (EDT)
Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id E9936FA
	for <ips@ece.cmu.edu>; Thu,  7 Aug 2003 15:15:55 -0400 (EDT)
Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237])
	by msgbas2x.cos.agilent.com (Postfix) with ESMTP
	id 5F76D392; Thu,  7 Aug 2003 13:15:55 -0600 (MDT)
Received: from wcosbh22.cos.agilent.com (wcosbh22.cos.agilent.com [130.29.152.178])
	by relcos2.cos.agilent.com (Postfix) with ESMTP
	id 3425E5D; Thu,  7 Aug 2003 13:15:55 -0600 (MDT)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: RE: StatSN and overlapped commands
Date: Thu, 7 Aug 2003 13:15:54 -0600
Message-ID: <1BEBA5E8600DD4119A50009027AF54A0132E0492@axcs04.cos.agilent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: StatSN and overlapped commands
Thread-Index: AcNccv2GCq+83chhEde69ACQJ0BKSgAn/yDw
From: <pat_thaler@agilent.com>
To: <wrstuden@wasabisystems.com>, <pkoning@equallogic.com>
Cc: <eddy_quicksall@ivivity.com>, <pat_thaler@agilent.com>,
	<satran@haifasphere.co.il>, <julian@cs.haifa.ac.il>,
	<Black_David@emc.com>, <dcuddihy@attotech.com>, <ips@ece.cmu.edu>
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-15.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,NO_REAL_NAME,QUOTED_EMAIL_TEXT
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

I agree with that approach as well.=20

It is valid for the target to still have the ITT in use until it gets =
the status acknoledgement. For instance, the target may need to do this =
when it supports data retransmission and there is still unacknowledged =
data for the command. If the initiator has a bug that causes it to =
duplicate ITT, the target MAY generate an error. It isn't necessary to =
call this case out explicitly.

Note that the initiator may reuse the ITT once the initiator has =
received the status. Therefore, a target might receive a PDU that has an =
ExpStatSN acknoledging receipt of a status message for a previous =
command where the new command has the same ITT as the previous command. =
If the target is checking for duplicate ITT, it must ensure that it =
clears away any ITTs for tasks acknowledged by the new PDU before it =
checks for duplicate ITT. This is just proper operation and I don't =
think we need to state this case explicitly either.

Pat

-----Original Message-----
From: wrstuden@wasabisystems.com [mailto:wrstuden@wasabisystems.com]
Sent: Wednesday, August 06, 2003 4:31 PM
To: Paul Koning
Cc: eddy_quicksall@ivivity.com; pat_thaler@agilent.com;
satran@haifasphere.co.il; julian@cs.haifa.ac.il; Black_David@emc.com;
dcuddihy@attotech.com; ips@ece.cmu.edu
Subject: RE: StatSN and overlapped commands


On Wed, 6 Aug 2003, Paul Koning wrote:

> Rather than clutter up the spec with more notes that say something is
> an error you can ignore, I'd rather keep it simple.
>
> I believe it's agreed that the case we're talking about is an
> initiator bug.
>
> Do we need to describe all possible bugs, and all allowed responses to
> such bugs?  I don't think so.  The spec should describe correct
> behavior, and required consistency checks.
>
> There's an infinite number of possible wrong behaviors that can be
> generated by bugs.  I believe this should just be covered by the
> standard *unwritten* rule that, if you mess up the protocol, you may
> not get the answer you were hoping for.

I'm happy with that too. My main concern, which you agree with, is to =
make
sure we don't say that this ITT re-use (w/o status ack) is something the
target MUST be happy with. Saying, "You get what you get," is fine.

Take care,

Bill
