Juliusz Chroboczek <jch@irif.fr> writes:
This has been clarified in RFC8966 as: "Note that the feasibility distance is not updated and the garbage-collection timer is not reset when a retraction (an update with infinite metric) is sent."
The feasibility distance is only updated if the metric is lower, which is never true for an (infinite-metric) retraction, so that's kinda implicit anyway.
We do actually update the garbage collection time regardless of the route metric in the regular update function (but not when sending an explicit retraction). I think that's OK, though?
Does that mean that a retracted route never expires?
Hmm, no, this is the garbage collection timer in the source table only. There are separate expiry timers on the route objects themselves, so all this means is that the source table entry will stick around slightly longer, and it may delay the garbage collection of a retracted route internally in Bird slightly... -Toke