[db-wg] RIPE abuse finder

Dear colleagues

If I can refer to the time line for the introduction of the "abuse-c:" 
attribute:
https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06
the RIPE NCC will make an announcement very soon on this.

Once deployed, this will be the one and only accepted method of 
documenting abuse contact details in the RIPE Database. It is very 
clear, very precise and very easy for software to find. As soon as this 
is deployed, we will adjust the Abuse Finder tool to work with this one 
and only method of finding abuse contact details.

This should address the issues discussed in this thread.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Group



On 19/03/2013 09:08, Peter Koch wrote:
> On Mon, Mar 18, 2013 at 11:25:08AM +0100, Gert Doering wrote:
>
>> But I do not accept implied responsibility by ill-designed tools trawling
>> along all possible cross-connects in the database to be able to return
>> "something", instead of having to answer "we're sorry we could not find
>> an abuse contact".
>
> I agree with Gert. The tool's logic is flawed and actually detrimental
> to the data quality of the RIPE DB since it provides an incentive to
> create duplicate person entries.  A "maintainer" is responsible for
> the database object, not for the entity (or person) referenced by it.
>
> -Peter
>
>