[Nfd-dev] NDN Weekly Call

[Bradford Lowe]

This is a reminder of the upcoming NFD call using Zoom
https://arizona.zoom.us/j/82909523174?pwd=bEc2VXk4M3ZrdC95SGlxUHVzRVFyUT09
The current call time is every Friday 09:00-11:00 Pacific Time.

The current agenda includes the following issues:

------------------------------

Discussion Agenda for 2/21/25:

   -

   NDNComm 2025 preparation
   -

      bashing the CPF
      -

      collect input to make a presentation list
      -

      collect input to make a hackathon topic list
      -

      hackathon preparation status, NDNComm webpage setup
      -

   Any other discussion topics?

NDN Community Meeting related

   -

   Committee:
   -

      2025-01-24: Beichuan agreed to be on the NDNcomm committee.
      -

   Registration system.
   -

      2025-01-24: Alex agreed to setup Eventbrite registration portal.
      -

   Open submission system. Don't wait until the last few weeks.
   -

   Elect hackathon leaders.
   -

      2025-01-17: Adam Thieme agreed to be a hackathon leader.
      -

   Make a public announcement of NDNcomm 2025 + hackathon on
   https://named-data.net frontpage.
   -

      Dates: 2025-04-17 ~ 2025-04-20.

Prefix Announcement related

   -

   Existing issues:
   -

      https://redmine.named-data.net/issues/4651 - NFD reuses application's
      prefix announcement object when it propagates the prefix announcement
      -

      https://redmine.named-data.net/issues/4541 - propagate strategy
      choice through routing announcement
      -

   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?
   -

   What should be the security model / trust schema for the testbed /
   global routing system to verify the prefix announcement objects?
   -

      1/ trust schema works on a given system model
      2/ we still need to answer the question of how the local host and
      local hub find each other.
      3/ with that, local hub fetches prefix announcement from the app
      -

      local forwarder is not in the business of verifying all the data
      forwarded, why prefix announcement (a data packet) should be different?

Workspace - ndn-call-notifications

   -

   Automate weekly sending.

Signed Interest

   -

   Carry parameters in Data packet enclosed in ApplicationParameters
   -

   Carry parameters with Reflexive Forwarding:
   https://datatracker.ietf.org/doc/draft-irtf-icnrg-reflexive-forwarding/
   -

   NDNCERT 0.4 spec (use signed Data instead of signed Interest)
   -

      create a new page under https://github.com/named-data/ndncert/wiki

Testbed related

   -

   new node sponsored by PCL, where is it?
   -

   AVEIRO: offline, repair or delete?
   -

   BERN: offline, repair or delete?
   -

   ANYANG: firewall blocking UDP and WebSocket incoming, repair?
   -

   QUB: offline, repair or delete?
   -

   TNO: firewall blocking UDP incoming, repair?
   -

   URJC, ANYANG, NEU, MEMPHIS, FRANKFURT, SINGAPORE: reinstall traffic
   capture scripts
   <https://github.com/tntech-ngin/ndn-traffic-capture-scripts>?
   -

      2025-02-27: Adam will take care of this.


If you want to edit the issue list in this document, go to the Workspace
app at https://ndn-workspace.web.app and follow the instructions to join a
new workspace with the following trust anchor:

/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

Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu
https://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20250220/73555aaa/attachment.htm>