Changes to Include Legacy Internet Resource Holders in the Abuse-c Policy

Summary of Proposal

The This proposal is about extending RIPE Document ripe-563, “ ripe-563 delete: </a> , “Abuse Abuse Contact Management in the RIPE Database”, Database insert: </a> ” to Legacy Internet Resource Holders.

Policy Text

a. Current policy text

The proposed modification adds a new section to and does not modify the current policy text.

b. New policy text

New section:

1.0 Scope

This policy applies to:

• Internet resources Resources assigned and allocated by the RIPE NCC
• Legacy Internet Resources as (as defined in RIPE Document, “ RIPE NCC Services to Legacy Internet Resource Holders ” ”). In these cases, the policy is applied when creating or modifying Legacy Internet Resource objects in the RIPE Database.

Rationale

The policy ripe-563 (“ ripe-563 Abuse Contact Management in the RIPE Database ”) introduced the new contact attribute, “abuse-c:”. attribute “abuse-c”. Although this attribute is mandatory for all delete: <b> aut-num delete: </b> objects and for at least every direct allocated delete: <b> directly-allocated inetnum delete: </b> and delete: <b> and inet6num delete: </b> object, objects, it cannot be enforced on Legacy Internet Resources. (See delete: <a class="external-link" href="https://www.ripe.net/publications/docs/ripe-639#1-2-scope" target="_self" title=""> ripe-639 delete: </a> , for Legacy Internet Resources (see ripe-639, “ delete: <span class="external-link"> insert: <a class="internal-link" href="resolveuid/3bc32d39af6d485c89f3f845b703db80#1-2-scope" target="_self" title="" data-val="3bc32d39af6d485c89f3f845b703db80#1-2-scope" data-linktype="internal"> RIPE NCC Services to Legacy Internet Resource delete: <b> delete: </b> Holders delete: </span> insert: </a> ”, section 1.2, paragraph 2.) 2).

This difference in dealing with resources assigned or allocated by the RIPE NCC versus compared to Legacy Internet Resources leads not only to an inconsistent data model used in the RIPE Database but also to poor data quality or and a lack of abuse contacts for some resources entered into in 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 delete: </h4> delete: <ul> insert: </h3>

1. More consistent data model delete: </li> delete: <li> Better data quality (at the end of the process). insert: </li>
insert: <li>
2. Simpler abuse contact finding tools.
3. More accurate data for abuse contact delete: </li> delete: </ul> contacts. If the Legacy Resource Holders will receive an error due to the improper creating or updating of Legacy Internet Resource objects, they will receive a dedicated friendly explanation about abuse-c instead of a generic error message. insert: </li>
insert: </ol>

b. Arguments opposing the proposal

1. Some knowledge has to be gained and work has to be done by Legacy Internet Resource Holders delete: </li> delete: <li> Some abuse-c contacts have to Resource Holders. insert: </li>
insert: <li>
2. The proposal has a long term effect, since some Legacy Internet Resource objects are stale and will not probably be entered into the RIPE Database by the RIPE NCC (as done in the past). delete: </li> delete: </ul> changed in the near and predictable future. insert: </li>
insert: </ol>

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:

  insert: </p>

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. insert: <br />
insert: <br />

2.0 insert: <a name="abuse-contact-information"> insert: </a> 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 all aut-num s.

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. delete: </p> delete: <p class=" ">   insert: <br />
insert: <br />

3.0 insert: <a name="attribution"> insert: </a> 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: delete: </p> delete: <p> insert: <br />
Tobias Knecht delete: </p> delete: <p>   delete: </p> insert: <br />
insert: <br />
insert: </p>