Draft Policy ARIN-2011-1: ARIN Inter-RIR Transfers

Status: NRPM 8.3

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 3 February 2011

Origin - ARIN-prop-119

Draft Policy - 3 February 2011 (with staff assessment)

AC postponed decsision to May - 18 April 2011

Remains on AC's docket - 24 May 2011

Revised - 22 September 2011 (with staff assessment)

Last Call - 19 October through 16 November 2011

Revised assessment - 9 November 2011

AC recommended adoption - 22 November 2011

Board takes under advisement pending discussion at ARIN XXIX - 10 January 2012

Adopted - Implementation no later than 31 July 2012

Implemented - 31 July 2012


Public Policy Mailing List

ARIN Public Policy Meeting:



ARIN Advisory Council:

AC Shepherds:
Bill Darte and Robert Seastrom


ARIN Board of Trustees:

16 December 2011
6 June 2012


Previous version(s)


31 July 2012

Draft Policy ARIN-2011-1
ARIN Inter-RIR Transfers

Date: 14 October 2011

Policy statement:

8.3 Transfers to Specified Recipients

In addition to transfers under section 8.2, IPv4 number resources may be
released to ARIN by the authorized resource holder or another RIR, in
whole or in part, for transfer to another specified organizational
recipient. Organizations in the ARIN region may receive transferred
number resources under RSA if they can demonstrate the need for such
resources in the amount which they can justify under current ARIN policies.

IPv4 address resources may be transferred to organizations in another
RIR's service region if they demonstrate need to their region's RIR,
according to that RIR's policies. Inter-regional transfers may take
place only via RIRs who agree to the transfer and share compatible,
needs-based policies. Such resources must be transferred in blocks of
/24 or larger and will become part of the resource holdings of the
recipient RIR.

Timetable for implementation: Upon ratification by the ARIN Board of Trustees

Note from the AC:

The Advisory Council reviewed the results of feedback from the ARIN
XXVIII Public Policy Meeting concerning Draft Policy 2011-1 Inter-RIR
Transfers. While there were concerns regarding the presented wording,
there was significant continued support for a policy enabling
Inter-Regional transfers of IPv4 number resources from organizations able
to make them available to any organization with valid requirements.

In addition to cumbersome wording, the presented text could not be
cleanly inserted into the NRPM. The following is new language that
directly modifies section 8.3 "Transfers to Specified Recipients" to
allow such transfers to or from organizations in other regions.

The first paragraph is a modified version of the current 8.3 policy
language, envisioning resources being released to ARIN by the authorized
resources holder or additionally by another RIR to be transferred to a
specified recipient. The second sentence was reorganized to emphasize
that it applies to an organization within the ARIN region that will
receive such a specified transfer, and to eliminate the single aggregate
language per 2011-10 which is also being sent to last call.

The new second paragraph adds language enabling transfers to a specified
recipient in another RIR's service region. This language specifies that
such recipients justify their need to their RIR, following that RIR's
policies. ARIN will verify that there is a compatible needs based
policy that the other RIR will use to evaluate the need of the recipient
and that both RIR's agree to the transfer. Implicit in the intent of
the language presented and in conformance with statements made, the size
of the block to be transferred is identified as /24 or larger, for
obvious practical reasons.

In accordance with concern for immediate adoption, the AC chose to
forward this version to last call. Concerns expressed by some
stakeholders for further controls were noted by the AC, and are being
considered for future policy modification, assuaged in part by ARIN
staff assurances that if any significant abuse of this policy were to
occur, then the policy could easily be suspended.