Handles synchronization logic of NLSR LSDB updates » History » Revision 3
Revision 2 (A K M Mahmudul Hoque, 04/17/2014 06:15 AM) → Revision 3/4 (A K M Mahmudul Hoque, 04/20/2014 10:15 PM)
Handles synchronization logic of NLSR LSDB updates ================================================== ### 1. Syncing LSDB - NLSR's Syncing Logic Handler (SLH) handles syncing logic of LSDB - SLH publishes updates on name \<router-prefix\> - SLH pushes sequence number to ChronoSync instead of letting ChronoSync generating it for NLSR - Sequence number is composed from the version number of Adjacency LSA, Prefix LSA and Hyperbolic LSA: 64 bit sequence number is composed as follows a. 40-59th bit represents Name LSA sequence number b. 20-39th bit represents Hyperbolic LSA sequence number c. 0-19th bit represent Adjacency LSA sequence number and 60-64th bit is unused at this moment. As ChronoSync needs strictly increasing sequence number, composing of sequence number follows that. - When SLH receives updates notification it decomposes the sequence number and retrieves version for LSAs. Decomposing is sequence number is done to get the LSA Sequence/Version number from ChronoSync sequence number. LSAs - Checks LSAs version with LSDB - If SLH finds newer version of LSAs, it communicates with InterestManager to send interest for LSAs - SLH also stores this sequence number in local store and retrieve the last sequence number used when boot up ### 2. Syncing Certificates - SLH publishes updates on name \<certificate-name\> - Sequence number is pushed from SLH - Upon updates notification reception, checks with certificate store - If newer version of certificate found, communicates with InterestManager to send interest - Stores Certificate sequences like LSDB sequences and retrieves when boot up