Abuse contact information

This is a proposal to introduce a mandatory reference to irt objects in the inetnum, inet6num and aut-num objects in the RIPE Database. It provides a more accurate and efficient way for abuse reports to reach the correct network contact and helps reporting institutions to find the correct abuse contact information more easily.

Summary of Proposal:

This is a proposal to introduce a mandatory reference to irt objects in the inetnum, inet6num and aut-num objects in the RIPE Database. It provides a more accurate and efficient way for abuse reports to reach the correct network contact and helps reporting institutions to find the correct abuse contact information more easily.

Summary of current problem

Network owners increasingly operate dedicated abuse handling departments, distinct from the basic operations department.

More and more network owners and other institutions are also starting to exchange data about abusive behavior with each other, to more quickly allow networks to identify internal abuse, external abuse, and other security problems.

Currently within the RIPE region, the biggest problem for network operators is to know the best place to publish abuse contact information (irt, "abuse-mailbox:", "remark-fields:", and in addition to that, in which object they should publish them?). On the other hand abuse reporting parties having a huge problem with finding a correct abuse contact in the variety of possibilities.

Since there is a specialised object (irt) for abuse contacts, this should be mandatory, to stop the uncontrolled growth.

Situation in other RIRs

AfriNIC:

AfriNIC is also discussing a similar policy proposal. [1]

APNIC

This policy was acknowledged by the APNIC members in Kuala Lumpur in March 2010.[2]

Implementation will be finished in November 2010.

ARIN:

An abuse-POC exists for Organisational ID identifiers.[3]

LACNIC:

An "abuse-c:" exists for aut-num, inetnum and inet6num objects.[4]

Policy Text:

New Policy

[Following text will result in a new RIPE Policy Document “Abuse Contact Information”, if the proposal reaches consensus]

1. Compulsory IRT Object

In the RIPE Database, a reference to an irt object is mandatory for the following database objects: inetnum, inet6num, aut-num

The irt reference must be set every time these type of objects are added into the database and must be updated when the objects are updated.

In the irt object it is mandatory to fill the "abuse-mailbox:" field.

The creation of new "abuse-mailbox:" fields for all objects without the irt object will not be allowed.

All the "abuse-mailbox:" attributes in objects other than irt objects will be deleted by end of 2012.

Rationale:

a. Arguments supporting the proposal

• This proposal should stop the irritation about the right way to publish abuse contact information in the RIPE Database.
• This proposal will solve the problem about finding the right abuse contact information.
• Every single IP address in the RIPE region has its abuse contact address and abuse issues will not be sent to other contacts anymore.
• The problem with query restrictions will be solved, because irt objects can be queried without restriction.
• The proposal has the advantage to use already existing objects and mechanisms.
• This permits greater administrative and operational flexibility, and faster abuse handling will be possible.
• APNIC and RIPE have the same abuse contact policy in place. Keeps things easier.
• Projects like RIPE Abuse Finder will be more easy to implement and could work more efficiently.

b. Argument opposing the proposal

• RIPE NCC members need to set up irt objects with the next update of their inetnum, inet6num and aut-num.

References:

[1] Abuse Contact Information in the AfriNIC service region (Proposal-Draft) http://www.afrinic.net/docs/policies/AFPUB-2010-GEN-002.htm

[2] prop-079: Abuse contact information http://www.apnic.net/policy/proposals/prop-079

[3] Introduction to ARIN's Database https://www.arin.net/knowledge/database.html#abusepoc

[4] There is no formal documentation on "abuse-c:" in inetnum and inet6num objects, but for documentation on the "abuse-c" in ASN records, see LACNIC Policy Manual (v1.3 - 07/11/2009) http://lacnic.net/en/politicas/manual4.html