[Ndn-interest] Repo-ng freshness period

Matteo Bertolino Matteo.Bertolino at eurecom.fr
Mon Dec 12 14:53:11 PST 2016

Dear Junxiao,
I understand (finally) what you mean.
Since I generate the certificates with ndnsec, is there a method to  
obtain that?

Thanks a lot,
Bests, Matteo

Quoting Junxiao Shi <shijunxiao at email.arizona.edu>:

> Hi Matteo
> You should change the program that generates and signs the certificate to
> add FreshnessPeriod, not repo-ng.
> If you patch repo-ng to update the certificate, it would not be valid
> anymore because the FreshnessPeriod is protected by the signature.
> Yours, Junxiao
> On Mon, Dec 12, 2016 at 3:27 PM, Matteo Bertolino <
> Matteo.Bertolino at eurecom.fr> wrote:
>> 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 other
>> application.
>> 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.

This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

More information about the Ndn-interest mailing list