[db-wg] restrict usage of RIPE-NCC-RPSL-MNT

On Fri, Nov 14, 2014 at 12:33:05PM +0100, Job Snijders wrote:

Dear Job and All

> I did some digging to understand how the RIPE-NCC-RPSL-MNT mntner object
> is used in practise. You can fetch the dataset through this command:
>     
>     $ whois -h whois.ripe.net -- '-K -i mnt-by RIPE-NCC-RPSL-MNT'
> 
> Usage exceeded my expectations:
> 
>     (object type: occurances)
> 
>     route: 12195

I have noticed also that TOP10 ASes cover 80% of those routes. Moreover,
most of them are longer prefixes from the same bigger network (like /16
divided to 256 /24 with the same data in the route object).

>     route6: 77
> 
> And much to my suprise I found that there are all kinds of objects which
> reference RIPE-NCC-RPSL-MNT with an "mnt-by:" attribute:
> 
>     aut-num: 341
>     mntner: 51
>     as-set: 37
>     person: 40
>     route-set: 33
>     organisation: 5
>     rtr-set: 1
>     inet-rtr: 1
>     key-cert: 1
> 
> Would it be an idea to prevent objects from being updated/created when
> they carry a "mnt-by: RIPE-NCC-RPSL-MNT" attribute? 

What about delete?

> Secondly, should RIPE NCC proactively remove all "mnt-by:
> RIPE-NCC-RPSL-MNT" references from the database? 

+1

Piotr

-- 
gucio -> Piotr Strzyżewski
E-mail: Piotr.Strzyzewski at polsl.pl