[ndnSIM] Question on FIB matching

[Alex Afanasyev]

Hi Asit,

The currently implemented way always attempts to lookup FIB and create PIT entry for incoming interest, and if there is a CS match, such a PIT entry will be immediately satisfied.

The main reason behind this implementation is to unify metric calculation: for every interest there will always be either new or existing PIT entry, and every satisfied interest can be tracked via PIT entry satisfaction.  It is technically possible to change the implementation, but I'm not yet sure if this would get any major benefits.

As for last question.  Yes, it is assumed that there is always some FIB entry, at least a default entry for root prefix, that can match incoming interests.  And if there is no such entry, then NDN router is not willing to do anything with such interests.

Do you have a specific scenario where this assumption doesn't hold?  It is relatively easy to create an alternative forwarding strategy with slightly different processing logic.

---
Alex

On May 8, 2013, at 3:31 PM, Asit Chakraborti <Asit.sc.Chakraborti at huawei.com> wrote:

> Hi Alex,
>  
> My understanding of the code could be wrong, but it seems we require a FIB match on an incoming
> Interest even before a CS match. Any historical reason behind this ? Or is it just the fact that with
> the current model and APIs, a FIB entry usually exists if the content is in content store ?
>  
> Thanks,
> Asit.
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20130508/ac486791/attachment.html>