[Nfd-dev] Default for missing AnswerOriginKind vs. MustBeFresh

[Thompson, Jeff]

If anyone wants to comment, here is the added text for the changes that applications need to make:

Changed default semantics of staleness.

Specifically, NDN-TLV Interest without any selectors will bring any data that matches the name, and only when MustBeFresh selector is enabled it will try to honor freshness, specified in Data packets. With Binary XML encoded Interests, the default behavior was to bring “fresh” data and return “stale” data only when AnswerOriginKind was set to 3.

Application developers must be aware of this change, reexamine the Interest expression code, and enable MustBeFresh selector when necessary.

From: Alex Afansyev <alexander.afanasyev at ucla.edu<mailto:alexander.afanasyev at ucla.edu>>
Date: Friday, March 7, 2014 2:14 AM
To: Jeff Thompson <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>
Cc: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>, NDN Lib <ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>>, nfd-dev <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] [Ndn-lib] Default for missing AnswerOriginKind vs. MustBeFresh

I have updated the spec, adding the suggested blurb (I put it before in ndnd-tlv redmine wiki, but forgot to propagate in other places).

---
Alex

On Mar 6, 2014, at 2:05 AM, Thompson, Jeff <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:

Thanks for the reply.

Perhaps this should be noted in the "Changes from CCNx" section.
http://named-data.net/doc/ndn-tlv/interest.html#changes-from-ccnx

Thanks,
- Jeff T

From: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>
Date: Wednesday, March 5, 2014 5:32 PM
To: Jeff Thompson <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>, NDN Lib <ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>>
Cc: nfd-dev <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Ndn-lib] Default for missing AnswerOriginKind vs. MustBeFresh

Hi JeffT
Yes, this definition is intentional.
It’s okay for the library to specify MustBeFresh=true by default.
Yours, Junxiao


"Thompson, Jeff" <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:
Hello.

In a CCNx interest, if the AnswerOriginKind interest selector was absent, the forwarder would treat it as allow stale = False.  But in the new TLV format, if the MustBeFresh selector is absent the spec says the default is to allow stale = True.
http://named-data.net/doc/ndn-tlv/interest.html#mustbefresh

Is this change to default behavior intentional?

Thanks,
- Jeff T


________________________________

Ndn-lib mailing list
Ndn-lib at lists.cs.ucla.edu<mailto:Ndn-lib at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-lib

_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140307/0de9c176/attachment.html>