Reconsider keeping infinite metric routes #618
Description
This is done because we used to follow the babel protocol more closely, and there keeping a retracted route made sense as a marker for periodic updates. However since we are now diverging, this should be looked at agian. There are a few scenarios for a metric to become infinite:
- A route expires
- A route is retracted by a peer
- A route has a next hop to a certain peer, and the connection to said peer dies
In case the route expires, it can be fetched again (better would be to implement #617 ).
If a route is retracted by a peer, that basically means option 1 or 3 happened on that peer, and no other feasible route exists.
If the peer dies, the route will certainly never work again (reconnecting the peer creates a different in process peer instance)
It seems as though in all cases, there is no point to keeping the routes. By removing them straight away, we can let the subnets expire faster, leading to faster aqcuisition times.