Job Snijders wrote on 14/10/2018 07:48:
When an operator makes a mistake, they've made a mistake.
When someone needs to create multiple ROAs, but only publishes one - it
is an operator error. When one misconfigures things... they are
misconfigured, no big deal.
operator error happens all the time. In most cases, it's reversible and
life goes on.
As it stands, the proposal allows some types of operator error to cause
irreversible changes to their exterior routing policy, with no
notification or grace period. It may be that those changes are for the
better, but there will also be cases where it's for the worse. The
RIPE-NONAUTH data set contains garbage, but it also contains plenty of
accurate objects.
If this proposal does not provide a mechanism to notify holders of
conflicting route/route6 objects and provide a reasonable grace period
for sorting conflicts, then the proposal is harmful and should not proceed.
Nick
