[Ndn-interest] Repo-ng freshness period
Matteo.Bertolino at eurecom.fr
Mon Dec 12 14:27:16 PST 2016
first of all thanks. Even if you explanation seems very clear, for my
poor knowledge I have still some black holes.
Supposing that I would like to use repo-ng to store and to distribute
the certificates. I can publish a certificate, for example, writing:
base64 -d cert.ndncert | nc localhost 7376 in the very basic case.
Now, client express an interest in order to retrieve cert.ndncert.
I imagine, seeing the code, that repo-ng take the data and put the
data in the face in order to satisfy the interest. Exactly like any
I would like to avoid that another node , that desire FRESH content,
retrieve that certificate after 10 seconds on an intermediate cache.
The request should arrive to repo-ng, instead of intermediate node.
The solution you proposed is not enough for this purpose. Are you sure
that I cannot obtain this behaviour? It seems quite strange, probably
I don't explained very well what I wish.
Quoting Junxiao Shi <shijunxiao at email.arizona.edu>:
> Hi Matteo
> 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.
> Yours, Junxiao
> 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?
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
More information about the Ndn-interest