[Ndn-interest] NFD flag clarification

[Vince Lehman (vslehman)]

Hi Tai-Lin,

Is this understanding correct?
Yes, I think you have the general idea.

The CHILD_INHERIT flag, when applied to a route, allows a longer child name prefix to use that route for forwarding. It adds the route as an option to the FIB, but the route used to forward the Interest is up to the strategy. A parent prefix with a route without the CHILD_INHERIT flag will not be added to the FIB entry for a longer prefix.

CAPTURE prevents a name prefix and longer children prefixes from using a route associated with a shorter parent name prefix. The CAPTURE flag will not only prevent inheritance for the same name prefix but also longer children prefixes.

What is the use case of capture?
The capture flag can be used to prevent traffic for a prefix from flowing to another route.

For example, if laptop 1 registers /A with CHILD_INHERIT and laptop 2 registers /A/B with no flags, traffic for /A/B can be forwarded to both laptop 1 and 2.

If laptop 2 instead registers /A/B with the CAPTURE flag, traffic for /A/B will be forwarded to laptop 2 and will not be forwarded to laptop 1.

--
Vince Lehman

On Apr 22, 2015, at 3:54 PM, Tai-Lin Chu <tailinchu at gmail.com<mailto:tailinchu at gmail.com>> wrote:

http://redmine.named-data.net/projects/nfd/wiki/RibMgmt

Is this understanding correct?
CHILD_INHERIT: true = usual lpm, false = exact matching
CAPTURE: prevent lpm to be used (in other entries with the same name)

What is the use case of capture?


Thanks.
_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150504/4173936a/attachment.html>