[arin-ppml] Draft Policy 2011-10: Remove Single Aggregate requirement from Specified Transfer

[ARIN]

Draft Policy ARIN-2011-10
Remove Single Aggregate requirement from Specified Transfer


On 18 August 2011 the ARIN Advisory Council (AC) selected "Remove Single 
Aggregate requirement from Specified Transfer" as a  draft policy for 
adoption discussion on the PPML and at the Public Policy Meeting in 
Philadelphia in October.

The draft was developed by the AC from policy proposal "ARIN-prop-144 
Remove Single Aggregate requirement from Specified Transfer." Per the 
Policy Development Process the AC submitted text to ARIN for a staff and 
legal assessment prior to its selection as a draft policy. Below the 
draft policy is the ARIN staff and legal assessment, followed by the 
text that was submitted by the AC.

Draft Policy ARIN-2011-10 is below and can be found at:
https://www.arin.net/policy/proposals/2011_10.html

You are encouraged to discuss Draft Policy 2011-10 on the PPML prior to
the October Public Policy Meeting. Both the discussion on the list and
at the meeting will be used by the ARIN Advisory Council to determine
the community consensus for adopting this as policy.

The ARIN Policy Development Process can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Member Services
American Registry for Internet Numbers (ARIN)


## * ##

Draft Policy ARIN-2011-10
Remove Single Aggregate requirement from Specified Transfer

Date: 24 August 2011

Policy statement:

Modify Section 8.3 as follows: Change "can demonstrate the need for such 
resources, as a single aggregate, in the exact amount which they can 
justify under current ARIN policies" to "can demonstrate the need for 
such resources in the amount which they can justify under current ARIN 
policies"

Rationale:

The "as a single aggregate" has been interpreted to apply only to 
"demonstrate the need" as opposed to the resources which may be received 
by ARIN staff. It is possible that the original intent was to require 
than each transfer be of a single aggregate.

HOWEVER, as multiple Section 8.3 transfers may be executed serially by a 
pair of entities which wish to use the specified transfer policy in 
order to transfer any number of blocks as long as there is needs 
justification for each, it simply saves the transferring entity, the 
recipient, AND ARIN paperwork to allow a transfer of multiple blocks to 
proceed as a single transfer.

Timetable for implementation: immediate


#####


ARIN STAFF ASSESSMENT

Proposal:  ARIN-prop-144 Remove Single Aggregate requirement from 
Specified Transfer
Date of Assessment: 18 August 2011

1.  Proposal Summary (Staff Understanding)

This proposed policy would remove the phrase, "as a single aggregate" 
from the existing NRPM 8.3 policy thus allowing the transfer of multiple 
prefixes during an 8.3 transfer.

2. Comments

A. ARIN Staff Comments

•	This would eliminate possible confusion and align the text with 
current implementation whereby transfers can involve multiple 
discontiguous IPv4 address ranges (in a single transaction with ARIN).

•	There are two or more proposals/draft policies that are trying to 
change 8.3. Need to make them work together. (see props 144,  151, 153).

B. ARIN General Counsel

Counsel affirmatively supports this suggested change. We do not see it 
as creating any additional legal liability. Given the myriad of factual 
situations that may arise, a single aggregate requirement could prove to 
be too rigid and could prohibit an overall good
policy result.


3. Resource Impact

This policy would have minimal resource impact from an implementation 
aspect.  It is estimated that implementation would occur within 3 months 
after ratification by the ARIN Board of Trustees. The following would be 
needed in order to implement:

•	Updated guidelines
•	Staff training

4. Proposal Text

ARIN-prop-144

Remove Single Aggregate requirement from Specified Transfer

Policy statement:

Modify Section 8.3 as follows: Change "can demonstrate the need for such 
resources, as a single aggregate, in the exact amount which they can 
justify under current ARIN policies" to "can demonstrate the need for 
such resources in the amount which they can justify under current ARIN 
policies"

Rationale:

The "as a single aggregate" has been interpreted to apply only to 
"demonstrate the need" as opposed to the resources which may be received 
by ARIN staff. It is possible that the original intent was to require 
than each transfer be of a single aggregate.
HOWEVER, as multiple Section 8.3 transfers may be executed serially by a 
pair of entities which wish to use the specified transfer policy in 
order to transfer any number of blocks as long as there is needs 
justification for each, it simply saves the transferring entity, the 
recipient, AND ARIN paperwork to allow a transfer of multiple blocks to 
proceed as a single transfer.

Timetable for implementation: immediate