Personally I recommend dropping them invalids. However, you could set local preferences as follows: - Valids routes get the highest local pref - unknown routes get a medium local pref - Invalids routes get the lowest local pref In this way, if you have competing routes, the one with the higher local pref gets preferred. By so doing, you are sure that an invalid route will never get preferred over an unknown one or a valid one. But, honestly there is no point in ROV if you will allow invalids…
On 29 Oct 2021, at 00:20, Lukas Tribus <lukas@ltri.eu> wrote:
Hello,
On Thu, 28 Oct 2021 at 21:35, <ssw@iu.edu> wrote: Given that some routes may have mistaken ROAs that resolve to an invalid state, is there a standard/best practice for processing exceptions?
There is no point in ROV, unless you are dropping invalid routes.
Not dropping invalid routes is something you'd do during transitional phases, when you are not yet sure about the impact. But if you keep it that way, you may as well not deploy it in the first place.
Refer to the BGP Filterguide at NLNOG for some low level details: https://bgpfilterguide.nlnog.net/guides/reject_invalids/
Lukas