[Ndn-interest] Repo-ng freshness period
shijunxiao at email.arizona.edu
Mon Dec 12 10:47:47 PST 2016
repo-ng cannot modify FreshnessPeriod on Data packets because it does not
possess the signing key. Instead, the producer who creates and signs the
Data should set FreshnessPeriod prior to inserting the Data into
NFD does not erase Data whose FreshnessPeriod has expires from the
ContentStore, because stale Data is still valid Data, and can be retrieved
by an Interest without MustBeFresh selector. Stale Data cannot satisfy an
Interest whose MustBeFresh selector is set.
Staleness can be considered in a CS policy. For example, the priority_fifo
policy evicts stale Data before fresh Data. This eviction occurs only if CS
is full; stale Data won't be erased just because it becomes stale, and
would stay indefinitely if the CS is never full.
On Mon, Dec 12, 2016 at 8:39 AM, Matteo Bertolino <
Matteo.Bertolino at eurecom.fr> wrote:
> I would like to modify the repo-ng source code in order to put a Freshness
> period on the data that it returns.
> I tried to insert the modification immediately before each
> "face.put(*data)" making a research in the souce code with "grep" tool.
> Unfortunately, the data published continues to stay indefinitely inside
> the content store of the intermediate nodes.
> Where can I inject my modification?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest