[Ndn-interest] Question about unsatisfied Interests

Marc.Mosko at parc.com Marc.Mosko at parc.com
Wed Oct 15 08:33:42 PDT 2014

So there is a field in the content object that distinguishes if it is fresh or not?  I thought there was only the FreshnessPeriod, which is a relative number from the time received and a remote node cannot determine if a content object was fresh or not when it came out of the content store.


A — B — C
D -/

Node A sends a normal (staled allowed) interest to B, who forwards it to C.  Just a bit later, node D issues a “MustBeFresh” interest for the same name.  Node B sees that they are different requests, so forwards the second interest to C also.

Node C replies to the first interest with a stale content object.  How can node B know  that the content object should only go to A and not to D?


On Oct 15, 2014, at 8:26 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Marc

Producer-generated NACK is a type of Data. It has the FreshnessPeriod field which determines how long it could be used to satisfy an Interest with Selector MustBeFresh=yes.
ContentProvider should set FreshnessPeriod to the duration in which it believes that the Data won't be generated.

Yours, Junxiao

On Wed, Oct 15, 2014 at 8:24 AM, <Marc.Mosko at parc.com<mailto:Marc.Mosko at parc.com>> wrote:
Shouldn’t the NAK have a limited lifetime?

If I ask for /news/version=100 an the provider only has version=98, it would NACK 100.  But, the provider will eventually want to publish version 100.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20141015/1eb8f6f4/attachment.html>

More information about the Ndn-interest mailing list