Task #3937
open
NLSR should react to Face event notifications
Added by Nicholas Gordon almost 8 years ago.
Updated almost 4 years ago.
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.
Related issues
2 (2 open — 0 closed)
- Status changed from New to In Progress
- Assignee set to Nicholas Gordon
- Due date set to 06/16/2017
- Start date set to 05/23/2017
- Status changed from In Progress to Code review
- Status changed from Code review to In Progress
- Status changed from In Progress to New
- Due date deleted (
06/16/2017)
- Target version changed from v0.4.0 to v0.5.0
- Assignee changed from Nicholas Gordon to Saurab Dulal
- Blocked by Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interface added
- Related to Task #4338: Use persistent face instead of permanent face for NLSR in Mini-NDN added
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.
- Target version changed from v0.5.0 to v0.6.0
- Target version changed from v0.6.0 to 0.7.0
Also available in: Atom
PDF