How to read this draft document:
This document relates to the policy proposal 2016-01, “Include Legacy Internet Resource Holders in the Abuse-c Policy”. If approved, it will modify ripe-563. To show you how the new document would be different to the old one, we have highlighted any new text or changes to the existing text.
We indicate changes to existing text in the document like this:
|
ORIGINAL TEXT |
NEW TEXT |
|---|---|
|
The text from the current policy document that will be replaced is displayed here. |
The proposed text change will be displayed here. |
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 in inetnum, inet6num and aut-num objects.
Content1.0 Abuse Contact Information |
Content1.0 Scope 1.0 Scope This policy applies to:
|
2.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 all aut-nums.
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.
The “abuse-mailbox:” attribute must be available in an unrestricted way via whois, APIs and future techniques.
As per current practice, other "e-mail:" attributes can be included for any other purposes.
3.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