[Nfd-dev] Proposed NDN spec change

Burke, Jeff jburke at remap.ucla.edu
Wed Jun 10 21:27:01 PDT 2015


Can you explain the motivating use case(s)?  
Would it make sense to provide a way to encode whether the packet should be considered "always fresh" or "always stale" explicitly?

On 6/10/15, 9:21 PM, "Nfd-dev on behalf of Alex Afanasyev" <nfd-dev-bounces at lists.cs.ucla.edu on behalf of alexander.afanasyev at ucla.edu> wrote:

>Dear all,
>The current NDN spec defines that Data packets without FreshnessPeriod are considered always fresh ("data packet cannot be marked stale", http://named-data.net/doc/ndn-tlv/data.html#freshnessperiod).
>This creates a problem for some applications that we are currently playing with and I would like the spec (and subsequently NFD implementation) to be changed to do the opposite:  when FreshnessPeriod is not specified, data packet should **never** be considered fresh.
>We have discussed this issue in the past (http://redmine.named-data.net/issues/2440), but haven't finalized the decision.  If there are no objections, I would like to proceed with the change ASAP.

More information about the Nfd-dev mailing list