>> but does not explain the cases where we see stuck routes on devices >> which have no config changes for a loooong time (if you believe >> rancid). > > Well, in the scenario above, R1 would have the config change, but *on > R1* the route would be gone. A downstream router R2 would have seen > the initial UPDATE, but never received a withdraw - so R2 would claim > "I have it, and I have it from R1!" while R1 would claim "no such > prefix".
so, could we look for a router where emile et alia found a stuck route and we have the rancid for the upstreams? randy
