<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-05-29</h2>
<ul>
<li>
<p>review and merge NAC-ABE pull request <a href="https://github.com/UCLA-IRL/NAC-ABE/pull/39">https://github.com/UCLA-IRL/NAC-ABE/pull/39</a> (Suravi, Tianyuan, Adam)</p>
<ul>
<li>Suravi to become maintainer of NAC-ABC repository</li>
</ul>
</li>
<li>
<p>NDNComm 2026 slides collection:</p>
<ul>
<li>Session 1: done</li>
<li>Session 2: done</li>
<li>Session 3 (Beichuan)</li>
<li>Session 4 (Tianyuan): <a href="https://ownly.work/ndn-ownly.named--data.net-weekly--calls/project/documents/Ownly-ndn6_20260519.pptx">Ownly-ndn6</a> is in Ownly</li>
<li>Session 5 (Junxiao): <a href="https://ownly.work/ndn-ownly.named--data.net-weekly--calls/project/documents/ndncomm2026-jsd.pptx">SCION</a> is in Ownly; others already uploaded</li>
</ul>
</li>
<li>
<p>session 5 recording: did we do it?</p>
</li>
<li>
<p>What is the problem with ndncomm26 mailing list (got it into spam list)? Let's fix it</p>
<ul>
<li>Requirements: <a href="https://www.cloudflare.com/learning/email-security/dmarc-dkim-spf/">SPF DKIM DMARC</a></li>
</ul>
</li>
<li>
<p>Ownly telemetry using <a href="https://www.bugsnag.com/">BugSnag</a></p>
<ul>
<li>
<p>When an error occurs in the web application, BugSnag automatically captures stack trace, recent UI clicks and console messages, browser version information, etc.
They are reported on BugSnag dashboard for the developer to review.</p>
<p><img src="https://imageperl.com/ext/Q6cd78DTp4.png" alt="BugSnag demo"></p>
<ul>
<li><em>PS. how to embed an image uploaded in Ownly workspace? I had to upload to external host for embedding to work.</em></li>
</ul>
</li>
<li>
<p><a href="https://www.bugsnag.com/pricing/">BugSnag pricing</a> — free tier limitations:</p>
<ul>
<li>only one user account per website</li>
<li>can only view errors in past 7 days</li>
</ul>
</li>
<li>
<p>Benefits and drawbacks:</p>
<ul>
<li>👍 Ownly developer can catch errors automatically without requiring each user to report the error.</li>
<li>👍 Errors on a mobile browser can be uploaded seamlessly without needing complex devtools setup.</li>
<li>👎 Privacy policy must be updated to reflect BugSnag usage.</li>
</ul>
</li>
</ul>
</li>
<li>
<p>Testbed status page webapp should validate signatures, to demonstrate NDN security.
Current code <a href="https://github.com/named-data/testbed/blob/864a24a46d5cc1d4bd1db5d3f86e5209bd881607/framework/ndn-testbed-status/src/App.vue#L182-L185">does not use <code>verifier</code></a>.</p>
</li>
<li>
<p>Publish written specifications for ndnd proprietary features that are intended for wider adoption:</p>
<ul>
<li>cross schema</li>
<li>2-step forwarding</li>
<li>validation of expired certificates</li>
</ul>
</li>
<li>
<p>Include automated interoperability testing for ndnd features that are intended to be compatible with existing specifications:</p>
<ul>
<li>NDNCERT</li>
<li>repo commands</li>
<li>Light VerSec</li>
<li>State Vector Sync</li>
<li><em>PS. ndn-rs has some interoperability tests with various maturity. In contrast, ndnd has zero interoperability testing so it could accidentally drift away from specifications.</em></li>
</ul>
</li>
<li>
<p>NDNComm 2026 debriefing (continued): what we learned, what issues arose, what we should aim for as next step.</p>
</li>
</ul>
<h2>2026-05-22</h2>
<ul>
<li>NDNComm 2026 debriefing: what we learned, what issues arose, what we should aim for as next step.
<ul>
<li>
<p>Ownly discussion is less utilized in 2026 than 2025.</p>
<ul>
<li>
<p>Some participants registered too late, so that they did not receive Ownly instruction posted via mailing list.</p>
</li>
<li>
<p>Both Zoom and Ownly should be prepared well before the conference, and the instructions should be included as part of Eventbrite confirmation email / ticket.</p>
</li>
<li>
<p>Mailing list has improper setup causing <code>dkim=fail</code> or <a href="https://www.mail-tester.com/test-6y26ixeuw">DKIM missing</a>.
This causes outgoing messages to go into spam or get dropped silently.</p>
<pre class="language-text"><code class="language-text code-highlight"><span class="code-line line-number" line="1">Authentication-Results-Original: relay.mimecast.com; dkim=fail ("body hash did
</span><span class="code-line line-number" line="2">not verify") header.d=cs.ucla.edu
</span><span class="code-line line-number" line="3">header.s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C header.b=Sq5fGZZY; dmarc=pass
</span><span class="code-line line-number" line="4">(policy=none) header.from=ucla.edu; spf=pass (relay.mimecast.com: domain of
</span><span class="code-line line-number" line="5">ndncomm2026-bounces@lists.cs.ucla.edu designates 131.179.128.22 as permitted
</span><span class="code-line line-number" line="6">sender) smtp.mailfrom=ndncomm2026-bounces@lists.cs.ucla.edu
</span><span class="code-line line-number" line="7">Received: from pike.cs.ucla.edu (Pike.CS.UCLA.EDU [131.179.128.22]) by
</span><span class="code-line line-number" line="8">relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,
</span><span class="code-line line-number" line="9">cipher=TLS_AES_256_GCM_SHA384) id usb-mta-38-1nhcO4nXOx6cBPYQPjvTZg-1; Sun,
</span><span class="code-line line-number" line="10">17 May 2026 14:50:17 -0700
</span></code></pre>
</li>
</ul>
</li>
<li>
<p>Home IoT use case: there's no drive to deploy them.</p>
<ul>
<li>We don't have NDN-based home IoT devices that people want to use continuously.</li>
<li>Existing cloud based system fails infrequently enough to cause user inconvenience.</li>
<li>User convenience is the main drive in staying in current course.</li>
</ul>
</li>
<li>
<p>Think about recurring discussion topics:</p>
<ul>
<li>One year from now, what direction do we want to get to?</li>
</ul>
</li>
<li>
<p>NDN for AI & AI for NDN is a topic that will have profound impact and will move rapidly.</p>
<ul>
<li>Current way we do research will become obsolete in a decade.</li>
<li>We can use AI as a tool so that a research paper can be completed in a few weeks.</li>
<li>AI is unable to come up with new ideas, but human researcher can often come up with new ideas when discussing with AI.</li>
<li>Having multiple AI agents may accelerate the progress.</li>
</ul>
</li>
</ul>
</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>
<br>
<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>