| Ashlesh Gawande | 9e955bc | 2017-11-30 17:33:03 -0600 | [diff] [blame] | 1 | NLSR version 0.1.0 (initial release) |
| 2 | ++++++++++++++++++++++++++++++++++++ |
| 3 | |
| 4 | Release date: August 25, 2014 |
| 5 | |
| 6 | The main design goal of NLSR is to provide a routing protocol to populate `NFD's |
| Alexander Afanasyev | 67758b1 | 2018-03-06 18:36:44 -0500 | [diff] [blame^] | 7 | <https://named-data.net/doc/NFD/>`_ RIB. NLSR calculates the routing table using |
| Ashlesh Gawande | 9e955bc | 2017-11-30 17:33:03 -0600 | [diff] [blame] | 8 | link-state or hyperbolic routing and produces multiple faces for each reachable name |
| 9 | prefix in a single authoritative domain. |
| 10 | |
| 11 | **Included features**: |
| 12 | |
| 13 | - Advertise availability of content through the configured router |
| 14 | |
| 15 | - Use `ChronoSync <https://github.com/named-data/ChronoSync>`_ to synchronize routers' LSA sequence numbers and Interest/Data to retrieve LSAs |
| 16 | |
| 17 | - Produce a list of ranked forwarding options for each name prefix to facilitate NDN's adaptive forwarding strategies |
| 18 | |
| 19 | - Configure maximum number of faces per prefix in NFD’s RIB |
| 20 | |
| 21 | - Set up NFD tunnels to neighbors automatically and maintain the tunnels to neighbors |
| 22 | |
| 23 | - Provide two routing protocols: |
| 24 | |
| 25 | + Link State routing: calculate route cost based on link costs |
| 26 | + Hyperbolic routing: calculate route cost based on hyperbolic coordinates |
| 27 | |
| 28 | - Use a hierarchical trust model for routing within a single administrative domain |
| 29 | |
| 30 | - Keep NFD’s RIB updated on failure and recovery |