<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head></head>
<body>
<p>This is a reminder of the upcoming NFD call using Zoom <a href="https://arizona.zoom.us/j/82909523174?pwd=bEc2VXk4M3ZrdC95SGlxUHVzRVFyUT09">https://arizona.zoom.us/j/82909523174?pwd=bEc2VXk4M3ZrdC95SGlxUHVzRVFyUT09</a>. The current call time is every Friday 09:00-11:00 Pacific Time.</p>
<p>
</p>
<h2>The current agenda includes the following issues:</h2>
<div id="issues">
<p class="c1"><span class="c0"></span></p>
<p class="c1"><span class="c0"></span></p>
<ul class="c7 lst-kix_afg97xc9ab5b-0 start">
<li class="c2 li-bullet-0"><span class="c0">NFD socket file path</span></li>
<li class="c2 li-bullet-0"><span class="c0">Where should we host Docker-related files?</span></li>
<li class="c2 li-bullet-0"><span class="c0">Maintainership of PSync, NLSR, mini-ndn</span></li>
</ul>
<p class="c1"><span class="c0"></span></p>
<p class="c9"><span class="c0">Strategy instances questions/design questions (AA)</span></p>
<ul class="c7 lst-kix_cgsg76gjqzw9-0 start">
<li class="c2 li-bullet-0"><span class="c0">Looks like for each prefix, we are creating new instance of the strategy class. I thought this should not have been the case, did the design changed or it is a bug?</span></li>
<li class="c2 li-bullet-0"><span class="c0">What could be the best place to introduce “traffic shaping†pipeline between strategy and forwarding (after strategy made decision before strategy sends data), potentially applying to multiple strategies (aware or not of shaping)</span></li>
</ul>
<p class="c1"><span class="c0"></span></p>
<p class="c9"><span>Progress check on unresolved testbed problems:</span></p>
<ul class="c7 lst-kix_ni36ky343t1j-0 start">
<li class="c2 li-bullet-0">
<span>testbed-nodes.json returns wrong information in ndn-up and ws-tls fields: </span><span class="c3"><a class="c4" href="https://named-data.slack.com/archives/C01EKSVNAB1/p1692413231845129">https://named-data.slack.com/archives/C01EKSVNAB1/p1692413231845129</a></span><span class="c0"><br>assigned to Alex on 20230825</span>
</li>
<li class="c2 li-bullet-0">
<span>Tianyuan cannot access MML2, ITB, ANYANG, DELFT, SRRU nodes; need to contact local operators to restore access<br></span><span class="c3"><a class="c4" href="https://named-data.slack.com/archives/C01EKSVNAB1/p1694563021207589?thread_ts=1694541186.027239&cid=C01EKSVNAB1">https://named-data.slack.com/archives/C01EKSVNAB1/p1694563021207589?thread_ts=1694541186.027239&cid=C01EKSVNAB1</a></span><span class="c0"><br>assigned to Tianyuan on 20230922</span>
</li>
</ul>
<ul class="c7 lst-kix_ni36ky343t1j-1 start">
<li class="c6 li-bullet-0"><span class="c0">Tianyuan Update 20230929: Email sent for all problematic nodes</span></li>
<li class="c6 li-bullet-0"><span class="c0">recheck on 20231020: unresponsive nodes will be evicted</span></li>
</ul>
<ul class="c7 lst-kix_ni36ky343t1j-0">
<li class="c2 li-bullet-0">
<span>TNO: UDP unreachable<br></span><span class="c3"><a class="c4" href="https://named-data.slack.com/archives/C01EKSVNAB1/p1694633737227409">https://named-data.slack.com/archives/C01EKSVNAB1/p1694633737227409</a></span><span class="c0">Â </span>
</li>
<li class="c2 li-bullet-0">
<span>SRRU: WebSocket does not work due to possible borked DNS resolver<br></span><span class="c3"><a class="c4" href="https://named-data.slack.com/archives/C01EKSVNAB1/p1694546491998299?thread_ts=1694541856.232119&cid=C01EKSVNAB1">https://named-data.slack.com/archives/C01EKSVNAB1/p1694546491998299?thread_ts=1694541856.232119&cid=C01EKSVNAB1</a></span><span class="c0">Â </span>
</li>
<li class="c2 li-bullet-0">
<span>ARIZONA and MEMPHIS: TLS certificate expired<br></span><span class="c3"><a class="c4" href="https://named-data.slack.com/archives/C01EKSVNAB1/p1696385979248889">https://named-data.slack.com/archives/C01EKSVNAB1/p1696385979248889</a></span><span class="c0">Â </span>
</li>
</ul>
<p class="c1"><span class="c0"></span></p>
<p class="c9"><span class="c0">Pull Reminders: (patches that have been waiting for review for more than 5 days)</span></p>
<ul class="c7 lst-kix_1nok7m7cqsbr-0 start">
<li class="c2 li-bullet-0">
<span>7133: fw: delegate sending Nack-duplicate to forwarding strategy | </span><span class="c3"><a class="c4" href="https://gerrit.named-data.net/c/NFD/+/7133">https://gerrit.named-data.net/c/NFD/+/7133</a></span><span class="c0">Â , reviewer: undetermined</span>
</li>
<li class="c2 li-bullet-0">
<span>7132: consumer: gather constructor args into Options struct | </span><span class="c3"><a class="c4" href="https://gerrit.named-data.net/c/PSync/+/7132">https://gerrit.named-data.net/c/PSync/+/7132</a></span><span class="c0">Â , reviewer: Tianxing</span>
</li>
</ul>
<p class="c1"><span class="c0"></span></p>
<p class="c1"><span class="c0"></span></p>
<ul class="c7 lst-kix_2wl22m6w7q9o-0 start"><li class="c2 li-bullet-0"><span class="c0">Forwarding Spec</span></li></ul>
<p class="c1 c8"><span class="c0"></span></p>
<ul class="c7 lst-kix_2wl22m6w7q9o-0"><li class="c2 li-bullet-0">
<span>ICNRG mailing list topics </span><span class="c3"><a class="c4" href="https://datatracker.ietf.org/rg/icnrg/documents/">https://datatracker.ietf.org/rg/icnrg/documents/</a></span>
</li></ul>
<p class="c1 c8"><span class="c0"></span></p>
<ul class="c7 lst-kix_2wl22m6w7q9o-0"><li class="c2 li-bullet-0"><span class="c3"><a class="c4" href="https://docs.google.com/document/d/17sDBdlQ0KbEwtjn6Bk2eRb1bcKAs3s-i1k4ChGLYssk/edit?usp=drivesdk">NDN Platform Development Roadmap</a></span></li></ul>
<p class="c1"><span class="c0"></span></p>
</div>
</body>
</html>