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.12) with LMTP; Mon, 28 Jul 2003 16:46:49 -0400
X-Sieve: CMU Sieve 2.2
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by newbox.ece.cmu.edu (Postfix) with ESMTP id D5FFA31C4
	for <ipsml@ece.cmu.edu>; Mon, 28 Jul 2003 16:46:48 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 8DA5C121; Mon, 28 Jul 2003 16:46:48 -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 35119F9; Mon, 28 Jul 2003 16:46:46 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 554EC8A02; Mon, 28 Jul 2003 16:46:29 -0400 (EDT)
Delivered-To: ips-outgoing@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 3B5018A00
	for <ips-outgoing@sos.ece.cmu.edu>; Mon, 28 Jul 2003 16:46:29 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 203AA7B; Mon, 28 Jul 2003 16:46:29 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id E676268; Mon, 28 Jul 2003 16:46:28 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by bache.ece.cmu.edu (Postfix) with ESMTP id 0389D7C
	for <ips-outgoing@ece.cmu.edu>; Mon, 28 Jul 2003 16:46:25 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id C9B698A04; Mon, 28 Jul 2003 16:46:25 -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 AB63D8A00
	for <ips@sos.ece.cmu.edu>; Mon, 28 Jul 2003 16:46:24 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 79E62F5; Mon, 28 Jul 2003 16:46:24 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 4FBCD121; Mon, 28 Jul 2003 16:46:24 -0400 (EDT)
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.31.40])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 1C51BF5
	for <ips@ece.cmu.edu>; Mon, 28 Jul 2003 16:46:22 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <NQHSN2FY>; Mon, 28 Jul 2003 16:46:18 -0400
Message-ID: <277DD60FB639D511AC0400B0D068B71E0C24678D@corpmx14.us.dg.com>
From: Black_David@emc.com
To: mako@almaden.ibm.com
Cc: ips@ece.cmu.edu
Subject: RE: iSCSI/iWARP drafts and flow control
Date: Mon, 28 Jul 2003 16:35:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-15.1 required=5.0
	tests=BAYES_01,NO_REAL_NAME,ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

> David, on your suggestion on "specifying a non-negotiable limit on the 
> number that can be outstanding", is that with the WG chair hat on?

I'm not sure that matters, as this is not a WG draft, but for
consistency, consider it to be with WG Chair hat on, but note that
I phrased it as advisory (fixed non-negotiable limit in specification
would be an acceptable way to address this issue).

Thanks,
--David

-----Original Message-----
From: Mike Ko [mailto:mako@almaden.ibm.com] 
Sent: Monday, July 28, 2003 1:32 PM
To: Black_David@emc.com
Cc: ips@ece.cmu.edu
Subject: RE: iSCSI/iWARP drafts and flow control


David, on your suggestion on "specifying a non-negotiable limit on the 
number that can be outstanding", is that with the WG chair hat on?

Mike Ko
IBM Almaden Research
San Jose, CA 95120

Sent by:        owner-ips@ece.cmu.edu
To:     elliott@hp.com, ips@ece.cmu.edu
cc: 
Subject:        RE: iSCSI/iWARP drafts and flow control



Rob,

> Note that SCSI asynchronous events were declared obsolete by
> T10 in November 2002 and have not been documented in SCSI
> Architecture Model - 3 (SAM-3) since revision 3 (the latest
> revision is 8).

iSCSI is based on SAM-2, which includes SCSI asynchronous events,
and moving it to SAM-3 is going to involve other changes (e.g.,
to task management).  That's not planned to happen any time soon,
but the fact that T10 considers SCSI asynchronous events obsolete
is more than adequate justification for specifying a non-negotiable
limit on the number that can be outstanding.

Also, let me caution everyone that the iSER and DA drafts are not
approved work items of the IP Storage WG.  Since they're related to
iSCSI, I suppose discussion on this list is ok, but I have no idea
if or when they may become drafts that this WG works on.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

