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

[Thompson, Jeff]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140306/4892d5e0/attachment.html>