<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-04-24</h2>
<ul>
<li>ICNRG Co-Chair reached out to solicit</li>
</ul>
<h2>2026-04-17</h2>
<ul>
<li>
<p>Remove PIT lookup for BIER multicast Interest?</p>
<ul>
<li>BIER multicast delivery itself is loop-free, the only source of looping is IGP</li>
<li>IGP looping does not lead to duplicate delivery, quote RFC 8279</li>
</ul>
<blockquote>
<p>If, at some time, the routing underlay is not providing a loop-free
path between BFIR-A and BFER-B, then BIER-encapsulated packets may
loop while traveling from BFIR-A to BFER-B.  However, such loops will
never result in delivery of duplicate packets to BFER-B.</p>
</blockquote>
</li>
<li>
<p>presentation on status of the RUST implementation of NFD by Peter Le (U. Memphis)</p>
<ul>
<li>
<p>@yoursunny's comment:</p>
<blockquote>
<p><a href="https://github.com/Quarmire/ndn-rs">ndn-rs</a> appears to be developed by Claude Sonnet with occasional participation of Claude Opus, with barely any human insight.
The many GitHub Issues posted by @yoursunny under advise from Gemini are intended to test the limits of Claude, although @yoursunny has validated the technical correctness of these comments.
Please do not blame @yoursunny if you feel the issues are overly complicated, as most of these issues are not meant to be implemented by a human developer.
The write-ups are structured for Claude consumption and not for human understanding.</p>
</blockquote>
</li>
</ul>
</li>
<li>
<p>Renaming RDR: we agreed that "realtime" is misleading, so what should we call it? "metadata discovery/retrieval protocol"?</p>
<ul>
<li>
<p>@yoursunny's answer: <strong>R</strong>ecent metadata <strong>D</strong>iscovery and <strong>R</strong>etrieval protocol.</p>
<p><small>Note: @yoursunny is at FABRIC KNIT12 conference and cannot attend this call.</small></p>
</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>