[arin-ppml] Draft Policy ARIN-2014-9: Resolve Conflict Between RSA and 8.2 Utilization Requirements

ARIN info at arin.net
Tue Mar 4 15:12:45 EST 2014

On 20 February 2014 the ARIN Advisory Council (AC) accepted
"ARIN-prop-199 Resolve Conflict Between RSA and 8.2 Utilization 
Requirements" as a Draft Policy.

Draft Policy ARIN-2014-9 is below and can be found at:

You are encouraged to discuss the merits and your concerns of Draft
Policy 2014-9 on the Public Policy Mailing List.

The AC will evaluate the discussion in order to assess the conformance
of this draft policy with ARIN's Principles of Internet Number Resource
Policy as stated in the PDP. Specifically, these principles are:

   * Enabling Fair and Impartial Number Resource Administration
   * Technically Sound
   * Supported by the Community

The ARIN Policy Development Process (PDP) can be found at:

Draft Policies and Proposals under discussion can be found at:


Communications and Member Services
American Registry for Internet Numbers (ARIN)

## * ##

Draft Policy ARIN-2014-9
Resolve Conflict Between RSA and 8.2 Utilization Requirements

Date: 4 March 2014

Problem Statement:

8.2 transfer policy has utilization requirements at the time of the 
review of the transfer request.

The RSA section 6 expressly forbids ARIN from de-registering blocks (in 
whole or in part) due to under-utilization or no-justification during 
transfer requests.

This is a direct conflict.

Return and aggregate are not done in collaboration; they are coerced by 
policy without the willing consent of the transfer parties.

We should remove all utilization references from 8.2 language to ensure 
the policy is compliant with the RSA.

Policy statement:

Remove from 8.2:
"In the event that number resources of the combined organizations are no 
longer justified under ARIN policy at the time ARIN becomes aware of the 
transaction, through a transfer request or otherwise, ARIN will work 
with the resource holder(s) to return, aggregate, transfer, or reclaim 
resources as needed to restore compliance via the processes outlined in 
current ARIN policy."

a.Timetable for implementation: Immediate
b.Anything else:

More information about the ARIN-PPML mailing list