[Ndn-interest] Question about unsatisfied Interests
David R Oran
David at OrandomNAS2.FamilyDS.net
Wed Oct 15 08:58:59 PDT 2014
On Oct 15, 2014, at 11:37 AM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> Hi Marc
> There's no such field. We only have FreshnessPeriod.
Right. And as I’ve pointed out in the past, this is in my opinion this is a bug/missing feature.
We need to separate data validity period from cache retention period. The former has to be baked into the data object for security reasons, the latter probably does not.
> By staleness definition, when the Data arrives at B, it's fresh until FreshnessPeriod has elapsed, regardless of how it's requested.
> Yours, Junxiao
> On Wed, Oct 15, 2014 at 8:33 AM, <Marc.Mosko at parc.com> wrote:
> 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?
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
More information about the Ndn-interest