[Ndn-interest] Forwarding interest to different faces

Susmit susmit at cs.colostate.edu
Mon Jul 10 10:02:50 PDT 2017

On Mon, Jul 10, 2017 at 10:56 AM, Mohammad Alhowaidi
<malhowaidi at gmail.com> wrote:
> Thank you for the reply. If the data is big and segmented into several
> chunks, ist possible to retrieve different chunks from different faces? like
> chunk1 from face1 and chunk2 from fac2 ? do I need to change the forwarding
> strategy to do that?

Yes, strategy would be the place to do it.

The code here does exactly what you described:

Note that the code is old and you might need to change it a bit to
match the latest ndn-cxx library API. I have not tested it recently.

> Thanks,
> Mohammad
> On Sun, Jul 9, 2017 at 10:25 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>> Hi Mohammad
>> Yes, a router is free to choose whatever path it thinks can reach the
>> Data. Forwarding strategy is the component that makes this decision.
>> However, if the Data has been retrieved from face1 and is still present in
>> the local cache, the router would return the cached Data when the same
>> Interest arrives the second time, instead of forwarding the Interest again
>> to face2.
>> Yours, Junxiao
>> On Sun, Jul 9, 2017 at 6:58 PM, Mohammad Alhowaidi <malhowaidi at gmail.com>
>> wrote:
>>> Hello,
>>> If I have an interest with prefix /ndn/a/b and it reach a router which
>>> has multiple entry to forward it for example the FIB look like
>>> /ndn/a/b , face1
>>> /ndn/a/b , face 2
>>> Can the router choose to forward the interest to face 1 in the first
>>> time, and if it receive the same interest again, then it will be forwarded
>>> into face2? so the interest will follow different path from time to time.
>>> Thanks,
>>> Mohammad
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest



More information about the Ndn-interest mailing list