[arin-ppml] ARIN-prop-144 Remove Single Aggregate requirement from Specified Transfer

[ARIN]

ARIN-prop-144 Remove Single Aggregate requirement from Specified Transfer

ARIN received the following policy proposal and is posting it to the
Public Policy Mailing List (PPML) in accordance with the Policy
Development Process.

The ARIN Advisory Council (AC) will review the proposal at their next
regularly scheduled meeting (if the period before the next regularly
scheduled meeting is less than 10 days, then the period may be extended
to the subsequent regularly scheduled meeting). The AC will decide how
to utilize the proposal and announce the decision to the PPML.

The AC invites everyone to comment on the proposal on the PPML,
particularly their support or non-support and the reasoning
behind their opinion. Such participation contributes to a thorough
vetting and provides important guidance to the AC in their deliberations.

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

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

Mailing list subscription information can be found
at: https://www.arin.net/mailing_lists/

Regards,

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


## * ##


ARIN-prop-144 Remove Single Aggregate requirement from Specified Transfer

Proposal Originator: Matthew Kaufman

Proposal Version: 1

Date: 2 May 2011

Proposal type: new

Policy term: permanent

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