[Ndn-interest] application scenario
gq.wang at huawei.com
Thu Oct 23 14:28:58 PDT 2014
It seems to me the ideal approach for these syncs is a pub-sub model that A should subscribe certain "interests" at B and C, and
get some events back (if any). Once received these events (saying some prefixes), A will determine what it wants to sync.
It can be done effectively in a well-organized network (e.g., a cluster-head), or somewhat awkward in a totally ad-hoc environment.
From: Ndn-interest [mailto:ndn-interest-bounces at lists.cs.ucla.edu] On Behalf Of ndn-interest-request at lists.cs.ucla.edu
Sent: Thursday, October 23, 2014 1:55 PM
To: ndn-interest at lists.cs.ucla.edu
Subject: Ndn-interest Digest, Vol 8, Issue 10
Send Ndn-interest mailing list submissions to
ndn-interest at lists.cs.ucla.edu
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
ndn-interest-request at lists.cs.ucla.edu
You can reach the person managing the list at
ndn-interest-owner at lists.cs.ucla.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ndn-interest digest..."
1. application scenario (Lan Wang (lanwang))
2. Re: application scenario (Christos Papadopoulos)
3. Re: application scenario (Lan Wang (lanwang))
4. Send and Receive Video using jNDN Client (Bassem Labib)
5. Re: Send and Receive Video using jNDN Client (Thompson, Jeff)
6. Re: Send and Receive Video using jNDN Client (Steve DiBenedetto)
7. Immediate opening for intern for CCN/NDN project (Cedric Westphal)
Date: Tue, 21 Oct 2014 20:35:34 +0000
From: "Lan Wang (lanwang)" <lanwang at memphis.edu>
To: "<ndn-interest at lists.cs.ucla.edu>"
<ndn-interest at lists.cs.ucla.edu>
Subject: [Ndn-interest] application scenario
Message-ID: <F0792922-A263-4ED8-9D3A-14F7C2CE370F at memphis.edu>
Content-Type: text/plain; charset="us-ascii"
Suppose I have a node A that has limited memory. It wants to synchronize partial data with other nodes (B and C). The other nodes are fully synchronized with each other (they use ChronoSync). Node A wants to get updates whenever the other nodes have more recent versions of the data it has, but the other nodes do not know what A has. What's the best way to design this application? Ideally we don't want A to specifically sync with one particular node (B or C).
Here's an illustration:
* Node A has:
* Node B and C have:
Ideally A should get update about /b/v2, but not /c/v3 as it's interested in /b, not interested in /c.
We don't want to run ChronoSync on A, as it doesn't have the space for all the data and it is not interested in all the data either.
More information about the Ndn-interest