Marco Schmidt via db-wg wrote on 11/10/2018 14:18:
We just published the RIPE Policy proposal, 2018-06, "RIPE NCC IRR
Database Non-Authoritative Route Object Clean-up", to the Routing
Working Group mailing list.
The goal of the proposal is to delete an non-authoritative object
stored in the RIPE IRR, if it conflicts with an RPKI ROA.
There are some corner cases where this could cause permanent and
unwarranted pain.
1. what's the procedure for backing out the deletion if the ROA holder
in the other RIR makes a mistake and, for example, forgets to create a
roa for a specific ASN and then they find their RIPE-NONAUTH route
object deleted by accident.
2. what happens when someone is busy creating ROAs in, for example,
Magastan and the RIPE NCC runs a deletion process mid-way through that
process
3. the above situations are complicated by RFC6382.
It might be a good idea to send some warnings to the holders of the
route/route6 objects before nuking their objects + build in a timeout
period.
Nick
