Actions
Task #3591
closed
Design NLSR and RIB Manager propagation advertisement protocol
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
04/07/2016
Due date:
% Done:
0%
Estimated time:
Description
When a laptop propagates a prefix to a gateway router, the prefix is registered with the remote NFD's RIB manager, but the prefix is not further advertised to the network.
This task should define in detail the interaction between the RIB Manager and NLSR where:
- The RIB Manager receives a propagation request
- The RIB Manager sends a prefix advertisement command to NLSR
- NLSR determines if the prefix should be advertised based on some advertisement policy
- NLSR responds to the RIB Manager with the outcome of the request
Updated by Junxiao Shi about 8 years ago
This feature is basically reboardcasting a static route as a dynamic route.
I disagree with the initial proposed procedure:
- The RIB Manager receives a propagation request
- The RIB Manager sends a prefix advertisement command to NLSR
- NLSR determines if the prefix should be advertised based on some advertisement policy
- NLSR responds to the RIB Manager with the outcome of the request
This procedure would couple NFD-RIB and NLSR, and also prevent multiple routing protocols from working together.
My proposal is:
- NFD-RIB should offer a notification stream of prefix propagation and revocation events.
- A separate program, independent from NFD-RIB and NLSR, subscribe to the notifications.
- Based on configured policy, the program decides whether to reboardcast the static route, and which routing protocols to reboardcast the route into.
- The program invokes the advertise/withdraw command of each routing protocol, including but not limited to NLSR Management.
Updated by Ashlesh Gawande about 7 years ago
- Status changed from New to Closed
Actions