[Nfd-dev] Fwd: NDN Weekly Call 2024-12-13

[Lixia Zhang]

I wont be able to attend the call tomorrow morning.
I had promised to send an email beforehand-- this is very last minute.
I missed the last Friday call too due to visiting to WashU.

I learned from students that last Friday discussed the (automated) prefix forwarding issues. Unfortunately most people with institution memory missed last Friday call.

My recollection: 
1/ in early days, we had concept of "scope": local host, local hub, everything else.

2/ register a prefix with local NFD means within local host, prefix wont propagate.
(this is to clarify with Varun that a prefix registration with local NFD does not mean it would/should be propagated by routing protocol)

3/ to have the prefix propane via routing protocol: one needs to do something like remote registration and/or auto prefix propagation, 
i.e. register the prefix with routing protocol, which requires going through a few steps of prefix ownership.

I hope people on TO: list has the long memory to get this issue clarified.

I should be able to tune into next Friday call 12/20.

Lixia

> Begin forwarded message:
> 
> From: noreply--- via Nfd-dev <nfd-dev at lists.cs.ucla.edu>
> Subject: [Nfd-dev] NDN Weekly Call 2024-12-13
> Date: December 12, 2024 at 2:00:12 PM PST
> To: nfd-dev at lists.cs.ucla.edu
> Reply-To: noreply at named-data.net
> 
> 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:
> 
> 
> 
> Lixia: NDNComm 2025 theme discussion
> 
> 
> NDN Overview revision planning
> 
> 
> _______________________________________________
> 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/20241212/fdc66995/attachment-0001.htm>