[Nfd-dev] NFD with a broadcast prefix

[Thompson, Jeff]

Hello. I'm working with the ndn-cpp implementation of ChronoSync as described in the 2013 paper “Let’s ChronoSync: Decentralized Dataset State Synchronization in Named Data Networking” and used in the related ChronoChat.

User A and user B are running ChronoChat on separate computers. They register to receive interests for the same broadcast prefix "/ndn/broadcast/ChronoChat-0.3/ndnchat". When the users get a new root hash, they both express the same interest, e.g. "/ndn/broadcast/ChronoChat-0.3/ndnchat/4aa4". User B should receive the interest from user A and vice versa.

When I run this on ndnd-tlv, the broadcast insterest is always forwarded to the other user. But on NFD, sometimes the interest is not forwarded. When I turn on NFD logging TRACE, I see user A sends the interest and it is forwarded to user B. But user B sends the interest and it is not forwarded to user A.

Can you think of why NFD might have this behavior?  (Under the default routing strategy it may be a feature, not a bug.) Or what I should do to get the full broadcast behavior?

Thanks,
- Jeff T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141007/b448df4e/attachment.html>