From bradlowe at g.ucla.edu  Thu May  1 20:38:57 2025
From: bradlowe at g.ucla.edu (Bradford Lowe)
Date: Thu, 1 May 2025 20:38:57 -0700
Subject: [Nfd-dev] NDN Weekly Call
Message-ID: <CAAmG7oYFid_ySqFw60x-xhPen3fBj8NMKreBDy8BFZnJ-PvEng@mail.gmail.com>

This is a reminder of the upcoming NDN 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 AgendaNDNComm 2025 Debriefing

   - What have we learned from NDNComm 2025?
   - Any missed issues?
   - Should we write a summary report?

Jacob Zhi: new prefix injection designTestbed 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?

>From NDN Weekly Call workspace on Ownly

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/20250501/41fa5b88/attachment-0001.htm>

From awlane at memphis.edu  Fri May  2 14:42:40 2025
From: awlane at memphis.edu (Alexander Wilhelm Lane (awlane))
Date: Fri, 2 May 2025 21:42:40 +0000
Subject: [Nfd-dev] Update on questions about NLSR capture flags
Message-ID: <CH3PR16MB58427053C6ACDFB0376FB41AD78D2@CH3PR16MB5842.namprd16.prod.outlook.com>

Good afternoon,

Realized I had forgotten to follow up on this at the NDN call this week.

Currently, the behavior in NLSR regarding prefix inheritance is to set locally advertised prefixes/prefixes from Name LSAs to have the capture flag set, along with the various router/LSA/sync prefixes. This was called into question, and I suspect that the original change which implemented this is most partially incorrect as it cited this Redmine issue specifically (https://redmine.named-data.net/issues/1841) which would not entail setting those flags for advertised prefixes, just the ones related to NLSR function. I believe I found the point in the code where this is being set and should just be able to modify it to not set the capture flag on locally advertised prefixes/prefixes from Name LSAs, but I wanted to get feedback before submitting such a change.

Thanks,
Alex Lane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20250502/f42790dd/attachment.htm>

From lixia at cs.ucla.edu  Fri May  2 21:48:09 2025
From: lixia at cs.ucla.edu (Lixia Zhang)
Date: Fri, 2 May 2025 21:48:09 -0700
Subject: [Nfd-dev] Update on questions about NLSR capture flags
In-Reply-To: <CH3PR16MB58427053C6ACDFB0376FB41AD78D2@CH3PR16MB5842.namprd16.prod.outlook.com>
References: <CH3PR16MB58427053C6ACDFB0376FB41AD78D2@CH3PR16MB5842.namprd16.prod.outlook.com>
Message-ID: <998D6DC7-E487-48B5-8C72-97F9DCB4B317@cs.ucla.edu>

Alex, thanks for looking into it. 
As everyone knows, I dont code. Having said that, I agree with you on just removing the capture flag for advertised prefixes.

Lixia

> On May 2, 2025, at 2:42?PM, Alexander Wilhelm Lane (awlane) via Nfd-dev <nfd-dev at lists.cs.ucla.edu> wrote:
> 
> Good afternoon,
>  
> Realized I had forgotten to follow up on this at the NDN call this week.
>  
> Currently, the behavior in NLSR regarding prefix inheritance is to set locally advertised prefixes/prefixes from Name LSAs to have the capture flag set, along with the various router/LSA/sync prefixes. This was called into question, and I suspect that the original change which implemented this is most partially incorrect as it cited this Redmine issue specifically (https://redmine.named-data.net/issues/1841) which would not entail setting those flags for advertised prefixes, just the ones related to NLSR function. I believe I found the point in the code where this is being set and should just be able to modify it to not set the capture flag on locally advertised prefixes/prefixes from Name LSAs, but I wanted to get feedback before submitting such a change.
>  
> Thanks,
> Alex Lane 
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu <mailto: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/20250502/dfce649a/attachment.htm>

From bradlowe at g.ucla.edu  Thu May  8 20:43:41 2025
From: bradlowe at g.ucla.edu (Bradford Lowe)
Date: Thu, 8 May 2025 20:43:41 -0700
Subject: [Nfd-dev] NDN Weekly Call
Message-ID: <CAAmG7oba5+Mmm5YHcJM_2t_498ALDA76LLjcS4BNc=1gQ56WPw@mail.gmail.com>

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

Due to an expired certificate issue, the call agenda on Ownly has not been
updated.

>From NDN Weekly Call workspace on Ownly

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/20250508/4047e927/attachment-0001.htm>

From bradlowe at g.ucla.edu  Thu May 15 21:59:43 2025
From: bradlowe at g.ucla.edu (Bradford Lowe)
Date: Thu, 15 May 2025 21:59:43 -0700
Subject: [Nfd-dev] NDN Weekly Call
Message-ID: <CAAmG7oZYpc=AdyES2SYyXhJG41sC_oZ9CUiHXXnUDRw+fdvRHw@mail.gmail.com>

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

>From NDN Weekly Call workspace on Ownly

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/20250515/c362ba31/attachment.htm>

From bradlowe at g.ucla.edu  Thu May 22 20:23:58 2025
From: bradlowe at g.ucla.edu (Bradford Lowe)
Date: Thu, 22 May 2025 20:23:58 -0700
Subject: [Nfd-dev] NDN Weekly Call
Message-ID: <CAAmG7oYBhuRPzzX=MpAYTUNpG0Zyj4NT90c5RqR9rE0SM5x0uw@mail.gmail.com>

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

   - Mininet and associated projects may no longer be maintained; ~2 years
   since last PR merged
   - The above do not cleanly install on recent fresh install of Ubuntu
   24.04 LTS (22.04 is fine)
   - Pros/Cons of forking Mininet; who hosts, who maintains?

NDNComm 2025 Debriefing

   - What have we learned from NDNComm 2025?
   - Any missed issues?* Should we write a summary report?

Jacob Shi: new prefix injection designTestbed 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?

>From NDN Weekly Call workspace on Ownly

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/20250522/6548ab9e/attachment.htm>

From bradlowe at g.ucla.edu  Thu May 29 23:06:24 2025
From: bradlowe at g.ucla.edu (Bradford Lowe)
Date: Thu, 29 May 2025 23:06:24 -0700
Subject: [Nfd-dev] NDN Weekly Call
Message-ID: <CAAmG7oY4FXK2KjyjNmVhvk3FN+cNHz5EZvCa489eb2TpO3-mww@mail.gmail.com>

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

   - Mininet and associated projects may no longer be maintained; ~2 years
   since last PR merged
   - The above do not cleanly install on recent fresh install of Ubuntu
   24.04 LTS (22.04 is fine)
   - Pros/Cons of forking Mininet; who hosts, who maintains?

NDNComm 2025 Debriefing

   - What have we learned from NDNComm 2025?
   - Any missed issues?
   - Should we write a summary report?

Jacob Shi: new prefix injection design

https://redmine.named-data.net/issues/5348#note-12
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?

>From NDN Weekly Call workspace on Ownly

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/20250529/4d523cb9/attachment.htm>