[Ndn-interest] Packet Format v0.3: semantics of FreshnessPeriod=0

[Lixia Zhang]

this reply is just to close the loop for others on the mailing list: as we discussed during NFD call today, yes you got it right.

> On Mar 26, 2018, at 1:01 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> 
> Dear folks
> 
> I have a question regarding the semantics of FreshnessPeriod=0 in Packet Format v0.3.
> 
> The protocol says <https://named-data.net/doc/NDN-packet-spec/current/data.html#freshnessperiod>:
> If the Data does not have a FreshnessPeriod or if it has a FreshnessPeriod equal to zero, it MUST be immediately marked “non-fresh”.
> If an Interest contains MustBeFresh element, a node MUST NOT return “non-fresh” Data in response to this Interest. The effect is the same as if that “non-fresh” Data did not exist (i.e., the Interest might be matched by some other Data in the store, or, failing that, get forwarded to other nodes).
> 
> My question is:
> A node receives an Interest containing MustBeFresh element from downstream, and forwards the Interest to upstream.
> The upstream returns a Data with FreshnessPeriod=0.
> At this moment, can the node return this Data to downstream?
> 
> From my understanding of the protocol, upon receiving the Data, it is already "non-fresh". Since "non-fresh" Data cannot satisfy an Interest containing MustBeFresh element, this Data cannot go to downstream.
> Is this understanding correct?
> 
> Yours, Junxiao
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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