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

Hi Gert

On 06/11/2015 10:00, Gert Doering wrote:
> Hi,
>
> On Fri, Nov 06, 2015 at 06:01:53AM +0530, Suresh Ramasubramanian wrote:
>> +1 here - though for step 3 it might be an idea to check just how many such objects are there and with what frequency they pop up.
>>
>> Some of these funny announcements can be short lived indeed - only lasting a few hours.
>
> Step 3 will only be relevant if another RIR withdraws address space
> (so a route: object that has been properly validated before now points
> to no-longer-valid address space), which I see as a somewhat infrequent
> event.
>
> Of course there is the issue of cleanup of "dangling" objects when the
> address space changes hands (properly documented, and all that) - but
> that's not much different from "people forget to remove stale route:
> objects after a transfer" in just a single registry.

We could add a STEP 5:
If a delete request is sent to the RIPE Database for a ROUTE object 
related to out of region address space without the proper authorisation, 
send a notification to the contacts for the authoritative address space 
holder. If an appropriate response is received back, delete the ROUTE 
object.

This would simulate the reclaim functionality for RIPE address space 
holders.

Another byproduct of implementing this is that we no longer need to hold 
copies of AUT-NUM objects in the RIPE Database. The out of region ASN 
auth requirement is satisfied by the appropriate response to the 
notification. So all 'foreign' AUT-NUM objects could be immediately 
deleted. (Or after allowing time for these ASN holders to make sure 
their routing policy is actually up to date in the authoritative AUT-NUM 
object.)

cheers
denis

>
> Gert Doering
>          -- NetMaster
>