FCP-3: Obsolete FCP_DL and FCP_BIDIRECTIONAL_DL

Bill Martin bill_martin at sierralogic.com
Fri Oct 1 09:30:03 PDT 2004


* From the T10 Reflector (t10 at t10.org), posted by:
* "Bill Martin" <bill_martin at sierralogic.com>
*
This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C4A799.3CE87A40
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

As an implementer that uses this field, we would object to removing it.
In addition to causing firmware changes, it will cause interoperability
problems until all instances of the firmware are changed (i.e. forever).

 

Bill Martin

Sr. Principal Engineer

Standards and Interoperability

Sierra Logic, Inc.

916 772-1234 x 112

bill_martin at sierralogic.com

  _____  

From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Robert
Snively
Sent: Thursday, September 30, 2004 2:49 PM
To: phil.colline at dothill.com; david_peterson at cnt.com
Cc: t10 at t10.org; t11_3 at mail.t11.org; Robert Snively
Subject: RE: FCP-3: Obsolete FCP_DL and FCP_BIDIRECTIONAL_DL

 

Phil reflects my original statement that the SCSI command set and its
data

counts are at a different architectural and implementation level than
the

FCP_DL.  The SCSI command set reflects a software-like understanding

between the application client and the device server about the length

of each logical block and the number of logical blocks.  The FCP_DL

reflects a hardware-like understanding of the number of bytes that

will flow to or from host memory hardware as FCP_DATA IUs for a

single exchange.  That hardware understanding is useful in setting up

and verifying the properties (including protection) of appropriate
buffers 

in both the host memory and the attached device.

 

I continue to believe that both these values are interesting and useful.

They provide important pieces of information to different levels of the

architecture.  They are especially useful to certain virtualization
implementations

that choose not to have a full understanding of the underlying data

properties.

 

Just because some hosts choose not to interpret the response codes

associated with errors does not mean that these are useless

parameters.  It simply adds another requirement for presenting

the information, like the one Dave has been preparing.

 

However, if all the HBA, RAID, and virtualizer implementers agree that

they no longer need FCP_DL for FCP devices, I would be swayed from

my position.  Note that Dot Hill is one of those RAID implementors, and

they seem to find the value useful. 

 

Bob

-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org]On Behalf Of
phil.colline at dothill.com
Sent: Thursday, September 30, 2004 1:31 PM
To: david_peterson at cnt.com
Cc: t10 at t10.org; t11_3 at mail.t11.org
Subject: Re: FCP-3: Obsolete FCP_DL and FCP_BIDIRECTIONAL_DL

I believe it would be a big mistake to obsolete FCP_DL.  The only other
way to determine the transfer size is to crack the payload (CDB) which
would put undue burden on hardware or software layers that currently
rely exclusively on FCP_DL.  While it is a true statement that the
FCP_DL is redundant with the CDB transfer length, forcing the many
existing implementations relying on FCP_DL to utilize the CDB instead
over an orthogonal issue is not the proper solution.  It also seems like
an invitation to renew a whole new set of interoperability problems.
 
Regards,
 
Phil
 
 
On Tue, 28 Sep 2004, David Peterson (Eng) wrote:
 
> * From the T10 Reflector ( t10 at t10.org <mailto:t10 at t10.org> ), posted
by:
> * "David Peterson \(Eng\)" < david_peterson at cnt.com
<mailto:david_peterson at cnt.com> >
> *
> Howdy All,
> 
> During the discussion of T10/03-393 at the recent CAP meeting the
notion
> of obsoleting the FCP_DL and FCP_BIDIRECTIONAL_READ_DL fields in FCP-3
> was mentioned.
> 
> A bit of history that got us to this point:
> 
> The FCP-3 working has been looking at an issue where the FCP_DL value
is
> not equal to the CDB transfer length. The goal is/was to provide a
> method to report this condition to the upper layer(s). The need for
this
> method drops significantly if the FCP_DL fields are obsolete. The
method
> may still have merit since there are other conditions such as the
WRDATA
> bit is set to one in a read type command and vice-versa. But no one
has
> really identified this is a problem case to date.
> 
> Additional reasons to obsolete such as "its redundent with the CDB
> transfer length" and "FCP is the only SCSI transport protocol that
> specifies a data length" have been mentioned.
> 
> Please indicate any preferences for or against obsoleting the FCP_DL
and
> FCP_BIDIRECTIONAL_DL fields along with your reasoning.
> 
> Thanks...Dave
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to  majordomo at t10.org
<mailto:majordomo at t10.org> 
> 
 

 


------=_NextPart_000_001F_01C4A799.3CE87A40
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
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 name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<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'>As an implementer that uses this =
field, we
would object to removing it.&nbsp; In addition to causing firmware =
changes, it
will cause interoperability problems until all instances of the =
firmware are
changed (i.e. forever).<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>=


<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Bill =
Martin<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'>Sr. Principal =
Engineer</span></font><font
color=3Dnavy><span style=3D'color:navy'><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'>Standards and =
Interoperability</span></font><font
color=3Dnavy><span style=3D'color:navy'><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'>Sierra Logic, =
Inc.<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'>916 772-1234 x =
112<o:p></o:p></span></font></p>

<p class=3DMsoNormal><u1:PersonName u2:st=3D"on"><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>bill_martin at sier=
ralogic.com</span></font></u1:PersonName><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></=
p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
owner-t10 at t10.org [mailto:owner-t10 at t10.org] <b><span =
style=3D'font-weight:bold'>On
Behalf Of </span></b>Robert Snively<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, =
September 30, 2004
2:49 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
phil.colline at dothill.com;
david_peterson at cnt.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> t10 at t10.org;
t11_3 at mail.t11.org; Robert Snively<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: FCP-3: =
Obsolete
FCP_DL and FCP_BIDIRECTIONAL_DL</span></font><o:p></o:p></p>

</div>

<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>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Phil reflects my original =
statement that
the SCSI command set and its data</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>counts are at a different =
architectural
and implementation level than the</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>FCP_DL.&nbsp; The SCSI command set
reflects a software-like understanding</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>between the application client and =
the
device server about the length</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>of each logical block and the =
number of
logical blocks.&nbsp; The FCP_DL</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>reflects a hardware-like =
understanding of
the number of bytes that</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>will flow to or from host memory =
hardware
as FCP_DATA IUs for a</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>single exchange.&nbsp; That =
hardware
understanding is useful in setting up</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>and verifying the properties =
(including
protection)&nbsp;of appropriate buffers </span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>in both the host memory and the =
attached
device.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I continue to believe that both =
these
values are interesting and useful.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>They provide important pieces of =
information
to different levels of the</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>architecture.&nbsp; They are =
especially
useful to certain virtualization =
implementations</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>that choose not to have a full
understanding of the underlying data</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>properties.</span></font><o:p></o:p=
></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Just because some hosts choose not =
to
interpret the response codes</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>associated with errors does not =
mean that
these are useless</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>parameters.&nbsp; It simply adds =
another
requirement for presenting</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>the information, like the one Dave =
has
been preparing.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>However, if all the HBA, RAID, and
virtualizer implementers agree that</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>they no longer need FCP_DL for FCP
devices, I would be swayed from</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>my position.&nbsp; Note that Dot =
Hill is
one of those RAID implementors, and</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>they seem to find the value =
useful.</span></font>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Bob</span></font><o:p></o:p></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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> owner-t10 at t10.org =
[mailto:owner-t10 at t10.org]<b><span
style=3D'font-weight:bold'>On Behalf Of =
</span></b>phil.colline at dothill.com<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, =
September 30, 2004
1:31 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
david_peterson at cnt.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> t10 at t10.org;
t11_3 at mail.t11.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: FCP-3: =
Obsolete
FCP_DL and FCP_BIDIRECTIONAL_DL</span></font><o:p></o:p></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>I believe it would be a big mistake to =
obsolete FCP_DL.&nbsp; The only other way to determine the transfer =
size is to crack the payload (CDB) which would put undue burden on =
hardware or software layers that currently rely exclusively on =
FCP_DL.&nbsp; While it is a true statement that the FCP_DL is redundant =
with the CDB transfer length, forcing the many existing implementations =
relying on FCP_DL to utilize the CDB instead over an orthogonal issue =
is not the proper solution.&nbsp; It also seems like an invitation to =
renew a whole new set of interoperability =
problems.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Regards,<o:p></o:p></span></font></pre><pre><=
font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Phil<o:p></o:p></span></font></pre><pre><font=

size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>On Tue, =
28 Sep 2004, David Peterson (Eng) =
wrote:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> * =
>From the T10 Reflector (<a
href=3D"mailto:t10 at t10.org">t10 at t10.org), posted =
by:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> * =
"David Peterson \(Eng\)" <<a
href=3D"mailto:david_peterson at cnt.com">david_peterson at cnt.com><o:=
p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
*<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
Howdy All,<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
During the discussion of T10/03-393 at the recent CAP meeting the =
notion<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> of =
obsoleting the FCP_DL and FCP_BIDIRECTIONAL_READ_DL fields in =
FCP-3<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> was =
mentioned.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> A =
bit of history that got us to this =
point:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> The =
FCP-3 working has been looking at an issue where the FCP_DL value =
is<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> not =
equal to the CDB transfer length. The goal is/was to provide =
a<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
method to report this condition to the upper layer(s). The need for =
this<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
method drops significantly if the FCP_DL fields are obsolete. The =
method<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> may =
still have merit since there are other conditions such as the =
WRDATA<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> bit =
is set to one in a read type command and vice-versa. But no one =
has<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
really identified this is a problem case to =
date.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
Additional reasons to obsolete such as "its redundent with the =
CDB<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
transfer length" and "FCP is the only SCSI transport protocol =
that<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
specifies a data length" have been =
mentioned.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
Please indicate any preferences for or against obsoleting the FCP_DL =
and<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
FCP_BIDIRECTIONAL_DL fields along with your =
reasoning.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
Thanks...Dave<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> =
*<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> * =
For T10 Reflector information, send a message =
with<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>> * =
'info t10' (no quotes) in the message body to <a
href=3D"mailto:majordomo at t10.org">majordomo at t10.org<o:p></o:p></span=
></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>><o:p>&nbsp;</o:p></span></font></pre><pre=
><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_001F_01C4A799.3CE87A40--




More information about the T10 mailing list