This policy proposal has been accepted and has been implemented
The new RIPE Document is: ripe-705
You're looking at an older version: 1
The current (published) version is 2In 2012, the RIPE community developed a policy (ripe-563) that introduced a mandatory "abuse-c:” contact attribute, which holds contact information intended for automatic and manual reports of abusive behaviour originating in resource holders’ networks. Since then, this “abuse-c:” information has become an essential part of the accountability of the RIPE community.
However, ripe-563 didn’t provide for the validation of “abuse-c:” contact information. This undermines the effectiveness of the policy, as “abuse-c:” information can often be of date or inaccurate (with no valid contact); the RIPE NCC receives several hundred reports of invalid contact information each year. Further problems with abuse contacts are discussed regularly on the Anti-Abuse WG mailing list.
This proposal aims to give the RIPE NCC a mandate to regularly validate “abuse-c:” information, and to follow up in cases where contact information is found to be invalid.
[The following text will update section 1.0 in the RIPE Policy Document “Abuse Contact Management in the RIPE Database” if the proposal reaches consensus.]
[…]
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 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 behaviour 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. If no valid reply is received by RIPE NCC within two weeks (including if the email bounces back), the “abuse-mailbox:” contact attribute will be marked as invalid.
In cases where the “abuse-mailbox:” contact attribute is invalid, the RIPE NCC will follow up with the resource holder and attempt to correct the issue.