alexander.afanasyev at ucla.edu
Mon Feb 11 09:22:33 PST 2013
There is some description about NACKs in our paper http://dx.doi.org/10.1016/j.comcom.2013.01.005
For the implementation, only routers generate NACKs, and this code is part of specialized forwarding strategy extension "ns3::ndn::fw::Nacks" (model/fw/nacks.h and model/fw/nacks.cc).
Currently, all existing forwarding strategies have this extension, but NACKs generation is disabled by default. At the same time, just enabling NACKs for strategy like BestRoute or Flooding could only trigger NACKs with code NACK_LOOP and NACK_GIVEUP_PIT (in some cases). For congestion related behavior described in the paper, you would want to use specialized strategy that enforces some kind of Interest limits (e.g., ns3::ndn::fw::BestRoute::PerOutFaceLimits).
You can check out and play with the congestion scenario that was used for the paper here: https://github.com/cawka/ndnSIM-comcom-stateful-fw
On Feb 11, 2013, at 9:09 AM, Natalya Rozhnova <natalya.rozhnova at lip6.fr> wrote:
> Hi all,
> I have a question about NACK implementation in NDNSim. I'm just wondering how it is working in existing ndnSIM code. Who generates and sends NACK packets: producer or routers?
> Also, could you please refer me to the function generating and sending NACK?
> Thanks a lot,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ndnSIM