NFD » ndn-tools

+1

Can we replicate options of actual ping command? At least some of them that make sense.

Alex Afanasyev wrote:

Can we replicate options of actual ping command? At least some of them that make sense.

Sure, I actually had the same thought. We are already diverging on -t unfortunately (it's -D in ping(8)), but several other options are applicable to ndn-ping as well (at least -AflOqswW).

On another thought about this. I think we shouldn't have any payload on the server side at all. I think we should simply add a parameter to the client that would add any random number of bytes to the name component. At least this would match IP-based ping, where ping/pongs are basically the same things.

I think we should simply add a parameter to the client that would add any random number of bytes to the name component.

ndnping client already has this ability, in the form of "client identifier", although it's not random and it's unnecessary to be random.

At least this would match IP-based ping, where ping/pongs are basically the same things.

NDN Interest is smaller than Data in the common case. Adding a payload allows one to simulate this common case, without having to use the traffic generator.

OK. Just a thought. I was also thinking to add something to interest to request payload size, but this could become a security hole.