I was opposing the first version of this proposal, where conflicting objects were silently and instantly removed. The new version seems to resolve these concerns - and 7-day notification should be fine.
But I'm not sure if all objects have optional 'notify' field (and a brief check showed that there are some without this field, I don't have exact numbers at the moment). If there is the technical opportunity I would suggest to also use notify field (and may be other contacts) from the related maintainer object. пт, 31 мая 2019 г. в 14:11, Tore Anderson <[email protected]>: > * Marco Schmidt > > > A new version of RIPE Policy proposal, 2018-06, "RIPE NCC IRR Database > Non-Authoritative Route Object Clean-up", is now available for discussion. > > > > The goal of the proposal is to delete an non-authoritative object stored > in the RIPE IRR, if it conflicts with an RPKI ROA. > > Eminently sensible. Supported. > > Tore > > -- Best regards, Alexander Azimov
