[lir-wg] AS Number Policy

Dear Berislav, Colleagues,

Berislav Todorovic wrote:

[...]


> Now, I know that unassigned AS numbers hanging around in the routing tables
> are nothing new. However, if they are properly registered within RIPE DB
> and noone notices the forgery - that's worrying:


[...]


> 
> Are we going to stick with the rule that RIPE NCC people cannot modify the
> RIPE DB and tolerate the offenders? Just wondering ...
>


I just wanted to note that though we have such general rule we also have 
exceptions. Especially when the data in the database conflicts with the 
information in the Registration Services. Of course our main concern is 
regarding the space distributed by the RIPE NCC.

Speaking of the quality of data in the RIPE Database in general, we are 
working towards making the database more restrictive to reject bogus 
records. We also run database consistency projects to help people to 
keep their records up to date.

Also, as you know, we perform massive clean-ups if the community have 
requested such actions. That, for instance, happened to unreferenced 
person objects; we plan a cleanup of non valid "auth:" fields in mntner 
objects. In my opinion such actions are more favourable as they get 
community consensus and require much less resources per inconsistency 
than a single clean-up.

We are also discussing some ideas of how to allow the holders of the 
address or ASN space to perform necessary clean-ups within their space 
without requesting the RIPE NCC to do this.


> Regards,
> Beri
> 

Regards,

Andrei Robachevsky
DB Group
RIPE NCC