[ndnSIM] Trace driven simulation

[Alex Afanasyev]

Hi Saran,

Yes, this is definitely a good idea and we were actually planning to do something similar, but haven't done anything yet.

There are a couple of ways you can make the trace-driven consumer.  One way is to have a simple list of interest names, and then it should be consumer app that decides when exactly it wants to start requesting them.  Another way is to have a list of names and (relative) times when these interests needs to be send out.   

In either case, you would need to write a completely new consumer implementation, since the ones that are in ndnSIM assume sequence number as essential part of the name (last component), which simplifies some logic with interest retransmission.  Without this assumption (if you still need retransmission), you will need to keep track of the whole names of expressed interests.

I have actually started some work to add richer NDN API for writing applications (e.g., you create a handler, express interests through handler, handler notifies you when data arrives or when there is a timeout), but the work is still in its very beginning and I don't even have a compilable/usable code to show yet.

--
Alex


On Jun 19, 2013, at 4:37 AM, Saran Tarnoi <sarantarnoi at gmail.com> wrote:

> Dear All,
> 
> I think it may be a good idea to have a TraceDriven Consumer app in ndnSIM.
> The concept is letting a consumer generates a number of interests whose names are read from a trace file.
> It will give more freedom to simulation scenario regarding the request traffic model.
> 
> Could you give me an idea to make it?
> Thank you for your time.
> 
> -- 
> Regards,
> Saran Tarnoi