[arin-ppml] REVISED: Draft Policy ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy

Chris Grundemann cgrundemann at gmail.com
Mon Nov 19 10:55:04 EST 2012

Hail PPML,

Following discussion at the 30th ARIN PPM, ARIN-2012-8 has been
revised. A change-log has been added to the rationale. Please send
feedback at your earliest convenience.

Draft Policy ARIN-2012-8 Aligning 8.2 and 8.3 Transfer Policy

Date: 19 November 2012

Policy statement:

Replace the first paragraph of section 8.2 with the following (second
paragraph remains unchanged):

ARIN will consider requests for the transfer of number resources in
the case of mergers and acquisitions under the following conditions:

 * The new entity must provide evidence that they have acquired assets
that used the resources transferred from the current registrant. ARIN
will maintain an up-to-date list of acceptable types of documentation.
 * The current registrant must not be involved in any dispute as to
the status of the transferred resources.
 * The new entity must sign an RSA covering all transferred resources.
 * The transferred resources will be subject to current ARIN policies.
 * The minimum IPv4 transfer size is a /24, or the original assignment
size, whichever is smaller.
 * The minimum IPv6 transfer size is a /48.


The base intent here is to lower confusion, raise clarity, and level
the bar between 8.2 and 8.3 transfers. M&A transfers are distinct from
specified transfers and not all of the same rules can apply - but many
can and should. Therefor this policy change explicitly adds
requirements which do not exist in 8.2 policy text today: Source must
be the undisputed current registered holder, recipient must sign an
RSA (and is subject to policy), and /24 minimum for IPv4, /48 for

Changes following discussion at the ARIN XXX public policy meeting:
1) Changed the first bullet. This was an area for objections because
it did not allow chain of custody transfers, so now instead of saying
that the purchased company must be the current registrant holder it
simply says that there can not be any dispute as to who the registered
holder is.
2) Removed the " such that their continued need is justified" text
from the second bullet, this was another area of debate at the meeting
and justification is already covered in paragraph 2 of 8.2 (which
remains unchanged).
3) Swapped the first two bullets.
4) Added "covering all transferred resources" to the RSA bullet, for clarity.
5) Swapped the third and fourth bullets.
6) Altered the IPv4 minimum allocation to bring it in line with 4.10
resources and any future exceptions.

Timetable for implementation: immediate



More information about the ARIN-PPML mailing list