NFD

What is the target version for this bug? Should I assign it to myself and fix it?

This issue is waiting on Lixia to provide evidence that proves the confusion.

No target version will be set until the proof is in place.

I can provide some emails of ndnSIM users having been confused because of that. Actually, I received the last one some days before.

Please post the mailing list links, or attach PDFs to this issue. Two complaints shall be enough.

After that, we can set target version, and make a plan on how to do a backwards-compatible change.

Reply to note-5: I'll wait for a second complaint before believe the confusion is widespread.

I want to point out that commenting out if (pitEntry->canForwardTo(*outFace)) does not turn the strategy into "pure broadcast" (ie. sending Interest to all faces even if there's no FIB nexthop record).
The strategy is still constrained among FIB nexthop records.
This modification would allow consumer retransmission Interests to go out of all faces listed in FIB nexthop records again, even if the out-record is unexpired.

In fact, "pure broadcast" is unfeasible under current strategy API, but I intend to solve this problem in #2000.

As we discussed in NFD call 08032015, I talked with two graduate students from the Mobility First project team during the recent FIA Project meeting at MIT. Both of them had looked our codebase and asked me why we broadcast the Interests.

20150810 conference call approves the design in note-9.

Reviewer has pointed out that commit:1d470df0da0467dae7888c5474eea134c0a8a533 is missing updates in "nfd.conf.sample.in" and "documentation that references broadcast strategy".

I have identified the following places in NFD repository that references "broadcast":

• daemon/fw/broadcast-strategy.hpp and its implementation and test suite: intentional, for backwards compatibility
• nfd.conf.sample.in and daemon/mgmt/tables-config-section.cpp: should be updated
• tools/ndn-autoconfig/multicast-discovery.cpp: should be updated
• docs/manpages/nfdc.rst: should be updated
• docs/RELEASE_NOTES.rst: do not update, to preserve history

I'm getting error (did you push just as a draft?)

At 20150903 conference call, Alex confirms BroadcastStrategy can be removed before next release.

http://gerrit.named-data.net/2444 deletes BroadcastStrategy.