<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18783"><!--[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-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
P.MsoNoSpacing {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 1
}
LI.MsoNoSpacing {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 1
}
DIV.MsoNoSpacing {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 1
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal-compose
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue vLink=purple>
<DIV dir=ltr align=left><FONT face=Calibri>Windows Working Group -
WinOF 2.1 Status
Meeting:
Tuesday, June 23, 2009 <o:p></o:p></FONT></DIV>
<DIV class=Section1>
<P class=MsoNoSpacing><FONT size=3> <o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>Attendees:
<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
Intel, QLogic, Mellanox, Microsoft<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT size=3>WHQL completed for IPoIB UD NDIS
5.1<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
This is not for the Trunk code. It is only for 2.0 with a handful of bug
fixes <FONT color=#0000ff><SPAN class=397550818-23062009><FONT size=2
face=Arial><FONT color=#000000>from</FONT></FONT></SPAN><SPAN
class=397550818-23062009> </SPAN></FONT>Mellanox.<o:p></o:p></FONT></P>
<P style="TEXT-INDENT: 0.5in" class=MsoNoSpacing><FONT size=3>NDIS 6 version
committed<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
Making connections and passing packets<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
Approximately 1 month of debug etc before WHQL testing<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
Need to adjust to get performance improvements for NDIS 6<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
Hope to wrap up in August timeframe.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT
size=3>
IPoIB C/M 5.1 version dropped in favor for work being done in IPoIB UD NDIS
6<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT size=3>Primary Discussion: Do we freeze
functionality and make a release ASAP or wait until NDIS 6 is
ready?<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT
size=3> Option
1: Wait for NDIS6 work to be completed. <o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Mellanox
targeting August<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT
size=3> Pros: Large
impact feature needed for release<o:p></o:p></FONT></P>
<P style="MARGIN-LEFT: 1.5in" class=MsoNoSpacing><FONT size=3>Don’t have
resources available now to perform QA on current code and continue with NDIS6
work which means it would be pushed out even further.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Cons: No
release in months from WinOF team<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Questions
as to whether August is a realistic date<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Pushes
future releases back even further.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT
size=3> Option
2: Freeze features now and make a release ASAP.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Make
a patch release if NDIS 6 is available in August.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNoSpacing><FONT
size=3> Pros: Get
a number of big fixes and other key features in customers’
hands<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Reestablish
with community that WInOF can make regular releases<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3>
<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><FONT
size=3> Cons: Resource
issues<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNoSpacing><FONT size=3><SPAN
class=397550818-23062009><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></FONT></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNoSpacing><FONT size=3><SPAN
class=397550818-23062009> </SPAN>Suggestion made… Mellanox remain
focused on NDIS6 while other members focus on QA and WHQL testing of current
trunk for release.<o:p></o:p></FONT></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNoSpacing><o:p><FONT
size=3> </FONT></o:p></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNoSpacing><FONT
size=3>Complication: Will Microsoft even give us a waiver for the ND Logo
for another NDIS 5.1 release. If they don’t the argument become
moot. QLogic to send request to Eric Lantz for
clarification.<o:p></o:p></FONT></P>
<P class=MsoNoSpacing><o:p><FONT size=3> </FONT></o:p></P>
<P class=MsoNormal><o:p><FONT size=3> </FONT></o:p></P></DIV></BODY></HTML>