Draft Policy ARIN-2014-11: Improved Registry Accuracy Proposal


Abandoned by the AC

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 4 March 2014

Origin - ARIN-prop-203

Draft Policy - 4 March 2014

Revised - 20 May 2014

Abandoned by the AC - 24 June 2014



Public Policy Mailing List

ARIN Public Policy Meeting:



ARIN Advisory Council:

AC Shepherds:
Kevin Blumberg, Bill Darte

ARIN Board of Trustees:



Draft Policy ARIN-2014-11
Improved Registry Accuracy Proposal

Date: 20 May 2014

Problem Statement

The importance of maintaining accurate records in the ARIN database is
recognized as one of the Registries main tasks. Currently, ARIN policy does
not clearly state the registry services to be provided to non-contracted legacy
resource holders and the policy for use of such services.

Policy Changes

Section 2, Adds to "Definitions"

Legacy Resource Holder

An entity who has been previously issued Number Resources prior to ARIN's inception on December 22, 1997 in its service area.

Legacy Resources

A Number Resource including Autonomous system numbers and IP address space issued to a Legacy Resource Holder.

Non Contracted Legacy Holder

A Legacy Resource Holder that has Legacy Resources not specifically covered under a Resource Agreement.

Section 13 Legacy Resources

ARIN has historically provided a number of services to Legacy Resource Holders under contract as well as Non Contracted
Legacy Resource Holders. ARIN as part of its stewardship role in Internet Number resources will provide the following services:

1. Legacy Resource Holders
a. Registry Update Services including:
i. Address
ii. Point of Contact(s)
iii. Reverse DNS delegation
iv. Reassignment through SWIP or RWhois
v. Resource Public Key Infrastructure (RPKI)
vi. Corporate Name Changes

2. Non Contracted Legacy Holders
a. Registry Update Services including:
i. Address
ii. Point of Contacts(s)
iii. Reverse DNS delegation


Older version

Date: 4 March 2014

Problem Statement

The importance of maintaining accurate records in the ARIN database is
recognized as the Registries principal task and is not being debated.
The Registry is unable to responsibly fulfill this task. Many resource
holders are not incented through mutual benefits to participate in the
registry, the process or the community and instead operate
successfully outside of its bounds further hampering the mission of


To create a sustainable RIPE 605-like environment in the ARIN region that
provides mutual benefits to legacy holders and ARIN and in support of
vastly improved and accurate registry service.

Policy Changes

Section 1, Adds to "Principles"


The principle of Accuracy guarantees stakeholders that all reasonable
and mutually beneficial steps will be take to insure that the Registry
is as accurate as possible.


The principle of Fairness guarantees stakeholders that they will be
treated fairly with respect to whatever class of resources they hold,
whether they are pre or post RIR assigned addresses.

Value Add

The principle of Value Add guarantees that the Registry, in its effort
to insure that all of the principles are applied equitably, will seek
to add value to all resource holders regardless of class by insuring
such thing as rapid update functionalities and reasonably easy
transfer administration.

Mutual Benefit

The principle of Mutual Benefit guarantees that ARIN will enter into
or dissolve contracts related to legacy resource holders in like
fashion of comparable Registries.

Section 2, Adds to "Definitions"

Legacy Internet Resource

Any Internet Resource obtained prior to or otherwise outside the
current system of hierarchical distribution (by allocation or
assignment) through the Regional Internet Registries.

Legacy Internet Resource Holder

The holder of a Legacy Internet Resource. Either by receiving these
resources directly or by receiving (part of) Legacy Internet Resources
from a Legacy Internet Resource Holder.

Registry Service Element

In practice, any Legacy Resource Holder actually avails of a subset of
the Registry Services mentioned above. Where it is necessary to
distinguish between the entire class of Registry Services and the
specific Registry Services actually provided in a particular case, the
latter are described as Registry Service Elements.