checking immediate data

To: "Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>
Subject: checking immediate data
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
Date: Thu, 7 Aug 2003 12:34:32 -0400
Content-Type: multipart/alternative;boundary="----_=_NextPart_001_01C35D01.C8042090"
Delivered-To: ips-outgoing@sos.ece.cmu.edu
Delivered-To: ips-outgoing@ece.cmu.edu
Delivered-To: ips@sos.ece.cmu.edu
Delivered-To: ips@ece.cmu.edu
Sender: owner-ips@ece.cmu.edu

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

Follow-Ups:
- Re: checking immediate data
  - From: "Julian Satran" <Julian_Satran@il.ibm.com>

Prev by Date: Re: StatSN and overlapped commands
Next by Date: Re: iSCSI/iWARP drafts and flow control
Prev by thread: [Fwd: Re: StatSN and overlapped commands]
Next by thread: Re: checking immediate data
Index(es):
- Date
- Thread

Home

Last updated: Fri Aug 08 02:19:25 2003
12802 messages in chronological order