From noreply at named-data.net  Thu Dec  5 14:00:06 2024
From: noreply at named-data.net (noreply at named-data.net)
Date: Thu, 05 Dec 2024 17:00:06 -0500
Subject: [Nfd-dev] NDN Weekly Call 2024-12-06
Message-ID: <675222666c93a_412dd208-329@mail.a2wood.art.mail>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241205/ea21ec0b/attachment.htm>

From bradlowe at g.ucla.edu  Thu Dec  5 19:07:01 2024
From: bradlowe at g.ucla.edu (bradlowe at g.ucla.edu)
Date: Fri, 06 Dec 2024 03:07:01 +0000
Subject: [Nfd-dev] NDN Weekly Call - Workspace Test Email
Message-ID: <48083985-81b7-66fe-42ba-2167be9e47f0@ucla.edu>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241206/0fa715e2/attachment.htm>

From bradlowe at g.ucla.edu  Thu Dec 12 13:01:44 2024
From: bradlowe at g.ucla.edu (bradlowe at g.ucla.edu)
Date: Thu, 12 Dec 2024 21:01:44 +0000
Subject: [Nfd-dev] NDN Weekly Call - Workspace Test Email
Message-ID: <fd3b389e-942d-67c6-90b8-79813b9f1a69@ucla.edu>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241212/5070e462/attachment.htm>

From noreply at named-data.net  Thu Dec 12 14:00:12 2024
From: noreply at named-data.net (noreply at named-data.net)
Date: Thu, 12 Dec 2024 17:00:12 -0500
Subject: [Nfd-dev] NDN Weekly Call 2024-12-13
Message-ID: <675b5cec21928_2a11af208-37b@mail.a2wood.art.mail>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241212/1f1ce2b1/attachment.htm>

From lixia at cs.ucla.edu  Thu Dec 12 21:35:11 2024
From: lixia at cs.ucla.edu (Lixia Zhang)
Date: Thu, 12 Dec 2024 21:35:11 -0800
Subject: [Nfd-dev] Fwd:  NDN Weekly Call 2024-12-13
References: <675b5cec21928_2a11af208-37b@mail.a2wood.art.mail>
Message-ID: <DC6AABF2-02C5-44B1-91DD-DE9AEB5C92CC@cs.ucla.edu>

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>

From bzhang at cs.arizona.edu  Fri Dec 13 09:00:39 2024
From: bzhang at cs.arizona.edu (Beichuan Zhang)
Date: Fri, 13 Dec 2024 10:00:39 -0700
Subject: [Nfd-dev] NDN Weekly Call 2024-12-13
In-Reply-To: <DC6AABF2-02C5-44B1-91DD-DE9AEB5C92CC@cs.ucla.edu>
References: <675b5cec21928_2a11af208-37b@mail.a2wood.art.mail>
 <DC6AABF2-02C5-44B1-91DD-DE9AEB5C92CC@cs.ucla.edu>
Message-ID: <CAFxh1C_SOqYU958ZMf2859PWxO1szYbnoEqEnC3R7v-oNa+z6w@mail.gmail.com>

Here's the UCLA tech report on auto prefix propagation:
https://irl.cs.ucla.edu/data/files/techreports/ndn0045-1.pdf

On Thu, Dec 12, 2024 at 10:35?PM Lixia Zhang <lixia at cs.ucla.edu> wrote:

> 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/20241213/684a73a2/attachment.htm>

From bzhang at cs.arizona.edu  Fri Dec 13 09:23:34 2024
From: bzhang at cs.arizona.edu (Beichuan Zhang)
Date: Fri, 13 Dec 2024 10:23:34 -0700
Subject: [Nfd-dev] NDN Weekly Call 2024-12-13
In-Reply-To: <CAFxh1C_SOqYU958ZMf2859PWxO1szYbnoEqEnC3R7v-oNa+z6w@mail.gmail.com>
References: <675b5cec21928_2a11af208-37b@mail.a2wood.art.mail>
 <DC6AABF2-02C5-44B1-91DD-DE9AEB5C92CC@cs.ucla.edu>
 <CAFxh1C_SOqYU958ZMf2859PWxO1szYbnoEqEnC3R7v-oNa+z6w@mail.gmail.com>
Message-ID: <CAFxh1C9k3-chd8VZREy_jDKApmV=Sd5DJSzNqfrMk8_A-OmySA@mail.gmail.com>

Junxiao pointed out that the design in the TR was obsoleted by the Prefix
Announcement Protocol (
https://redmine.named-data.net/projects/nfd/wiki/PrefixAnnouncement).
Currently NFD implements the old design, and YaNFD implements the new
design.

Beichuan

On Fri, Dec 13, 2024 at 10:00?AM Beichuan Zhang <bzhang at cs.arizona.edu>
wrote:

> Here's the UCLA tech report on auto prefix propagation:
> https://irl.cs.ucla.edu/data/files/techreports/ndn0045-1.pdf
>
> On Thu, Dec 12, 2024 at 10:35?PM Lixia Zhang <lixia at cs.ucla.edu> wrote:
>
>> 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/20241213/bd471aab/attachment.htm>

From noreply at named-data.net  Thu Dec 19 14:00:05 2024
From: noreply at named-data.net (noreply at named-data.net)
Date: Thu, 19 Dec 2024 17:00:05 -0500
Subject: [Nfd-dev] NDN Weekly Call 2024-12-20
Message-ID: <67649765b123b_13ced1208-3ea@mail.a2wood.art.mail>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241219/7b3ef2b3/attachment.htm>

From bradlowe at g.ucla.edu  Thu Dec 19 20:35:58 2024
From: bradlowe at g.ucla.edu (bradlowe at g.ucla.edu)
Date: Fri, 20 Dec 2024 04:35:58 +0000
Subject: [Nfd-dev] NDN Weekly Call - Workspace Test Email
Message-ID: <4a9308e2-5690-ee87-209e-2422c45c4e3e@ucla.edu>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241220/f276d655/attachment-0001.htm>

From noreply at named-data.net  Thu Dec 26 14:00:08 2024
From: noreply at named-data.net (noreply at named-data.net)
Date: Thu, 26 Dec 2024 17:00:08 -0500
Subject: [Nfd-dev] NDN Weekly Call 2024-12-27
Message-ID: <676dd1e849312_6bdff208-39@mail.a2wood.art.mail>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241226/8cdd4f0d/attachment.htm>

From bradlowe at g.ucla.edu  Thu Dec 26 20:10:45 2024
From: bradlowe at g.ucla.edu (bradlowe at g.ucla.edu)
Date: Fri, 27 Dec 2024 04:10:45 +0000
Subject: [Nfd-dev] NDN Weekly Call - Workspace Test Email
Message-ID: <aafe1bed-ad77-d7de-09d2-fbd681a220a2@ucla.edu>

An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20241227/faf225d1/attachment.htm>