Changes to Abuse Contact Management in the RIPE 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 Database, including potential areas for improvement and alternative approaches.

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

Content

delete: <b> insert: <strong> 1.0 Abuse Contact Information delete: </b> delete: <br /> delete: <b> insert: </strong> insert: <br />
insert: <strong> 2.0 Attribution delete: </b> insert: </strong>

1.0 Abuse Contact Information

The "abuse-c:" will reference a role object holding abuse contact information. The positioning of the “abuse-c:” “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:” “abuse-c:” attribute.

The “abuse-c:” “abuse-c:” will be mandatory for all delete: <b> all  insert: <strong> aut-num delete: </b> insert: </strong> s.

Due the hierarchical nature of IP address objects, at least every direct allocated delete: <b> allocated  insert: <strong> inetnum delete: </b> and delete: <b> insert: </strong>  and  insert: <strong> inet6num delete: </b> needs insert: </strong>  needs to have an “abuse-c:”. “abuse-c:”. Inherited objects might have their own “abuse-c:” “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:” “abuse-mailbox:” attribute which is intended for receiving automatic and manual reports about abusive behavior originating in the resource holders' networks.

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

The RIPE NCC will validate the “abuse-mailbox:” attribute at least annually. Where the attribute is deemed incorrect, it will follow up in compliance with relevant RIPE Policies and RIPE NCC procedures.

As per current practice, other "e-mail:" attributes can be included for any other purposes. purposes. 

2.0 Attribution

This document is developed by the RIPE community.

The following people actively contributed by making proposals through the RIPE Policy Development Process: insert: </p>

Tobias Knecht delete: <br /> delete: <br /> delete: </p> insert: </p>