<html 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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
.MsoPapDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:278924582;
mso-list-template-ids:1392008202;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Everyone<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Here is a tentative meeting agenda for 24 February 2023. With all of the moving parts and initiatives, I wanted to have the full hour to go over everything. Unfortunately, I just ended up being scheduled for
a meeting that I am unable to miss, at 8:30 am, tomorrow. So, I’ll try to be fast and start right at 8 am.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">The Reference Repository<o:p></o:p></li><ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo1">We need to get Registration for Events agreed upon<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo1">We need to get the code finished on the propagation<o:p></o:p></li></ol>
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">Aggregators---any more information than is on the page?<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">The Use-Cases for Composability<o:p></o:p></li><ol start="1" type="1">
<li class="MsoListParagraph" style="color:#00000A;mso-list:l0 level2 lfo1"><span style="color:windowtext">Using ResourceBlocks and the Resource Composition abstraction in Redfish is something we have discussed soon after we joined this group and it is totally
in line with our point of view. At the time we got stuck with the discussion on who creates the resource blocks. The two options at the time were: The composition service infers them from the structure of the fabric or, the agents advertise all resources as
resource blocks. We should restart this conversation to define these aspects because they would change the way agents register to the OFMF and advertise components.</span><span style="font-size:13.5pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#00000A;mso-list:l0 level2 lfo1"><span style="color:windowtext">On your use-cases I think they are ok but I do not understand the alternate flow depicting a situation when the resources are “not local to the requesting
client”. What do you mean with a resource being local to a client requestor? I only see remote/local to apply here from the CPU perspective. i.e., the memory is remote (through fabric) to the CPU, etc.</span><span style="font-size:13.5pt"><o:p></o:p></span></li></ol>
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">The framework for the fabric Agents<o:p></o:p></li><ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo1">CXL mock-up<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo1">We’ll expand out a slide with disaggregated components and build out schemas to account for 1). CXL bridging across RDMA (OmniPath) fabrics, 2) OmniPath connecting NVMe over Fabrics, 3) CXL ports
toggling to switches, 4) CXL connecting NVMe, 5) OmniPath switch topologies<o:p></o:p></li></ol>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>