<div class="c3 doc-content">
<p class="c4">
<span class="c1">
This is a reminder of the upcoming NDN call using Zoom
</span>
<span class="c2">
<a class="c5" href="https://arizona.zoom.us/j/82909523174?pwd=bEc2VXk4M3ZrdC95SGlxUHVzRVFyUT09">https://arizona.zoom.us/j/82909523174?pwd=bEc2VXk4M3ZrdC95SGlxUHVzRVFyUT09</a>
</span>
<br>
<span class="c1">
The current call time is every Friday 09:00-11:00 Pacific Time.
</span>
</p>
<p class="c0">
<span class="c1">
</span>
</p>
<!-- <p class="c4">
<span class="c1">
<h2>
The current agenda includes the following issues:
</h2>
</span>
</p> -->
<hr><h1>NDN Weekly Call Discussion Agenda</h1>
<h2>2026-10-16</h2>
<ul>
<li>This entry is inserted on 2026-10-08 to test whether the <a href="https://github.com/UCLA-IRL/call-notification-agent/issues/2">improper week ranges</a> bug has been resolved in the running script for sending weekly agenda emails.
<ul>
<li>
<p>Per Adam's claim on 2026-07-17, <a href="https://github.com/UCLA-IRL/call-notification-agent">UCLA-IRL/call-notification-agent</a> is the official repository for the script, and he would take over as the maintainer once <a href="https://github.com/UCLA-IRL/call-notification-agent/pull/1">PR#1</a> is merged, which occurred on 2026-07-28.</p>
</li>
<li>
<p>The latest commit is <a href="https://github.com/UCLA-IRL/call-notification-agent/tree/b41c9e7238e56828f873ba034ef5d086724485ed">b41c9e72</a> as observed on 2026-10-08, where there is no evidence of bugfix.</p>
</li>
<li>
<p>If the 2026-10-02 section appears on the email for 2026-10-09, it indicates the bug is not resolved, and Adam needs to fix this bug as he promised on 2026-07-17 call.</p>
</li>
<li>
<p>If the 2026-10-02 section does not appear on the email for 2026-10-09, Adam needs to push the bugfix to this repository.
This would enable future developers to pick up from there, preventing the "identify where is the source code" delay when Adam eventually graduates.</p>
<p>Adam - The code is updated according to the issue: Previous week, Current week, and all future weeks. I am working on cleaning up the code so I can push it to a public repository.</p>
</li>
</ul>
</li>
</ul>
<h2>2026-10-09</h2>
<ul>
<li>Has Ownly registered for the IETF 127 hackathon, which starts in 5 weeks?
<ul>
<li>Who would be the project champions?
Champions are responsible for registering the project on <a href="https://wiki.ietf.org/en/meeting/127/hackathon">IETF 127 hackathon wiki</a>.</li>
<li>What would be the project objectives at the IETF 127 hackathon?</li>
<li>Would there be an I-D that describes the project that potential participants could read ahead?
If so, who would submit the I-D?</li>
</ul>
</li>
<li>Testbed node SSH access by operators:
<ul>
<li>Testbed operator cannot SSH into the following nodes:
<ul>
<li>AFA (Adam can SSH into this node)</li>
<li>ANYANG (contacted 10/6)</li>
<li>IIITH (can SSH but cannot update; contacted 10/6)</li>
<li>QUB (contacted 10/6)</li>
<li>SRRU (contacted 9/24)</li>
</ul>
</li>
<li>Setup crontab to automatically SSH into each node once a day, so that the loss of SSH access can be discovered quickly.</li>
</ul>
</li>
<li><a href="https://named-data.slack.com/archives/C01EKSVNAB1/p1789750491683539">Parallel ndnd testbed</a>
<ul>
<li>2026-10-02 report: local operators have been contacted, but ARIZONA operator email is wrong.
<ul>
<li>ARIZONA operator email is now corrected in docs. HOST_VARS in general should be updated</li>
</ul>
</li>
<li>This network should use <code>/ndnd</code> as root name to avoid conflicts and confusion.</li>
<li>Once there are five nodes with requested ports open, deployment can start.</li>
<li>Meanwhile, Compose file is being developed.</li>
</ul>
</li>
<li>Open issues of the ndnd testbed:
<ul>
<li>How to perform authentication and authorization on the prefix registration requests received at <code>/localhop/nfd/rib/register</code>?
<ul>
<li>i.e. What's the equivalent of <a href="https://github.com/named-data/NFD/blob/23c535357d7902e727615523bcd28c1da7590db6/nfd.conf.sample.in#L348">NFD <code>localhop_security</code></a>?</li>
<li>If the answer is a completely different prefix registration protocol, where is the protocol specification?</li>
</ul>
</li>
<li>How to monitor the routing protocol?
<ul>
<li>i.e. What's the equivalent of <a href="https://redmine.named-data.net/projects/nlsr/wiki/LSDB_DataSet">NLSR LSDB dataset</a>?</li>
<li>How do I know the routing is working properly, e.g. calculating the correct distance vectors?</li>
</ul>
</li>
<li>How to advertise/withdraw a route statically, not <a href="https://github.com/named-data/ndnd/issues/141#issuecomment-2843470832">through readvertise</a>?
<ul>
<li>i.e. What's the equivalent of <a href="https://github.com/named-data/NLSR/blob/bb59d40e3a71f1433beccae4eafdddd016f4ae91/tools/nlsrc.cpp#L85-L86"><code>nlsrc advertise</code> command</a>?</li>
<li>This is needed so that an aggregated route representing the site, such as <code>/ndn/nl/tno</code>, could be advertised, instead of one route per application such as <code>/ndn/nl/tno/ping</code> and <code>/ndn/nl/tno/repo</code>.</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2>2026-10-02</h2>
<ul>
<li>Is Ownly demo still planned for IETF 127 ?</li>
<li><a href="https://named-data.slack.com/archives/C01EKSVNAB1/p1789750491683539">Parallel ndnd testbed</a>
<ul>
<li>UDP 6364, WebTransport 6367, WebSocket via existing Caddy</li>
<li>Tianyuan is contacting the local operators to enable these ports, please report progress.</li>
</ul>
</li>
<li>Several testbed nodes have EOL operating system Ubuntu 20.04: AFA ANYANG IIITH QUB.
They need <code>do-release-upgrade</code>.
<ul>
<li>AFA: upgraded</li>
<li>ANYANG: cannot SSH</li>
<li>IIITH: cannot SSH</li>
<li>QUB: cannot SSH</li>
</ul>
</li>
<li>Tianxing: We have updated the OpenABE library used by NAC-ABE so that it now supports OpenSSL 3.0, which is the default OpenSSL version on Ubuntu 22.04 and later. At the moment, we are using a personal repository for this code. Would it be appropriate to create an official ndn/openabe repository to host and maintain this updated version?</li>
<li><a href="https://github.com/UCLA-IRL/ndn-python-repo/pull/119">ndn-python-repo#119</a> needs code review; <a href="https://named-data.slack.com/archives/C05T3B0BDPF/p1785783928535329?thread_ts=1785780702.033259&cid=C05T3B0BDPF">Adam promised on 2026-08-03</a>
<ul>
<li>Done. A short presentation on why the design was chosen (how it meets the needs of the app) would be instructive, especially for (1) single Interest-data exchange for sending a Command and (2) prefix registration based on Data name</li>
</ul>
</li>
<li><a href="https://github.com/named-data/ndn-svs/pull/37">ndn-svs#37</a>: need rework by Tianxing</li>
</ul>
<hr>
<p class="c0">
<span class="c1">
</span>
</p>
<!-- <p class="c4">
<span>
If you want to edit the issue list in this document, go to the Workspace app at
</span>
<span class="c2">
<a class="c5" href="https://ndn-workspace.web.app">https://ndn-workspace.web.app</a>
</span>
<span class="c1">
and follow the instructions to join a new workspace with the following trust anchor:
</span>
</p>
<p class="c0">
<span class="c1">
</span>
</p>
<p class="c4">
<span>
/8=ndn/8=weekly-call-doc/8=KEY/8=%A0w%E9%88%23%27%D91/8=self/54=%00%00%01%92%CA%C4EN/1=%16u%A9%29%8BM%DA%82%A5%8FR%F2%AB%04-%89a%CF%82%AF%ED%FD%A1%5B%0E%28%F0%23%27%0B%D5%24
</span>
</p> -->
<p class="c4">
<span class="c1">
Sent via Ownly
</span>
</p>
</div>