This document relates to the policy proposal 2019-04, “Validation of "abuse-mailbox"”. If approved, it will modify ripe-705, “Abuse Contact Management in the RIPE Database”.
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.
| 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. |
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.
1.0 Abuse Contact Information
2.0 Attribution
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. |
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 must receive messages, either for automatic (e.g. X-ARF/RFC5965/RFC6650) or manual reports about abusive behaviour originating in the resource holders’ networks and must not force the sender to use a form. |
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. |
The RIPE NCC will validate if the “abuse-mailbox:” attribute is present and can receive messages at least every six months*. If the validation fails, the RIPE NCC will follow up in compliance with relevant RIPE Policies and RIPE NCC procedures. This validation process will not check how the abuse cases are processed. The community should escalate/report back to the RIPE NCC, so anonymised statistics can be collected and periodically published. As per current practice, other "e-mail:" attributes can be included for any other purposes. *The RIPE NCC may change the validation period depending on the level of accuracy of the contacts. For example, switching from six-month to one-year period once contact accuracy has improved. |
This document is developed by the RIPE community.
The following people actively contributed by making proposals through the RIPE Policy Development Process:
Tobias Knecht