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; Fri, 08 Aug 2003 01:26:45 -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 B444F3216
	for <ipsml@ece.cmu.edu>; Fri,  8 Aug 2003 01:26:45 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 37F89A2; Fri,  8 Aug 2003 01:26:45 -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 3497499; Fri,  8 Aug 2003 01:26:37 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 1D95D89E0; Fri,  8 Aug 2003 01:26:21 -0400 (EDT)
Delivered-To: ips-outgoing@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 0C70189DF
	for <ips-outgoing@sos.ece.cmu.edu>; Fri,  8 Aug 2003 01:26:21 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 8C24E91; Fri,  8 Aug 2003 01:26:20 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 0F2558D; Fri,  8 Aug 2003 01:26:20 -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 4B2F8C5
	for <ips-outgoing@ece.cmu.edu>; Fri,  8 Aug 2003 01:25:10 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 1C69C89E7; Fri,  8 Aug 2003 01:25:10 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@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 7357D89E0
	for <ips@sos.ece.cmu.edu>; Fri,  8 Aug 2003 01:25:08 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 9037388; Fri,  8 Aug 2003 01:25:07 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id D6EC07E; Fri,  8 Aug 2003 01:25:06 -0400 (EDT)
Received: from d12lmsgate-5.de.ibm.com (d12lmsgate-5.de.ibm.com [194.196.100.238])
	by osgood.ece.cmu.edu (Postfix) with ESMTP
	id BBDDE83; Fri,  8 Aug 2003 01:25:04 -0400 (EDT)
Received: from d12relay02.megacenter.de.ibm.com (d12relay02.megacenter.de.ibm.com [9.149.165.196])
	by d12lmsgate-5.de.ibm.com (8.12.9/8.12.8) with ESMTP id h785Ox9e104930;
	Fri, 8 Aug 2003 07:25:00 +0200
Received: from d10ml001.telaviv.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12relay02.megacenter.de.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h785OwFg288418;
	Fri, 8 Aug 2003 07:24:59 +0200
In-Reply-To: <AEC4671C8179D61194DE0002B328BDD285804F@atlops.ivivity.com>
To: Eddy Quicksall <eddy_quicksall@ivivity.com>
Cc: "Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>,
	owner-ips@ece.cmu.edu
Subject: Re: checking immediate data
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF165388EF.34049EE5-ONC2256D7C.001B8763-C2256D7C.001DBD9C@telaviv.ibm.com>
Date: Fri, 8 Aug 2003 08:24:51 +0300
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 08/08/2003 08:24:59,
	Serialize complete at 08/08/2003 08:24:59
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,IN_REP_TO
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

The reason beyond this was that a 'highly optimized target may have 
prepared already the R2T. I guess that you are objecting to the second 
MUST in the sentence  and I guess that except for recovery it is a bit too 
strong. For recovery however you might end up having a different sequence 
in recovery vs. original.

Regards,
Julo



Eddy Quicksall <eddy_quicksall@ivivity.com> 
Sent by: owner-ips@ece.cmu.edu
07/08/2003 19:34

To
"Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>
cc

Subject
checking immediate data






Section 12.11 says:
 
If ImmediateData is set to No and InitialR2T is set to Yes, then the
initiator MUST NOT send unsolicited data and the target MUST reject
unsolicited data with the corresponding response code.
 
 
If the initiator says ImmediateData=No and the target has the capability 
of taking immediate data BUT the initiator sends immediate data anyway, 
why should the target be responsible to make that check (as long as it 
isn't going to break the target)? 
 
Eddy
 

