You're looking at an older or unpublished version: 1

Abuse Contact Management in the RIPE NCC Database

This is a proposal to introduce a new contact attribute named "abuse-c:", which can be included in inetnum, inet6num and aut-num objects.

Summary of proposal:

This is a proposal to introduce a new contact attribute named "abuse-c:", which can be included in inetnum, inet6num and aut-num objects.

The syntax will make this an optional attribute, but business rules will require it to be included in allocations managed by the RIPE NCC Registration Services, PI assignments and AS number registrations.

It provides a more efficient way for maintainers to organize their provided information and helps to increase accuracy and efficiency in routing abuse reports to the correct network contact. In addition to that, it helps all kinds of institutions to find the correct abuse contact information more easily.

Currently within the RIPE NCC service region, it is not clear whether to use the "abuse-mailbox:" attribute, the "remark:" attribute or an irt object. And since the "abuse-mailbox:" attribute can be added to various role objects, it is not clear in which of these role objects it should be preferred.

 

Policy text:

New policy text

[Following text will result in a new RIPE Policy Document “Abuse Contact Management in the RIPE NCC Database“]

Abstract

This policy originated from the work of the Abuse Contact Management Task Force. The task force examined the collection and maintenance of resource registration information in the RIPE NCC Registry Database, including potential areas for improvement and alternative approaches.

 

1.0 Abuse Contact Information

The "abuse-c:" will reference a role object holding abuse contact information. The positioning of the "abuse-c:" attributes will make use of the hierarchical nature of the resource data to minimize the workload on resource holders.

The role objects used for abuse contact information will be required to contain a single "abuse-mailbox:" attribute which is intended for receiving automatic and manual reports about abusive behavior originating the resource holders’ networks.

Other "e-mail:" attributes can be included for private conversations between the resources holder, or the holders’ teams, and external persons or institutions.

The current query option "-b" will be extended to search for the “abuse-c:” attribute in addition to all existing locations. If the "abuse-c:" is found only this data will be returned. After a transition period the “-b” option will only search for “abuse-c:”.

During this transitions period maintainers will be requested to reorganize their abuse contact references.

After the transition period there will be some automated clean up of users data to reorganize abuse contact references where possible.

 

2.0 Attribution

This document is compiled from policies developed by the RIPE community.

The following people actively contributed by making proposals through the RIPE Policy Development Process:

Tobias Knecht

 

Rationale

a. Arguments supporting the proposal

It provides a more efficient way for maintainers to organize their provided information and helps to increase accuracy and efficiency in routing abuse reports to the correct network contact. In addition to that, it helps all kinds of institutions to find the correct abuse contact information more easily.

b. Arguments opposing the proposal

None.