[Ndn-interest] LSDB in NLSR

Tanusree Chatterjee tnsr.chatterjee at gmail.com
Sat Jun 25 04:36:38 PDT 2016

Hi all,

Previously, in NLSR we can see that Sync computes a hash tree over all the
data in a slice (of LSDB) that exchange the root hash between neighbors to
detect inconsistencies. If the hash value do not agree, then two
neighboring nodes exchange the hash value of nodes on the next tree level
until they detect the specific leaf nodes (data) causing the problems.
While NLSR using chronosync every party keeps an outstanding sync interest
with the current state digest.As soon as some party generates new data, the
state digest changes, and the outstanding interest gets
satisfied. ChronoSync module on her machine immediately noticesits state
digest is newer and hence proceeds to satisfy the sync interest with sync
data that contains the name of LSA. Whoever receives the sync data updates
the digest tree to reflect the new change to the dataset state, and sends
out a new sync interest with the updated state digest, reverting the system
to a stable state.

So, using chronosync, it reduces too much message exchanges than the
previous sync protocol? While there is a change in the digest, the
outstanding interest is satisfied by the LSA name itself which causes the
change? It is in form of a ndn data packet thus preserving the integrity as
well? What changes it has now in security while disseminating LSAs?

-- Regards,
Tanusree Chatterjee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160625/df32316e/attachment.html>

More information about the Ndn-interest mailing list