Actions
Task #3937
openNLSR should react to Face event notifications
Start date:
05/23/2017
Due date:
% Done:
0%
Estimated time:
Description
Currently, NLSR only reacts to when a Face is destroyed. Since HelloProtocol effectively diagnoses it, NLSR does not waste too much time if a Face goes down. However, when a Face comes back up, NLSR does not react to it in any way. This means there is a long period, before the next HelloInterval, where NLSR is possibly ignoring a neighbor. Fixing this would improve performance. NLSR should react accordingly based on whether the Face is permanent or ephemeral.
Updated by Nicholas Gordon over 7 years ago
- Status changed from New to In Progress
- Assignee set to Nicholas Gordon
Updated by Nicholas Gordon over 7 years ago
- Due date set to 06/16/2017
- Start date set to 05/23/2017
Updated by Nicholas Gordon over 7 years ago
- Status changed from In Progress to Code review
Updated by Nicholas Gordon over 7 years ago
- Status changed from Code review to In Progress
Updated by Nicholas Gordon about 7 years ago
- Status changed from In Progress to New
Updated by Nicholas Gordon almost 7 years ago
- Due date deleted (
06/16/2017) - Target version changed from v0.4.0 to v0.5.0
Updated by Nicholas Gordon over 6 years ago
- Assignee changed from Nicholas Gordon to Saurab Dulal
Updated by Ashlesh Gawande over 6 years ago
- Blocked by Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interface added
Updated by Ashlesh Gawande over 6 years ago
- Related to Task #4338: Use persistent face instead of permanent face for NLSR in Mini-NDN added
Updated by Nicholas Gordon over 6 years ago
Correction: NLSR also responds when a Face is created by checking through its list of neighbors to see if that Face URI corresponds to any neighbors there.
Updated by Saurab Dulal over 5 years ago
- Target version changed from v0.5.0 to v0.6.0
Updated by Saurab Dulal almost 4 years ago
- Target version changed from v0.6.0 to 0.7.0
Actions