[anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

On Thu, Nov 05, 2015 at 07:40:58PM +0000, ripedenis at yahoo.co.uk wrote:
>STEP 2
>
>For those ROUTE objects from STEP 1 where the out of region
>resource does exist, hold the object creation as pending. The
>mechanism for doing this already exists in the RIPE Database
>software as it is used for multiple authentications.
>
>Lookup the out of region resource(s) in the authoritative
>database(s) and find the contacts for that resource. Send a
>notification to those contacts informing them of the pending
>ROUTE object creation in the RIPE Database. The notification
>mechanism already exists in the RIPE Database software. If they
>don't approve, do nothing and the creation request will time out
>after a week and the object will not be created. If they do
>approve, respond in some way (many technical options for doing
>this that the RIPE NCC can choose from). If appropriate
>approval(s) are received within a week, create the ROUTE object.

The issue I see is that it is even harder to verify out-of-region
resource holders than RIPE NCC ones. (Please don't even mention
letterheaded faxes, this is 2015 not 1995).  If you can assume
that, just as in the RIPE region, the majority of those resource
holders are honest, this is workable.

Overall a good idea even if it goes against simplicity.

>STEP 3
>
>On a daily basis, for each ROUTE object in the RIPE Database
>that relates to an out of region resource, check for the
>continued existence of that resource in the appropriate RIR
>database. If it no longer exists, delete the ROUTE object from
>the RIPE Database.

rgds,
Sascha Luck