[ndnSIM] [EXT] must-be-fresh problem

Junxiao Shi shijunxiao at email.arizona.edu
Fri Jul 8 10:25:25 PDT 2022


Hi Amir

This behavior is by design.

An Interest with MustBeFresh can only be satisfied by a Data with non-zero
FreshnessPeriod.
When FreshnessPeriod is omitted, it is equivalent to being set to zero.

Yours, Junxiao

On Fri, Jul 8, 2022 at 12:29 PM Esmaeili, Amir (Student) <ae3wc at umsl.edu>
wrote:

> *External Email*
> Hi
> I want to make an experiment that focuses on must-be-fresh tag. For this
> aim I do the following steps:
>
>    1. First of all, my simulation is dedicated to window-based consumers,
>    and for enabling must-be-fresh tag in Interenst requests I edited
>    ndn-consumer.cpp SendPacket() function, and added this code:
>    interest->setMustBeFresh(true);
>    2. Then, I started the simulation, unfortunately, after 1 second
>    consumers stop sending interest.
>    3. I found If I set a none zero value to the ndn::Producer::Freshness
>    parameter that normally is zero, the problem will solve, and consumers
>    continue sending requests.
>
> Could you please tell me whether I correctly enabled the must-be-fresh tag
> or not?
> Sincerely.
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> https://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20220708/3bc195f5/attachment.html>


More information about the ndnSIM mailing list