ndnSIM

I have another idea. There is no real value of including interest hop count, as data must follow path of Interests. So, I would propose change the way hop count is measured (the original measure is/was confusing anyways).

Yeah, I have also thought of that, but I wanted to provide the same functionality as before.
So, you suggest that I measure only the hops for the interest packet and just double that for the data packet?
I like the fact that the calculation now is symmetric... I mean as far as the code structure is concerned...

No. There is no reason to double. The measure will just measure number of hops a packet has traveled. If someone is interested in number of hops Interest traveled, they can measure that in producer app. If someone wants to measure hops of Data packets, they can look for that inside consumer. If someone wants total count of hops for Interest + Data, then they always just multiply, but I don't think this is what people are really interested in.

So we will have two independent counters in an essence, right?
Ok, I can do that..

Addressed.