<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Today’s agenda:</div>
<ul style="margin:0;padding-left:36pt;">
<li>Review some materials from Sean</li><li>Review suggestions from Paul as to how we can divide some work so we can operate in parallel and strictly serial</li></ul>
<div> </div>
<div>916-356-2663, Bridge 3</div>
<div>Participant Passcode: 8101113</div>
<div> </div>
<div>Agenda:</div>
<ul style="margin:0;padding-left:36pt;">
<li>Review the charter and modify as required:<br>
OpenFramework Working Group (OFWG) within the OFA’s bylaws with the following charter:</li></ul>
<ul style="margin:0;padding-left:72pt;">
<li><i>Develop, test, and distribute</i></li></ul>
<ul style="margin:0;padding-left:108pt;">
<li><i>An extensible, open source framework that provides access to high-performance fabric interfaces and services.</i></li><li><i>Extensible, open source interfaces aligned with ULP and application needs for high-performance fabric services</i></li></ul>
<ul style="margin:0;padding-left:72pt;">
<li><i>Work with standards bodies as needed to create interoperability; the OFA will not itself create industry standards</i></li></ul>
<ul style="margin:0;padding-left:36pt;">
<li>Identify participants by name and company affiliation</li><li>See if there’s any interest in leadership of the WG, again, given the Bylaws provision on member/nonmember rights and privileges</li><li>Identify deliverables to be produced by the WG</li><li>Discuss general procedures for developing and approving deliverables</li></ul>
<div> </div>
<div>Further thoughts are more than welcome</div>
<div> </div>
<div>Thanks, Jim, acting chair of the OFWG</div>
<div> </div>
</span></font>
</body>
</html>