Delete expired RIB entries
Write a callback that can delete the nexthops of the expired entries.
#9 Updated by Junxiao Shi over 5 years ago
A proposal about which component should generate FIB updates is sent to nfd-dev list.
I invite watchers of this Task to have a look.
#10 Updated by Syed Amin over 5 years ago
The proposed changes should be a separate task and should be targeted for the next version, otherwise it may delay the release of v0.2 further. By that time the relevant fib update task would have been completed as well. For now if we don't have any other issue besides moving rib-expiration logic to the Rib, then I think the code we have currently can be accepted?
#13 Updated by Alex Afanasyev over 5 years ago
While looking into http://gerrit.named-data.net/#/c/911/ I realized a big problem with this commit, unless I'm mistaken.
It will expire all manually created entries using nfdc within 1 hour, as it is for some reason "default" expiration period if not overridden with -e option. This applies to all manually created routes with nfdc.
The protocol itself is also a little ambiguous on the issue: http://redmine.named-data.net/projects/nfd/wiki/RibMgmt#Register-a-route
It only defines that expiration period should be "practically" infinity when FaceId is omitted, otherwise it is still 1 hour. What is "practically" and why it cannot be actually infinity (in a sense that we don't set up timers for such entry)?
Why 1 hour? If we submit this commit, how static routes can work? Why expiration lifetime for statically created routes is not defaulted to infinity?