[ndnSIM] Freshness value handling

[Samar Alduayji]

Thanks for replying Lixia, really appreciate it.


*1/ wonder why you are interested in carrying (x-y seconds) in the packet?
(Playing with cache management?)*


 The idea is to keep trake of the accurate remaining data lifetime.
So how would a node or a consumer knows if a packet is expired or became
stale without considering how much it stayed in the previous CS? How the
freshness period will be decreased over the caching and transmission time?
Is there any other indicator for that?

Regards,
Samar


On Wed, 3 Feb 2021, 5:15 pm Lixia Zhang, <lixia at cs.ucla.edu> wrote:

>
> > On Feb 3, 2021, at 2:04 AM, Samar Alduayji via ndnSIM <
> ndnsim at lists.cs.ucla.edu> wrote:
> >
> > Dear All,
> >
> > I just have a question regarding handling the freshness value of data
> packet when it is sent from one node to another.
> > i.e. when a data packet is cached in node A with freshness value ( ttl)
> of x seconds, then after y seconds the data is retrieved to be send to
> another node B. Will the freshness value stay x seconds or there is a
> process that it implemented within the ndnsim to change it to x-y seconds?
>
> ndnSIM follows NDN design.
> By design the whole data packet, including the freshness period, is signed
> by the original producer (cannot be changed by other parties).
>
> 1/ wonder why you are interested in carrying (x-y seconds) in the packet?
> (Playing with cache management?)
>
> 2/ to experiment, someone suggested earlier the idea of attaching such a
> value to the data packet (e.g. by NDNLP), I dont think ndnSIM itself does
> it.
>
> > If there is such a handling function that is already implemented can you
> please point it out for me?
> >
> > Kind Regards
> > _______________________________________________
> > ndnSIM mailing list
> > ndnSIM at lists.cs.ucla.edu
> > http://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/20210203/129ea2ce/attachment.html>