ARIN-PPML Message

[arin-ppml] ARIN-prop-175 Delete Section 8.2

ARIN-prop-175 Delete Section 8.2

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-175 Delete Section 8.2

Proposal Originator: Harrison Grundy

Proposal Version: 1

Date: 20 June 2012

Proposal Type: Modify

Policy Term: Permanent

Policy Statement:

Delete section 8.2, and renumber section 8.3 to 8.2,

Add language to the new Section 8.2 (Transfers to Specified Recipients):

"ARIN will provisionally update the registry to reflect the transfer
request initiated by the resource holder pending ARIN's approval or
rejection of the transfer. If the transfer is rejected, ARIN will update
the registry to reflect the original resource holder."

Rationale:

Transfers due to mergers and acquisitions should follow the same process
as any directed transfer. Current language in the NRPM is silent on the
status of those resources as it relates to RSAs, while requiring that
the number resources of the merged organisations comply with ARIN's
policies. This situation is needlessly confusing, and serves only to
create a legal grey area for these resources.

There is also no clear delineation on when an entity may elect to
perform an 8.2 transfer over an 8.3 transfer, beyond the requirement
that "the new entity has acquired assets that used the transferred
resources from the current registrant". Purchasing a single router from
an entity should not magically transform what is otherwise a transfer to
a specified recipient into a special transfer that does not carry the
requirements of an 8.3 transfer. The text of 8.2 would also appear to
preclude transferring resources that are not currently in use.

This policy proposal serves to homogenise transfer requirements so that
there is one simple method of transfer, regardless of the business
circumstances surrounding that transaction.

By immediately updating the registry upon receiving a request,
renumbering pain as part of M&A transactions will only occur where the
resources will not be used for their already approved purpose.

Timetable for implementation: Immediate