You are here: Home > Participate > Policy Development > Policy Proposals > Abuse Contact Management in the RIPE NCC Database

Changes to Abuse Contact Management in the RIPE NCC Database

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted

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 :

  insert: </p>

insert: <p>

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. This proposal is explicitly not about data accuracy. If the RIPE community wishes, the data accuracy issue will be tackled in a separate policy 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, addition, 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 delete: <b> irt delete: </b> delete: <b> delete: </b> object. And since the "abuse-mailbox:" attribute can be added to various role objects, issue for maintainers to determine the best place to publish abuse contact information (irt, "abuse-mailbox:", "remark-fields:", and in which object they should be published). As a consequence, it is an issue for all kinds of institutions to find the correct abuse contact. insert: </p>

insert: <p>

The proposal intends to improve the abuse reporting value of the RIPE database at a high level. It does not clear in which of these role objects it should be preferred. intend to specify the technical details of the implementation or the procedures for the transition from the current system of abuse contact to the prospect one. Such details will be presented in the Review Phase of the PDP after the initial community discussion.

 

Policy text :

New policy text insert: </p>

insert: <p>

 

[Following text will result in a new RIPE Policy Document “Abuse Contact Management in the RIPE NCC Database“] Database“ insert: <i> ] insert: </i> insert: <i> insert: </i> insert: </p>

insert: <p>

 

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.

This policy introduces a new contact attribute named "abuse-c:", that can be included in inetnum, inet6num and aut-num objects. insert: </p>

insert: <p>

 

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. Internet number resources need to have an "abuse-c:". insert: </p>

insert: <p>

The "abuse-c:" will be mandatory for all aut-nums. insert: </p>

insert: <p>

Due the hierarchical nature of IP address objects, at least every direct allocated inetnum and inet6num needs to have an "abuse-c:". Inherited objects might have their own "abuse-c:" attribute or they will be covered by the higher level objects.

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 in the resource holders’ networks.

Other The "abuse-mailbox:" attribute must be available in an unrestricted way via whois, APIs and future techniques. insert: </p>

insert: <p>

As per current practice, other "e-mail:" attributes can be included for private conversations between the resources holder, or the holders’ teams, and external persons or institutions. delete: </p> delete: <p> 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:”. delete: </p> delete: <p> During this transitions period maintainers will be requested to reorganize their abuse contact references. delete: </p> delete: <p> After the transition period there will be some automated clean up of users data to reorganize abuse contact references where possible. any other purposes. insert: </p>

insert: <p>

 

 

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, addition, it helps all kinds of institutions to find the correct abuse contact information more easily.

Unlike existing email contacts in RIPE database, the new "abuse-c:" will have the advantage of being available with no restrictions to bulk access, which facilitates automated abuse reporting processes. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

b. Arguments opposing the proposal

None. delete: </p> As this RIPE policy proposal does not describe in detail the process and procedure of the policy implementation, it will be necessary to clarify these details. insert: </p>

Get Involved

The Anti-Abuse Working Group is open to anyone with an interest in combating network abuse. Areas such as cybersquatting and hosting illegal content are beyond the scope of the WG. The WG advises relevant parties such as Internet service providers (ISPs), governments and law enforcement agencies on both technical and non-technical methods of tackling abuse. This mailing list was previously the “anti-spam-wg”, the archives of which are still publicly available on the RIPE NCC website. To post a message to the list, send an email to anti-abuse-wg@ripe.net. Please note that only subscribers can post messages.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.