Abuse Contact Management in the RIPE Database Author: RIPE Working Group: Anti-Abuse Working Group Document ID: ripe-705 Updates: ripe-563 Date: June 2018 ------------------------------------------ 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:”, that can be included ininetnum,inet6numandaut-numobjects. Content 1.0 Abuse Contact Information 2.0 Attribution 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:” attribute. The “abuse-c:” will be mandatory for allaut-nums. Due the hierarchical nature of IP address objects, at least every direct allocatedinetnumandinet6numneeds 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. The “abuse-mailbox:” attribute must be available in an unrestricted way via whois, APIs and future techniques. 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. 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: Tobias Knecht