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

Burke, Jeff jburke at remap.ucla.edu
Wed Mar 5 16:58:08 PST 2014



From: "Thompson, Jeff" <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>
Date: Thu, 6 Mar 2014 00:47:07 +0000
To: NDN Lib <ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>>
Subject: [Ndn-lib] Default for missing AnswerOriginKind vs. MustBeFresh

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

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


More information about the Nfd-dev mailing list