[Nfd-dev] Proposed NDN spec change

Alex Afanasyev alexander.afanasyev at ucla.edu
Wed Jun 10 21:21:31 PDT 2015


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.

---
Alex

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150610/28964bdc/attachment.bin>


More information about the Nfd-dev mailing list