<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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>With the approval of the OFA-SNIA Alliance on Remote PM (attached ), OFA and SNIA have agreed to collaborate on 2 deliverables:</div>
<ul style="margin:0;padding-left:36pt;">
<li>The next revision of the “NVM PM Remote Access for HA” white paper</li><li>A new remote PM use case enumeration</li></ul>
<div> </div>
<div>As the editor first version of the NVM PM Remote Access for HA white paper, I have volunteered to begin defining the next version. I think the best way to do that would be to review the current public version of the document in ofiwg. I would be happy
to briefly introduce that document in an upcoming ofiwg meeting, however the review itself should be driven by participants interested in the work of the alliance reading and commenting on the document at </div>
<div><a href="https://www.snia.org/sites/default/files/technical_work/final/NVM_PM_Remote_Access_for_High_Availability_v1.0.pdf"><font color="#0563C1"><u>https://www.snia.org/sites/default/files/technical_work/final/NVM_PM_Remote_Access_for_High_Availability_v1.0.pdf</u></font></a></div>
<div> </div>
<div>Comments that arise from that review can then be merged with a list of modifications already suggested by prior reviewers. The list so far includes the following:</div>
<div>Section 3.3 – Add OmniPath, Gen-Z, Open CAPI and CCIX to the description of Disaggregated Persistent Memory in the remote access taxonomy</div>
<div>Section 4 – Add sub-sections on integrity checking and pipelined sequences of RDMA operations for transactions.</div>
<div>New section – introduce the relationship between visibility and durability.</div>
<div>Section 5 – add asynchronous flush, enhance RDMA stack model, revisit figure</div>
<div>Section 6 – add discussion of flush scope, flush barrier ordering and more detail on pipelined sequences of RDMA for transactions</div>
<div>Section 6 – update all figures</div>
<div>Section 8 – describe limited role of network infrastructure in media error handling, reference integrity check, address “delivered but not durable” scenario.</div>
<div>Section 9 – Revisit requirements summary</div>
<div> </div>
<div>Paul Grun and I will coordinate the scheduling of this review in ofiwg.</div>
<div> </div>
<div>Work on the use case enumeration deliverable will proceed in parallel with this review.</div>
<div> </div>
<div>Thank You,</div>
<div>Doug Voigt,</div>
<div>SNIA NVMP TWG co-chair</div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>