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

On 06/11/2015 11:55, denis wrote:
> 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.

this could and probably should be made smarter.

I'd be generally happy with the idea of formally asking the RIPE NCC to
kindly deal with obviously abusive behaviour in a way that seems most
appropriate to them.  E.g. stuff like detection + rate limiting of object
creation, credibility scores for mntners, checks for out of hours creation
of route: objects, i.e. at 18:05 CET on friday evenings and so forth.

Richard Clayton provides some really good quality analysis of at least some
of the things going on here:

> https://www.lightbluetouchpaper.org/2015/10/02/badness-in-the-ripe-database/

> https://www.lightbluetouchpaper.org/2015/11/02/ongoing-badness-in-the-ripe-database/

Nick