ARIN-PPML Message

[arin-ppml] ARIN-2012-1: Clarifying requirements for IPv4 transfers

Here is the final 2012-1 text for the meeting in Vancouver. I am working
on presentation slides so let me know if you have any feedback or thoughts
that should be clarified during the meeting discussion. This text includes
the word "transfers" in the 12 month restriction window placed on the
source. This change was the result of previous mailing list discussions
and feedback from Staff.

Thanks,
Dan


Final text: 2012-1: Clarifying requirements for IPv4 transfers

Replace Section 8.3 with

8.3 Transfers between Specified Recipients within the ARIN Region.

In addition to transfers under section 8.2, IPv4 numbers resources may be
transferred according to the following conditions.

Conditions on source of the transfer:

* The source entity must be the current registered holder of the IPv4
address resources, and not be involved in any dispute as to the status of
those resources.
* The source entity will be ineligible to receive any further IPv4 address
allocations or assignments from ARIN for a period of 12 months after a
transfer approval, or until the exhaustion of ARIN's IPv4 space, whichever
occurs first.
* The source entity must not have received a transfer, allocation, or
assignment of IPv4 number resources from ARIN for the 12 months prior to
the approval of a transfer request. This restriction does not include M&A
transfers.
* The minimum transfer size is a /24

Conditions on recipient of the transfer:

* The recipient must demonstrate the need for up to a 24 month supply of
IP address resources under current ARIN policies and sign an RSA.
* The resources transferred will be subject to current ARIN policies.


Add Section 8.4 Inter-RIR Transfers to Specified Recipients

Inter-regional transfers may take place only via RIRs who agree to the
transfer and share reciprocal, compatible, needs-based policies.

Conditions on source of the transfer:

* The source entity must be the current rights holder of the IPv4 address
resources recognized by the RIR responsible for the resources, and not be
involved in any dispute as to the status of those resources.
* Source entities outside of the ARIN region must meet any requirements
defined by the RIR where the source entity holds the registration.
* Source entities within the ARIN region will not be eligible to receive
any further IPv4 address allocations or assignments from ARIN for a period
of 12 months after a transfer approval, or until the exhaustion of ARIN's
IPv4 space, whichever occurs first.
* Source entities within the ARIN region must not have received a
transfer, allocation, or assignment of IPv4 number resources from ARIN for
the 12 months prior to the approval of a transfer request. This
restriction does not include M&A transfers.
* The minimum transfer size is a /24.


Conditions on recipient of the transfer:

* The conditions on a recipient outside of the ARIN region will be defined
by the policies of the receiving RIR.
* Recipients within the ARIN region will be subject to current ARIN
policies and sign an RSA for the resources being received.
* Recipients within the ARIN region must demonstrate the need for up to a
24 month supply of IPv4 address space.
* The minimum transfer size is a /24


Rationale:

The original text of this proposal attempted to clarify the requirements
of an IPv4 address transfer while protecting any resources remaining in
the ARIN free pool. This revision is a result of feedback from the mailing
list, ARIN Staff, and discussions with the original author. The one key
point that has been removed from the original text is that a needs based
review remains in place.

The current text attempts to retain the original concepts of protecting an
ARIN free pool, and incorporating it with the point of bringing resources
under RSA. The resulting text attempts to put safeguards in place on the
practice of paid transfers by creating a black out period for transfers
and requests to the free pool. The text also tries to incorporate
discussions regarding inter-RIR transfers and come up with language that
includes the free pool protections for transfers in and out of the Region.

Timetable for implementation: immediate.