<div class="c3 doc-content">
<p class="c4">
<span class="c1">
This is a reminder of the upcoming NFD 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><h2>Discussion Agenda:</h2><ul><li><p>recent plan on workspace.</p></li><li><p>recent progress on SVSPS</p></li></ul><h2>NDN Community Meeting related</h2><ul><li><p>Committee:</p><ul><li><p>2025-01-24: Beichuan agreed to be on the NDNcomm committee.</p></li></ul></li><li><p>Registration system.</p><ul><li><p>2025-01-24: Alex agreed to setup Eventbrite registration portal.</p></li></ul></li><li><p>Open submission system. Don't wait until the last few weeks.</p></li><li><p>Elect hackathon leaders.</p><ul><li><p>2025-01-17: Adam Thieme agreed to be a hackathon leader.</p></li></ul></li><li><p>Make a public announcement of NDNcomm 2025 + hackathon on https://named-data.net frontpage.</p><ul><li><p>Dates: 2025-04-17 ~ 2025-04-20.</p></li></ul></li></ul><h2>Prefix Announcement related</h2><ul><li><p>Existing issues:</p><ul><li><p>https://redmine.named-data.net/issues/4651 - NFD reuses application's prefix announcement object when it propagates the prefix announcement</p></li><li><p>https://redmine.named-data.net/issues/4541 - propagate strategy choice through routing announcement</p></li></ul></li><li><p>After a local application creates a prefix registration in the local forwarder from a prefix announcement object, how to decide whether the prefix should (1) stay in the local forwarder, or, (2) propagate to the connected testbed router and readvertised into global routing?</p></li><li><p>What should be the security model / trust schema for the testbed / global routing system to verify the prefix announcement objects?</p><ul><li><p>1/ trust schema works on a given system model<br>2/ we still need to answer the question of how the local host and local hub find each other.<br>3/ with that, local hub fetches prefix announcement from the app</p></li><li><p>local forwarder is not in the business of verifying all the data forwarded, why prefix announcement (a data packet) should be different?</p></li></ul></li></ul><h2>Workspace - ndn-call-notifications</h2><p>All prior issues have been filed at https://github.com/UCLA-IRL/ndn-workspace-solid/issues . These issues are kept here because the issue tracker is disabled at https://github.com/brad-lowe/ndn-call-notifications repository.</p><ul><li><p>Automate weekly sending.</p></li></ul><h2>Signed Interest</h2><ul><li><p>Carry parameters in Data packet enclosed in ApplicationParameters</p></li><li><p>Carry parameters with Reflexive Forwarding: https://datatracker.ietf.org/doc/draft-irtf-icnrg-reflexive-forwarding/</p></li><li><p>NDNCERT 0.4 spec (use signed Data instead of signed Interest)</p><ul><li><p>create a new page under https://github.com/named-data/ndncert/wiki</p></li></ul></li></ul><h2>Testbed related</h2><ul><li><p>new node sponsored by PCL, where is it?</p></li><li><p>AVEIRO: offline, repair or delete?</p></li><li><p>BERN: offline, repair or delete?</p></li><li><p>SRRU: offline, repair or delete?</p></li><li><p>ANYANG: firewall blocking UDP and WebSocket incoming, repair?</p></li><li><p>MEMPHIS: offline, repair?</p></li><li><p>QUB: offline, repair or delete?</p></li><li><p>TNO: firewall blocking UDP incoming, repair?</p></li><li><p>URJC, ANYANG, NEU, MEMPHIS, FRANKFURT, SINGAPORE: reinstall <a href="https://github.com/tntech-ngin/ndn-traffic-capture-scripts">traffic capture scripts</a>?</p><ul><li><p>2025-02-27: Adam will take care of this.</p></li></ul></li></ul><p></p><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">
Nfd-dev mailing list
</span>
<br>
<span class="c2">
<a class="c5" href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a>
</span>
<br>
<span class="c2">
<a class="c5" href="https://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">https://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a>
</span>
</p>
</div>