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 11:29:26 -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 2CE5D3361
	for <ipsml@ece.cmu.edu>; Fri,  8 Aug 2003 11:29:26 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 99DCDB2; Fri,  8 Aug 2003 11:29:25 -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 9FBB287; Fri,  8 Aug 2003 11:29:04 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 44F5B89DD; Fri,  8 Aug 2003 11:28:49 -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 3336D8950
	for <ips-outgoing@sos.ece.cmu.edu>; Fri,  8 Aug 2003 11:28:49 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 05A047A; Fri,  8 Aug 2003 11:28:49 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id B9DB925; Fri,  8 Aug 2003 11:28:48 -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 0CA2993
	for <ips-outgoing@ece.cmu.edu>; Fri,  8 Aug 2003 11:28:30 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 5A4048950; Fri,  8 Aug 2003 11:28:28 -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 BECE089F6
	for <ips@sos.ece.cmu.edu>; Fri,  8 Aug 2003 11:28:24 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id CB8B48D; Fri,  8 Aug 2003 11:28:23 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 9805995; Fri,  8 Aug 2003 11:28:23 -0400 (EDT)
Received: from mail.ivivity.com (unknown [64.238.111.99])
	by hazard.ece.cmu.edu (Postfix) with ESMTP
	id 9B0D896; Fri,  8 Aug 2003 11:28:15 -0400 (EDT)
Received: by atlops.ivivity.com with Internet Mail Service (5.5.2653.19)
	id <QMWLWF9P>; Fri, 8 Aug 2003 11:28:15 -0400
Message-ID: <AEC4671C8179D61194DE0002B328BDD28580B5@atlops.ivivity.com>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: John Hufferd <hufferd@us.ibm.com>,
	Eddy Quicksall <eddy_quicksall@ivivity.com>
Cc: ips@ece.cmu.edu, owner-ips@ece.cmu.edu
Subject: RE: checking immediate data
Date: Fri, 8 Aug 2003 11:28:14 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C35DC1.AF1B9E80"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-14.8 required=5.0
	tests=BAYES_10,HTML_40_50,HTML_FONT_COLOR_BLUE,ORIGINAL_MESSAGE,
	      QUOTED_EMAIL_TEXT
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C35DC1.AF1B9E80
Content-Type: text/plain

John,
 
I also agree that this particular case is not a performance issue. 
 
I tried to indicate below that the premise of making this type of
requirement can be extended to many other cases and if the premise is
acceptable, where do you stop? (E.g., one person's flag may require a memory
access but another person's flag may not - don't forget also that the
performance path may be running in on chip memory that is small, so extra
code to support unnecessary requirements is not a good idea)? IMHO, a spec
should not make these kinds of statements in a performance path.
 
Eddy
 
-----Original Message-----
From: John Hufferd [mailto:hufferd@us.ibm.com] 
Sent: Friday, August 08, 2003 11:00 AM
To: Eddy Quicksall
Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu
Subject: RE: checking immediate data
 

Eddy, 
I guess I do not put this trivial immediate data check in the same league as
some of the other possible performance path checks.  I do not think that I
can be convinced that checking a "flag" that says that I can or can't accept
immediate data will impact the performance path.  And with that in mind, I
support David's comments.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/System Group, San Jose CA
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688
Alt Office: (408) 997-6136, Cell: (408) 499-9702
Internet Address: hufferd@us.ibm.com 



 
Eddy Quicksall <eddy_quicksall@ivivity.com> 
Sent by: owner-ips@ece.cmu.edu 
08/08/2003 06:34 AM 
        
        To:        Black_David@emc.com, Julian_Satran@il.ibm.com 
        cc:        ips@ece.cmu.edu 
        Subject:        RE: checking immediate data 



First, note that I realize it is too late to change this but I just want to
comment that using that rational, it would seem that the target should be
checking many other things that the initiator may do wrong. Obviously, that
would eventually effect performance; and this thinking is not consistent
with the consensus on another thread going on here regarding checking the
ITT for reuse.

In general, this kind of requirement should not appear in a performance
path.

Eddy

-----Original Message-----
From: Black_David@emc.com [mailto:Black_David@emc.com] 
Sent: Friday, August 08, 2003 9:26 AM
To: Julian_Satran@il.ibm.com; eddy_quicksall@ivivity.com
Cc: ips@ece.cmu.edu
Subject: RE: checking immediate data

Eddy and Julian

In the current specification, the target requirement also avoids
an interoperability problem if a broken initiator sends immediate
data that it has no business sending - since in the absence of the
requirement, target acceptance of the immediate data will be
implementation-dependent, the result is an annoying "sometimes
it works, sometimes it doesn't" situation.

It's better to have the initiator fail the first time it tries this
and get fixed, as opposed to building up an installed base where this
works when it shouldn't, as that would eventually cause removal of
the ImmediateData negotiation key, as targets would always have to
accept immediate data to deal with broken initiators who don't
know how not to send it.

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
----------------------------------------------------

> -----Original Message-----
> From: Julian Satran [mailto:Julian_Satran@il.ibm.com] 
> Sent: Friday, August 08, 2003 1:25 AM
> To: Eddy Quicksall
> Cc: Ips@Ece.Cmu.Edu (ips@ece.cmu.edu); owner-ips@ece.cmu.edu
> Subject: Re: checking immediate data
> 
> 
> 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
>  
> 



------_=_NextPart_001_01C35DC1.AF1B9E80
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C35DA0.26BB3760">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:"Times New Roman";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:auto;
	mso-font-signature:0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>John,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I also agree that this particular =
case is
not a performance issue. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I tried to indicate below that the =
premise
of making this type of requirement can be extended <span =
class=3DGramE>to</span>
many other cases and if the premise is acceptable, where do you stop? =
(E.g., one
person's flag may require a memory access but another person's flag
may not - don't forget also that the performance path may be
running in on chip memory that is small, so extra code to support =
unnecessary
requirements is not a good idea)? IMHO, a spec should not make these =
kinds of
statements in a performance path.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Eddy<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> John Hufferd
[mailto:hufferd@us.ibm.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, August 08, =
2003
11:00 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Eddy Quicksall<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> ips@ece.cmu.edu;
owner-ips@ece.cmu.edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: checking =
immediate
data</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Eddy,</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>I
guess I do not put this trivial immediate data check in the same league =
as some
of the other possible performance path checks. &nbsp;I do not think =
that I can
be convinced that checking a &quot;flag&quot; that says that I can or =
can't
accept immediate data will impact the performance path. &nbsp;And with =
that in
mind, I support David's comments.<br>
.<br>
.<br>
John L. Hufferd<br>
Senior Technical Staff Member (STSM)<br>
IBM/System Group, San Jose CA<br>
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688<br>
Alt Office: (408) 997-6136, Cell: (408) 499-9702<br>
Internet Address: hufferd@us.ibm.com</span></font> <br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%;mso-cellspacing:1.5pt;margin-left:.5in'>
 <tr style=3D'mso-yfti-irow:0;mso-yfti-lastrow:yes'>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><b><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
  7.5pt;font-family:sans-serif;font-weight:bold'>Eddy Quicksall
  &lt;eddy_quicksall@ivivity.com&gt;</span></font></b> <br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>Sent
  by: owner-ips@ece.cmu.edu</span></font> <o:p></o:p></p>
  <p><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:
  sans-serif'>08/08/2003 06:34 AM</span></font> <o:p></o:p></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:7.5pt;
  font-family:Arial'>&nbsp; &nbsp; &nbsp; &nbsp; </span></font><br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; =
&nbsp;Black_David@emc.com,
  Julian_Satran@il.ibm.com</span></font> <br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; =
&nbsp;ips@ece.cmu.edu</span></font>
  <br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;RE: checking
  immediate data</span></font> <o:p></o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
<br>
<br>
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>First, note that I realize it is too late to =
change
this but I just want to<br>
comment that using that rational, it would seem that the target should =
be<br>
checking many other things that the initiator may do wrong. Obviously, =
that<br>
would eventually effect performance; and this thinking is not =
consistent<br>
with the consensus on another thread going on here regarding checking =
the<br>
ITT for reuse.<br>
<br>
In general, this kind of requirement should not appear in a =
performance<br>
path.<br>
<br>
Eddy<br>
<br>
-----Original Message-----<br>
From: Black_David@emc.com [mailto:Black_David@emc.com] <br>
Sent: Friday, August 08, 2003 9:26 AM<br>
To: Julian_Satran@il.ibm.com; eddy_quicksall@ivivity.com<br>
Cc: ips@ece.cmu.edu<br>
Subject: RE: checking immediate data<br>
<br>
Eddy and Julian<br>
<br>
In the current specification, the target requirement also avoids<br>
an interoperability problem if a broken initiator sends immediate<br>
data that it has no business sending - since in the absence of the<br>
requirement, target acceptance of the immediate data will be<br>
implementation-dependent, the result is an annoying &quot;sometimes<br>
it works, sometimes it doesn't&quot; situation.<br>
<br>
It's better to have the initiator fail the first time it tries this<br>
and get fixed, as opposed to building up an installed base where =
this<br>
works when it shouldn't, as that would eventually cause removal of<br>
the ImmediateData negotiation key, as targets would always have to<br>
accept immediate data to deal with broken initiators who don't<br>
know how not to send it.<br>
<br>
Thanks,<br>
--David<br>
----------------------------------------------------<br>
David L. Black, Senior Technologist<br>
EMC Corporation, 176 South St., Hopkinton, MA &nbsp;01748<br>
+1 (508) 293-7953 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; FAX: +1 =
(508)
293-7786<br>
black_david@emc.com &nbsp; &nbsp; &nbsp; &nbsp;Mobile: +1 (978) =
394-7754<br>
----------------------------------------------------<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Julian Satran [mailto:Julian_Satran@il.ibm.com] <br>
&gt; Sent: Friday, August 08, 2003 1:25 AM<br>
&gt; To: Eddy Quicksall<br>
&gt; Cc: Ips@Ece.Cmu.Edu (ips@ece.cmu.edu); owner-ips@ece.cmu.edu<br>
&gt; Subject: Re: checking immediate data<br>
&gt; <br>
&gt; <br>
&gt; The reason beyond this was that a 'highly optimized target may =
have <br>
&gt; prepared already the R2T. I guess that you are objecting to <br>
&gt; the second <br>
&gt; MUST in the sentence &nbsp;and I guess that except for recovery it =
<br>
&gt; is a bit too <br>
&gt; strong. For recovery however you might end up having a <br>
&gt; different sequence <br>
&gt; in recovery vs. original.<br>
&gt; <br>
&gt; Regards,<br>
&gt; Julo<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Eddy Quicksall &lt;eddy_quicksall@ivivity.com&gt; <br>
&gt; Sent by: owner-ips@ece.cmu.edu<br>
&gt; 07/08/2003 19:34<br>
&gt; <br>
&gt; To<br>
&gt; &quot;Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)&quot; =
&lt;ips@ece.cmu.edu&gt;<br>
&gt; cc<br>
&gt; <br>
&gt; Subject<br>
&gt; checking immediate data<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Section 12.11 says:<br>
&gt; &nbsp;<br>
&gt; If ImmediateData is set to No and InitialR2T is set to Yes, then =
the<br>
&gt; initiator MUST NOT send unsolicited data and the target MUST =
reject<br>
&gt; unsolicited data with the corresponding response code.<br>
&gt; &nbsp;<br>
&gt; &nbsp;<br>
&gt; If the initiator says ImmediateData=3DNo and the target has the =
<br>
&gt; capability <br>
&gt; of taking immediate data BUT the initiator sends immediate <br>
&gt; data anyway, <br>
&gt; why should the target be responsible to make that check (as <br>
&gt; long as it <br>
&gt; isn't going to break the target)? <br>
&gt; &nbsp;<br>
&gt; Eddy<br>
&gt; &nbsp;<br>
&gt; <br style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C35DC1.AF1B9E80--
