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

Alexander, Daniel Daniel_Alexander at Cable.Comcast.com
Thu Mar 8 14:28:58 EST 2012


Owen and Chris G,

In previous threads you have suggested the inclusion of transfers in the
12 month restriction on the source organization of a transfer. This would
be in addition to any allocation or assignment from ARIN's free pool.

I have asked ARIN staff for feedback and they raised a point. Section 8.2
transfers are often used to bring records up to date prior to any 8.3
transfer. If we only say "transfers" without clarifying, it could create
an issue. Is your thought to include any and all transfers as triggering a
12 month black out from further sourcing transfers, or would you suggest
only 8.3 (and 8.4 as this proposal is written) transfers be included in
the restriction? 

Everyone else on the mailing list is encouraged to respond as well. I
would really like to continue the conversation regarding this point and
the proposal as a whole. I've included the current text as a reference.

Thank you,
Dan Alexander
AC Shepherd


Current 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 an allocation or assignment of
IPv4 number resources from ARIN for the 12 months prior to the approval of
a transfer request.
* 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 an
allocation or assignment of IPv4 number resources from ARIN for the 12
months prior to the approval of a transfer request.
* 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





More information about the ARIN-PPML mailing list