Skip to main content

Include Legacy Internet Resource Holders in the Abuse-c Policy

This policy proposal has been withdrawn

You're looking at an older version: 1

The current (published) version is 2
Publication date
Draft document
Proposal Version
2.0 - 17 May 2016
All Versions
04 Jul 2016
State Discription
Working Group
Anti-Abuse Working Group
Proposal type
  • Modify
Policy term

Summary of Proposal

The proposal is about extending RIPE Document ripe-563, “Abuse Contact Management in the RIPE Database”,to Legacy Internet Resource Holders.

Policy Text

a. Current policy text

The proposed modification adds a new section to the current policy text.

b. New policy text

New section:

1.0 Scope

This policy applies to:


ripe-563 introduced the new contact attribute, “abuse-c:”. Although this attribute is mandatory for all aut-num objects and for at least every direct allocated inetnum and inet6num object, it cannot be enforced on Legacy Internet Resources. (See ripe-639, “RIPE NCC Services to Legacy Internet ResourceHolders”, section 1.2, paragraph 2.)

This difference in dealing with resources assigned or allocated by the RIPE NCC versus Legacy Internet Resources leads not only to an inconsistent data model used in the RIPE Database but also to poor data quality or lack of abuse contacts for some resources entered into the database.

It will be a benefit for the entire Internet community to have better quality of abuse contact data.

a. Arguments supporting the proposal

  • More consistent data model
  • Better data quality
  • More accurate data for abuse contact

b. Arguments opposing the proposal

  • Some work has to be done by Legacy Internet Resource Holders
  • Some abuse-c contacts have to be entered into the RIPE Database by the RIPE NCC (as done in the past).