NDN project issue tracking system: Issueshttps://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232017-07-06T12:01:13ZNDN project issue tracking system
Redmine NLSR - Feature #4170 (New): Use ndn-cxx Dispatcher to satisfy LSA interests.https://redmine.named-data.net/issues/41702017-07-06T12:01:13ZNicholas Gordonnmgordon@memphis.edu
<p>Since NLSR is moving away from home-rolled solutions toward library-standard methods to interact with the network, we should extend this to LSAs.</p>
<ul>
<li>NLSR as a program would exclusively use the ndn-cxx-provided dispatcher to handle interests for LSAs.</li>
<li>The LSDB as a module would have no knowledge of how interests arrive, but only return an LSA upon request.</li>
</ul>
NLSR - Task #4109 (Code review): Replace NextHopList with a better containerhttps://redmine.named-data.net/issues/41092017-05-31T14:11:19ZNicholas Gordonnmgordon@memphis.edu
<p>Currently, NextHopList is implemented as a class that implements semantics that allow only one next hop in the list, which are equivalent to a set. Further, it implements comparison semantics for NextHopLists. We should use a container that suits the requirements better.</p>
NLSR - Feature #3948 (New): Multiple network supporthttps://redmine.named-data.net/issues/39482017-02-06T09:36:51ZAshlesh Gawande
<p>Do not forward LSA interests to routers not in the same network. Multiple networks should not interfere with each other.</p>
<p>Currently, if two routers are working on different network prefixes, e.g. <code>/ndn/</code> and <code>/ccn</code>, LSAs distributed will leak into the other network, and cause interruptions.</p>
<ul>
<li>(1) On a single computer, multiple NLSR processes could run simultaneously without interfering with each other.</li>
<li>(2) LSAs distributed for one network would not clutter other networks.</li>
</ul>
<p>This is a CI-NEW grant (NDN-CRI) goal for year two.</p>