[arin-ppml] Additional modifications to Section 8.3 related to ASN's and legacy addresses

[Martin Hannigan]

Policy Proposal Name: Section 8.3 Modifications: ASN and legacy resources

Policy Proposal Name: Inter-RIR
Proposal Originator
  name: Martin Hannigan
  email: martin at theipv4guy.com
  telephone:
  organization: Elected ARIN Advisory Council Member
Proposal Version: 1.0
Date: 21 May 2012
Proposal type: NEW
Policy term: PERMANENT
Policy statement:


Change Policy Statement from:

8.3 Transfers to Specified Recipients

In addition to transfers under section 8.2, IPv4 number resources may be
released to ARIN by the authorized resource holder or another RIR, in
whole or in part, for transfer to another specified organizational
recipient. Organizations in the ARIN region may receive transferred
number resources under RSA if they can demonstrate the need for such
resources in the amount which they can justify under current ARIN policies.

IPv4 address resources may be transferred to organizations in another
RIR's service region if they demonstrate need to their region's RIR,
according to that RIR's policies. Inter-regional transfers may take
place only via RIRs who agree to the transfer and share compatible,
needs-based policies. Such resources must be transferred in blocks of
/24 or larger and will become part of the resource holdings of the
recipient RIR.


Change policy statement to:


8.3 Transfers to Specified Recipients

In addition to transfers under section 8.2, IPv4 number resources and
16 bit ASN's may be
released to ARIN by an authorized resource holder or another RIR, in
whole or in part, for transfer to another specified organizational
recipient. Organizations in the ARIN region may receive transferred
IPv4 number resources under RSA if they can demonstrate that the need for such
resources exists and in the amount that they can justify under current
ARIN policies.

IPv4 address resources and 16 bit ASN's may be transferred to
organizations in another
RIR's service region if they demonstrate need to their region's RIR and
compliance with that RIR's policies. IPv4 number resources may be
transferred in blocks of
the minimum allocation unit of the recipient RIR and will become part
of the resource holdings of the
recipient RIR.

Needs assessments or services agreements with ARIN are not required
for legacy resource transfers.

ARIN will provide a written and detailed notice that includes the
reasons why when refusing any number resource or ASN transfer.  This
notice will be provided to both parties to the transfer and to the
recipient RIR.

Rationale:

To further increase the utilization of available 16 bit ASN's in order
to stimulate 32 bit ASN uptake. The resulting benefit will be realized
over (a shorter period of) time as desirable numbers are used from
both pools of addresses and software, systems and processes integrate
the same to accommodate an eventual compatibility of both pools
instead of partial backwards compatibility overall.

With regards to the language modifications related to v4 number
resources, suggested modifications will pull the stop on the legacy
market and make it "more" attractive to utilize the ARIN based
transfer system and improve the accuracy of whois data overall.
Portions of this proposal would result in greater value to debtors and
by creating further support of ARIN policy and confidence in the
system. Increasing the level of confidence that a transaction will
succeed is "a good thing". Written notice to insure transparency.
There are also a few in simple in-context grammatical edits.

Note, this is the pre-approved but not yet implemented language vs.
the old language. I have confidence 2011-1 is moving forward and this
would modify that language.