Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h4LCOC306550
	for <ipsml@ece.cmu.edu>; Wed, 21 May 2003 08:24:12 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 68B8997; Wed, 21 May 2003 08:24:11 -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 9A7597E; Wed, 21 May 2003 08:23:55 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 4B6138953; Wed, 21 May 2003 08:23:38 -0400 (EDT)
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 38EE7893D
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 21 May 2003 08:23:38 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 045097B; Wed, 21 May 2003 08:23:38 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id B95BA8A; Wed, 21 May 2003 08:23:37 -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 E5AD07B
	for <ips-outgoing@ece.cmu.edu>; Wed, 21 May 2003 08:23:29 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id BC3A789D5; Wed, 21 May 2003 08:23:29 -0400 (EDT)
X-Original-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 DBC738953
	for <ips@sos.ece.cmu.edu>; Wed, 21 May 2003 08:23:27 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 5B4AA7E; Wed, 21 May 2003 08:23:27 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 289D687; Wed, 21 May 2003 08:23:27 -0400 (EDT)
Received: from mail.ivivity.com (unknown [64.238.111.99])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id 2B9717E
	for <ips@ece.cmu.edu>; Wed, 21 May 2003 08:23:18 -0400 (EDT)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <2CY0S05N>; Wed, 21 May 2003 08:23:13 -0400
Message-ID: <AEC4671C8179D61194DE0002B328BDD26A84AD@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: "Nicholas A. Bellinger" <nick@pyxtechnologies.com>,
   "Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>
Subject: RE: iSCSI: DataPDUInOrder=No Clairification
Date: Wed, 21 May 2003 08:23:01 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C31F93.B8AA2DC0"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-15.3 required=5.0
	tests=BAYES_01,HTML_60_70,HTML_FONT_COLOR_BLUE,
	      HTML_FONT_FACE_ODD,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_01C31F93.B8AA2DC0
Content-Type: text/plain

*       Sequence 0: Offsets: 65536->98304
> Sequence 1: Offsets: 32768->65536
> Sequence 2: Offsets: 98304->131072
> Sequence 3: Offsets: 0->32768
 
This shows overlap of offsets 98304, 65536 and 32768. Did you intend for
that to be part of the example?
 
Eddy
 
-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com] 
Sent: Wednesday, May 21, 2003 7:39 AM
To: Nicholas A. Bellinger
Cc: Andre Hedrick; David Black; Mallikarjun Chadalapaka; IPS MailingList
Subject: Re: iSCSI: DataPDUInOrder=No Clairification
 

Dear Nicholas, 


"Nicholas A. Bellinger" <nick@pyxtechnologies.com> wrote on 21/05/2003
12:48:15:

> [This is a resend due to mailer problems, please excuse any duplicates.]
> 
> Greeting all,
> 
>    I am inquiring about the author's intent and proper usage of
> DataPDUInOrder=No.  Of course the definition of the aforementioned
> parameter is defined in section 12.18:
> 
> "No is used by iSCSI to indicate that the data PDUs within sequences 
>  can be in any order."
> 
> I had originally used the interpretation that it was mainly designed to
> aid within-command recovery in the following DataOUT (not excluding
> DataIN) example:
> 
> When a DataOut PDU fails a Data Checksum, DataPDUInOrder=No allows the
> target to continue to receive the rest of the DataOut sequence without
> having to discard PDUs received after the initial failure.  Hence,
> the Recovery R2T only has to contain Failed Offset + Failed PDU Length.
> 
> This compared to the same example with DataPDUInOrder=Yes:
> 
> When a DataOut PDU fails a Data Checksum, DataPDUInOrder=Yes requires
> the target to NOT acknowledge the any futher PDUs in the DataOut
> sequence until the initial failure is recovered.  Hence, the Recovery
> R2T must contain Failed Offset -> Length to end of Sequence.
> 
> This type of example seems like the most logical application of
> DataPDUInOrder=No, that is one assumes the pdus in a given sequence will
> be still sent in increasing order.  If an error occurs one is allowed to
> continue to receieve pdus out of order and request only the missing
> ones.
> 
> Now let us consider another more unorthadox (and perhaps a bit
> illogical) example:
> 
> Consider a DataOUT Sequence of 32k, interpreting the definition in
> section 12.18 can one assume the following is legal?
> 
> Initiator -> Target
> 
> DataSN: 0, Offset: 24576, Length: 8192
> DataSN: 1, Offset: 0, Length: 8192
> DataSN: 2, Offset: 16384, Length: 8192
> DataSN: 3, Offset: 8192, Length: 8192
> 
This is indeed legal 

> This type of example assumes the pdus in a given sequence may be sent in
> any order, and the target handles the metadata for each pdu.  If this is
> indeed legal, then its safe to assume the following 128k DataIN example
> for DataSequenceInOrder=No is legal as well:
> 
> Target -> Initiator
> 
> Sequence 0: Offsets: 65536->98304
> Sequence 1: Offsets: 32768->65536
> Sequence 2: Offsets: 98304->131072
> Sequence 3: Offsets: 0->32768
> 
> My guess is these both are indeed legal.
> 

Yes they are legal. 

The stricter sequencing requirement is not there to avoid recovery but
rather to enable devices to optimize 
transmission in face of "mechanical" delay and lack of resources. 

> Thanks,
> -- 
> Nicholas A. Bellinger <nick@pyxtechnologies.com>
> 

------_=_NextPart_001_01C31F93.B8AA2DC0
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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@01C31F72.2EBC48D0">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"time"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<!--[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]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@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;}
tt
	{font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
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;}
@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;}
 /* List Definitions */
 @list l0
	{mso-list-id:36246937;
	mso-list-type:hybrid;
	mso-list-template-ids:1858628712 71874766 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Courier New";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><tt><font size=3D2 =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;mso-fareast-font-family:=
Wingdings;
mso-bidi-font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=D8<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font></tt><![endif]><tt><font size=3D2
face=3D"Courier New"><span style=3D'font-size:10.0pt'>Sequence 0: =
Offsets:
65536-&gt;98304</span></font></tt><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">&gt; Sequence 1: Offsets: =
32768-&gt;65536</font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 2: Offsets: =
98304-&gt;131072</font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 3: Offsets: =
0-&gt;32768<o:p></o:p></font></tt></span></font></p>

<p class=3DMsoNormal><tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></tt></p>

<p class=3DMsoNormal><tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>This shows overlap of offsets 98304, 65536 and 32768. Did you =
intend
for that to be part of the example?<o:p></o:p></span></font></tt></p>

<p class=3DMsoNormal><tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></tt></p>

<p class=3DMsoNormal><tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Eddy</span></font></tt><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><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> Julian Satran
[mailto:Julian_Satran@il.ibm.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> =
</span></font><st1:date
Month=3D"5" Day=3D"21" Year=3D"2003"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
 10.0pt;font-family:Tahoma'>Wednesday, May 21, =
2003</span></font></st1:date><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> </span></font><st1:time
Hour=3D"7" Minute=3D"39"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
 font-family:Tahoma'>7:39 AM</span></font></st1:time><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>To:</span></b> Nicholas A. =
Bellinger<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Andre Hedrick; David =
Black;
Mallikarjun Chadalapaka; IPS MailingList<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: iSCSI: =
DataPDUInOrder=3DNo
Clairification</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'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'>Dear Nicholas,</span></font> <br>
<br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&quot;Nicholas
A. Bellinger&quot; &lt;nick@pyxtechnologies.com&gt; wrote on =
</span></font></tt><st1:date
Month=3D"5" Day=3D"21" Year=3D"2003"><tt><font size=3D2 face=3D"Courier =
New"><span
 =
style=3D'font-size:10.0pt'>21/05/2003</span></font></tt></st1:date><tt><=
font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'> =
12:48:15:</span></font></tt><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt;font-famil=
y:"Courier New"'><br>
<br>
<tt><font face=3D"Courier New">&gt; [This is a resend due to mailer =
problems,
please excuse any duplicates.]</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Greeting all,</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; &nbsp; &nbsp;I am inquiring about =
the
author's intent and proper usage of</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataPDUInOrder=3DNo. &nbsp;Of =
course the
definition of the aforementioned</font></tt><br>
<tt><font face=3D"Courier New">&gt; parameter is defined in section =
12.18:</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; &quot;No is used by iSCSI to =
indicate that
the data PDUs within sequences </font></tt><br>
<tt><font face=3D"Courier New">&gt; &nbsp;can be in any =
order.&quot;</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; I had originally used the =
interpretation that
it was mainly designed to</font></tt><br>
<tt><font face=3D"Courier New">&gt; aid within-command recovery in the =
following
DataOUT (not excluding</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataIN) example:</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; When a DataOut PDU fails a Data =
Checksum,
DataPDUInOrder=3DNo allows the</font></tt><br>
<tt><font face=3D"Courier New">&gt; target to continue to receive the =
rest of the
DataOut sequence without</font></tt><br>
<tt><font face=3D"Courier New">&gt; having to discard PDUs received =
after the
initial failure. &nbsp;Hence,</font></tt><br>
<tt><font face=3D"Courier New">&gt; the Recovery R2T only has to =
contain Failed
Offset + Failed PDU Length.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; This compared to the same example =
with
DataPDUInOrder=3DYes:</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; When a DataOut PDU fails a Data =
Checksum,
DataPDUInOrder=3DYes requires</font></tt><br>
<tt><font face=3D"Courier New">&gt; the target to NOT acknowledge the =
any futher
PDUs in the DataOut</font></tt><br>
<tt><font face=3D"Courier New">&gt; sequence until the initial failure =
is
recovered. &nbsp;Hence, the Recovery</font></tt><br>
<tt><font face=3D"Courier New">&gt; R2T must contain Failed Offset =
-&gt; Length
to end of Sequence.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; This type of example seems like the =
most
logical application of</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataPDUInOrder=3DNo, that is one =
assumes the
pdus in a given sequence will</font></tt><br>
<tt><font face=3D"Courier New">&gt; be still sent in increasing order. =
&nbsp;If
an error occurs one is allowed to</font></tt><br>
<tt><font face=3D"Courier New">&gt; continue to receieve pdus out of =
order and
request only the missing</font></tt><br>
<tt><font face=3D"Courier New">&gt; ones.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Now let us consider another more =
unorthadox
(and perhaps a bit</font></tt><br>
<tt><font face=3D"Courier New">&gt; illogical) example:</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Consider a DataOUT Sequence of 32k,
interpreting the definition in</font></tt><br>
<tt><font face=3D"Courier New">&gt; section 12.18 can one assume the =
following is
legal?</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Initiator -&gt; =
Target</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; DataSN: 0, Offset: 24576, Length: =
8192</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataSN: 1, Offset: 0, Length: =
8192</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataSN: 2, Offset: 16384, Length: =
8192</font></tt><br>
<tt><font face=3D"Courier New">&gt; DataSN: 3, Offset: 8192, Length: =
8192</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt></span></font><br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>This is
indeed legal</span></font></tt> <br>
<font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">&gt; This type of example assumes the =
pdus in a
given sequence may be sent in</font></tt><br>
<tt><font face=3D"Courier New">&gt; any order, and the target handles =
the
metadata for each pdu. &nbsp;If this is</font></tt><br>
<tt><font face=3D"Courier New">&gt; indeed legal, then its safe to =
assume the
following 128k DataIN example</font></tt><br>
<tt><font face=3D"Courier New">&gt; for DataSequenceInOrder=3DNo is =
legal as well:</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Target -&gt; =
Initiator</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 0: Offsets: =
65536-&gt;98304</font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 1: Offsets: =
32768-&gt;65536</font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 2: Offsets: =
98304-&gt;131072</font></tt><br>
<tt><font face=3D"Courier New">&gt; Sequence 3: Offsets: =
0-&gt;32768</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; My guess is these both are indeed =
legal.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt></span></font><br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Yes they are
legal.</span></font></tt> <br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>The stricter
sequencing requirement is not there to avoid recovery but rather to =
enable
devices to optimize</span></font></tt> <br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>transmission
in face of &quot;mechanical&quot; delay and lack of =
resources.</span></font></tt>
<br>
<font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">&gt; Thanks,</font></tt><br>
<tt><font face=3D"Courier New">&gt; -- </font></tt><br>
<tt><font face=3D"Courier New">&gt; Nicholas A. Bellinger
&lt;nick@pyxtechnologies.com&gt;</font></tt><br>
<tt><font face=3D"Courier New">&gt; =
</font></tt></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C31F93.B8AA2DC0--
