Project

General

Profile

Handles synchronization logic of NLSR LSDB updates » History » Version 3

A K M Mahmudul Hoque, 04/20/2014 10:15 PM

1 1 A K M Mahmudul Hoque
Handles synchronization logic of NLSR LSDB updates
2
==================================================
3
4
### 1. Syncing LSDB
5
6
- NLSR's Syncing Logic Handler (SLH) handles syncing logic of LSDB
7
- SLH publishes updates on name \<router-prefix\>
8
- SLH pushes sequence number to ChronoSync instead of letting ChronoSync generating it for NLSR
9 3 A K M Mahmudul Hoque
- 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.
10
- 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.
11 1 A K M Mahmudul Hoque
- Checks LSAs version with LSDB
12
- If SLH finds newer version of LSAs, it communicates with InterestManager to send interest for LSAs
13
14
- SLH also stores this sequence number in local store and retrieve the last sequence number used when boot up
15
16
17
### 2. Syncing Certificates
18 2 A K M Mahmudul Hoque
- SLH publishes updates on name \<certificate-name\>
19 1 A K M Mahmudul Hoque
- Sequence number is pushed from SLH
20
- Upon updates notification reception, checks with certificate store
21
- If newer version of certificate found, communicates with InterestManager to send interest
22
23
- Stores Certificate sequences like LSDB sequences and retrieves when boot up