[Ndn-interest] DDSN - Distributed Dataset Synchronization in Disruptive Networks
Jeff.White at dell.com
Sun Feb 21 19:11:55 PST 2021
From: Zhaoning Kong <jonnykong at cs.ucla.edu>
Sent: Sunday, February 21, 2021 9:09 PM
To: Lixia Zhang
Cc: White, Jeff; ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] DDSN - Distributed Dataset Synchronization in Disruptive Networks
Please see the following link for the latest SVS (the new DDSN) implementation:
On Sun, Feb 21, 2021 at 1:46 PM Lixia Zhang <lixia at cs.ucla.edu<mailto:lixia at cs.ucla.edu>> wrote:
On Feb 21, 2021, at 9:51 AM, White, Jeff via Ndn-interest <ndn-interest at lists.cs.ucla.edu<mailto:interest at lists.cs.ucla.edu>> wrote:
Dell Customer Communication - Confidential
This exchange is on a public mailing list, so I assuming nothing I can be confidential :-)
Hell NDN Community:
We are working on a research problem and I noted DDSN has some very desirable aspects for solving our challenge.
Great to hear.
BTW we renamed and revised DDSN to SVS, state-vector sync (simpler), and made a new spec and implementation (hope someone could help with a pointer)
Below are just some personal view; others may chip in with different opinions.
• How is group membership regulated – how do you join a DDSN group? How do you exit?
1/ Group membership is really app level decision, not by the protocol.
2/ physically a member just needs to be able to send and receive the sync interest.
* Sending: requires one be a legit member (i.e. get necessary crypto credential);
* Receiving: ideally the network should be doing multicast delivery of sync interests to only the group members, that require members make necessary routing announcements and forwarders use multicast strategy (to cheat in a small setting, forwarders could just broadcast anything that they suppose to apply multicast strategy)
Exit: you mean kicking someone out? Just revoke the credential
• I remember from Vectorsync that scale in terms of membership could be an issue as the state vector increases linearly with number of participants. Is this an issue for DDSN, what is the practical limit in group size?
If you meant the original vectorsync: its sync interests carry an ordered list of the latest seq# of each producer, without producer names.
Started from DDSN (now SVS), the protocol uses a state vector of [producer, seq#]. This change not only removed the need for strict synchronization of the membership among all the participants all the time, but also opened the door of letting each sync interest carry a partial, instead of complete, state vector.
Any insight would be helpful.
Curious what kind of problems you are thinking about applying SVS to.
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest