I guess all we can do is keep highlighting the problem (I highlight
Geoff's BGP Update report almost every BGP Best Practice training I run
here in AsiaPac, for example) - but how to make noisy peers go away,
longer term...? :-(
> * These problems aren’t DFZ wide. Peer A might be sending a bajillion updates to peer B, but peer B sees there is no change in the route and correctly doesn’t forward the update onwards to it’s peers / public collectors. So this is
probably happing a lot more than we see via RIS or RouteViews. Only some parts of the DFZ will be receiving the gratuitous updates/withdraws.