Actions
Task #2936
open
Determine how to make NFD FIB Entries consistent with ranking in NLSR when costs are the same
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
06/23/2015
Due date:
% Done:
0%
Estimated time:
Description
Currently, the order of next hops with the same cost installed in NFD's FIB depend on the order that adjacencies are detected by NLSR. NLSR's routing table sorts ties using lexicographical ordering based on the next hop's FaceUri.
NLSR receives router B's adjacency LSA and determines it can reach router C through router B with cost 2
NLSR registers (Name: router C's prefix, next hop: router B, cost: 2)
NLSR receives router A's adjacency LSA and determines it can reach router C through router A with cost 2
NLSR registers (Name: router C's prefix, next hop: router A, cost: 2)
NLSR's ordering
(..., next hop: router A, ...), (..., next hop: router B, ...)
NFD's ordering
(..., next hop: router B, ...), (..., next hop: router A, ...)
This task should determine a way to keep these two view consistent with one another.
Updated by Nicholas Gordon over 7 years ago
As I understand it, the only way NextHops are sorted in NFD is by cost. There are then three courses of action:
- Open an issue to also sort ties in NFD using lexicographic sorting
- Consider that this is not a property we need to maintain, and close this as not-an-issue.
- Remove lexicographic sorting of ties from NLSR, and sort as-they-come like NFD.
Actions