> 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? -- Juliusz
