[Nfd-dev] Update on questions about NLSR capture flags

[Lixia Zhang]

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>