[db-wg] [anti-abuse-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database

Hello Marco,

Yes, in the data entry side a little bit more effort is required, but as we have mentioned at (https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06), there are two main reasons for that:

a) This models the reality, in almost every case we know of, abuse handling is a role within an organisation. On he other hand attaching an email address to a resource is creating an arbitrary link.

b) Operationally it is a lot more feasible for our members and users to enter data and more importantly to maintain this data over time if it is centralised in an entity modelled after their real work setup. 

All that said, we have also considered facilitating data entry. As we have mentioned we will provide additional tooling for data entry, so users can add their data easily. 

In the case you have mentioned, we are planning to provide a web based data entry tool which asks users for some basic required information and automatically prepares and creates both "ROLE" and "ORG" objects and then updates the internet resource in question. We just need to ask the user for the name of the entity, address, abuse contact email address and a maintainer and with that we can create all required objects and update the resource in question. 

We will also provide this through our update API for users who prefer to automatically add abuse contact information for their own customers.

All the best,
Kaveh.

---
Kaveh Ranjbar,
RIPE NCC Database Group Manager

On Nov 16, 2012, at 5:03 PM, Marco d'Itri <md at Linux.IT> wrote:

> On Nov 15, Kaveh Ranjbar <kranjbar at ripe.net> wrote:
> 
>> The RIPE NCC's proposed implementation plan of RIPE policy 563 (policy proposal 2011-06) titled "Abuse Contact Management in the RIPE Database" is as follows:
> 
> Requiring that LIRs maintain a new and otherwise totally useless 
> organization object for every customer who need a delegated abuse-c 
> attribute is very inconvenient.
> At least unless that object can be simplified to contain only the 
> abuse-c attribute and no other data.
> ...



-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20121119/d08850be/attachment.html>