[Nfd-dev] [Ndn-app] Close NFD backdoor

[Dave Oran (oran)]

___________________________
iDevice - please excuse typos.

On Sep 8, 2014, at 6:21 PM, Yingdi Yu <yingdi at cs.ucla.edu<mailto:yingdi at cs.ucla.edu>> wrote:


On Sep 8, 2014, at 12:58 PM, Dave Oran (oran) <oran at cisco.com<mailto:oran at cisco.com>> wrote:

I don’t mean to hijack this thread, but it seems that the architecture needs two cache timers, not one.

One is an Expiry timer after which the data is no longer considered valid (and hence should not be returned from the cache if an interest arrives)

I am not sure if it is always possible for a data producer to predict the time when the data will become invalid.
If not the producer, then who? All data kept outside an application's private (and possibly permanent) store has a validity period, if not shorter then at least no longer than the lifetime of the key that signed it.

Take DNS as an example, the authoritative server may never know when one of the records will be changed.

Wrong analogy. A DNS Authoritative server is like a repo, a producer is in effect the application that updated the DNS.

Yingdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140909/f81f5a12/attachment.html>