[Ndn-interest] Producing new contents with same name

[Junxiao Shi]

Hi Jongdeog

1. Is it allowed to produce different contents with same name?
>
No, it violates data immutability as required by NDN protocol design
principles <https://named-data.net/project/ndn-design-principles/>.

2. If it is allowed, what would be a conventional way to implement it? My
> thoughts are:
> - the interest of the consumer 'must be fresh'
> - the producer produces the contents with the minimal freshness period (0
> or 1).
>
> 3. If there is any other conventional way of fetching the newest version
> of contents, please let me know. As we discussed in the NDN seminar, the
> selector (right most child) does not solve the problem as it can sometimes
> retrieve old cached data.
>
You may use iterative version discovery
<https://github.com/named-data/ndn-tools/blob/25625ca1a06d5f6e0a1c8c9b88303a8a2b6d19a7/tools/chunks/catchunks/discover-version-iterative.hpp>:
use ChildSelector=rightmost to find a version, then express another
Interest that excludes that and all lower versions, repeat until you are
unable to retrieval any newer versions. A drawback is that there needs to
be a timeout <https://redmine.named-data.net/issues/3793> to complete this
version discovery procedure.
So far, no valid alternative solution has been proposed. You may post your
idea in #3793.

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170208/a6158320/attachment.html>