<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-07-31</h2>
<ul>
<li>Signature Timestamp: should it be required, or optional</li>
<li><a href="https://github.com/UCLA-IRL/ndn-python-repo/pull/120">ndn-python-repo #120</a>: enable Python 3.13 support</li>
<li>Discuss 1Y goal document</li>
</ul>
<h2>2026-07-24</h2>
<ul>
<li>Timestamp in SVS-PS MappingData</li>
<li>StateVectorSync spec and implementations:
<ul>
<li><a href="https://github.com/named-data/StateVectorSync/pull/21">spec #21</a>: prefix announcement should include <code>/v=3</code> component ✅<em>merged</em></li>
<li><a href="https://github.com/named-data/StateVectorSync/pull/22">spec #22</a>: include <code>t=<bootstrap-time></code> in SVS-PS name structure; use SequenceNumNameComponent instead of GenericNameComponent ✅<em>merged</em></li>
<li><a href="https://github.com/named-data/ndn-svs/pull/36">ndn-svs #36</a>: update C++ library to match v3 spec; multi-threading changes should be split to another PR if desired</li>
<li><a href="https://github.com/named-data/ndnd/pull/198">ndnd #198</a>: update Go library to match spec change #21 ✅<em>merged</em></li>
<li><a href="https://github.com/named-data/python-ndn/pull/105">python-ndn #105</a>: clarify <code>ndn.app_support.svs</code> is SVS v1 and incompatible with other SVS protocol versions ✅<em>merged</em></li>
<li>NDNts: spec change #21 ✅<em>done</em></li>
<li>NDNts: spec change #22 ✅<em>done</em></li>
</ul>
</li>
<li>One year from now, what direction do we want to get to? (recurring topic established 2026-05-22)
<ul>
<li>we discussed on 7/10. We can do a summary here.</li>
</ul>
</li>
</ul>
<h2></h2>
<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>