SAS-2 Channel Models

Fri Oct 28 19:18:14 PDT 2005

* From the T10 Reflector (t10 at t10.org), posted by:
* "Mike Jenkins" <jenkins at lsil.com>
*
This is a multi-part message in MIME format.

------=_NextPart_000_0204_01C5DBF4.581DD360
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

All,

A number of measured channel models have been uploaded recently.  This
information is valuable in the specification/budgeting process for 6
Gb/s, and I can imagine the amount of work it takes to procure such
data.  Hence, I don't bring this up lightly, but feel compelled to point
out that crosstalk (NEXT & FEXT) will also be an important part of the
budgeting process.  Several standards typically provide not only the S21
data (in .s4p format) for the forward channel, but also one or more NEXT
and FEXT transfer functions (also in .s4p format).  Lack of this
information may lead to a too optimistic estimate of the channel's
performance.

For example, I offer the document, T11/05-665v1
<http://www.t11.org/ftp/t11/pub/fc/pi-4/05-665v1.pdf> , presented during
the October Fibre Channel meetings which includes the NEXT and FEXT
files.

Regards,

Mike

------=_NextPart_000_0204_01C5DBF4.581DD360
Content-Type: text/html;
	charset="us-ascii"
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 name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* 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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@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 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All,<o:p></o:p></span></font></p>

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

A number of measured channel models have been =
uploaded
recently. &nbsp;This information is valuable in the =
specification/budgeting
process for 6 Gb/s, and I can imagine the amount of work it takes to =
procure
such data. &nbsp;Hence, I don&#8217;t bring this up lightly, but feel =
compelled
to point out that crosstalk (NEXT &amp; FEXT) will also be an important =
part of
the budgeting process. &nbsp;Several standards typically provide not =
only the
S21 data (in .s4p format) for the forward channel, but also one or more =
NEXT
and FEXT transfer functions (also in .s4p format). &nbsp;Lack of this
information may lead to a too optimistic estimate of the =
channel&#8217;s
performance.<o:p></o:p>

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

For example, I offer the document, <a
href=3D"http://www.t11.org/ftp/t11/pub/fc/pi-4/05-665v1.pdf">T11/05-665v=
1,
presented during the October Fibre Channel meetings which includes the =
NEXT and
FEXT files. &nbsp;<o:p></o:p>

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0204_01C5DBF4.581DD360--