Policy 2007-8: Transfer Policy Clarifications

Status: Adopted - NRPM Section 8

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 2 March 2007

Staff assessment - 13 April 2007
Last call - 25 April through 9 May 2007 Public Policy Mailing List

ARIN Public Policy Meeting:


ARIN Advisory Council:

1 March 2007
24 April 2007
17 May 2007

ARIN Board of Trustees:

Adopted on 14 June 2007



22 August 2007


Paul Andersen

Proposal type: Modify

Policy term: Permanent

Policy statement:

That Section 8 of the NRPM is replaced as follows:

8. Transfers

8.1. Transfers

Number resources are non-transferable and are not assignable to any other organization unless ARIN has expressly and in writing approved a request for transfer. ARIN is tasked with making prudent decisions on whether to approve the transfer of number resources.

It should be understood that number resources are not "sold" under ARIN administration. Rather, number resources are assigned to an organization for its exclusive use for the purpose stated in the request, provided the terms of the Registration Services Agreement continue to be met and the stated purpose for the number resources remains the same. Number resources are administered and assigned according to ARIN's published policies.

Number resources are issued, based on justified need, to organizations, not to individuals representing those organizations. Thus, if a company goes out of business, regardless of the reason, the point of contact (POC) listed for the number resource does not have the authority to sell, transfer, assign, or give the number resource to any other person or organization. The POC must notify ARIN if a business fails so the assigned number resources can be returned to the available pool of number resources if a transfer is not requested and justified.

8.2. Transfer Requirements

ARIN will consider requests for the transfer of number resources only upon receipt of evidence that the new entity has acquired the assets which had, as of the date of the acquisition or proposed reorganization, justified the current entity's use of the number resource. Examples of assets that justify use of the number resource include, but are not limited to:

  • Existing customer base
  • Qualified hardware inventory
  • Specific software requirements.

8.3. Documentation Requirements

In evaluating a request for transfer, ARIN may require the requesting organization to provide any of the following documents, as applicable, plus any other documents deemed appropriate:

  • An authenticated copy of the instrument(s) effecting the transfer of assets, e.g., bill of sale, certificate of merger, contract, deed, or court decree
  • A detailed inventory of all assets utilized by the requesting party in maintaining and using the number resource
  • A list of the requesting party's customers using the number resources

If further justification is required, the requesting party may be asked to provide any of the following, or other supporting documentation, as applicable:

  • A general listing of the assets or components acquired
  • A specific description of acquisitions, including:
    • Type and quantity of equipment
    • Customer base
  • A description of how number resources are being utilized
  • Network engineering plans, including:
    • Host counts
    • Subnet masking
    • Network diagrams
    • Reassignments to customers


Staff analysis and community comments have a problem with the inconsistent use of the terms "ASN" and "IP Address" in this section which leads to confusion on which resources can be transferred. The entire section now utilizes the term "number resources" to clarify what would appear to be the original intent.

A section regarding the handling of customer networks outside ARIN's geographic region has been removed to reflect the actual current procedure utilized that was developed in conjunction with the ERX transfer project.

The last section of old text has been removed as it does not appear to be so much policy as guidance.

Timetable for implementation: Immediate