Project

General

Profile

Feature #1697

Updated by Junxiao Shi over 10 years ago

Currently, FIB calculation uses "longest prefix match" to set cost for the Face in the FIB entry.    This is demonstrated in note 31 of if issue #1325, where the current implementation is depicted in a second example. 

 The "correct" behavior should be to determine the lowest cost for the Face among possible parent records.    This should result in FIB like 

 |    Name    | (Face, Cost) | 
 |--------|--------------| 
 | /        |    (1, 10)       | 
 | /a       |    (1, 10)       | 
 | /a/b     |    (2, 5), (1, 10) | 

 Given the routes:  

 - (/, face=1, Cost=10, `CHILD_INHERIT`=yes), 
 - (/a, face=1, Cost=20, `CHILD_INHERIT`=yes), and 
 - (/a/b, face=2, Cost=5, `CHILD_INHERIT`=no) 

Back