ARIN-prop-274: No Specified Transfers for 4.1.8.2 Blocks [Archived]

OUT OF DATE?

Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.

Date: 10 April 2019

Proposal Originator: Joe Provo

Problem Statement:

The ARIN “Unfulfilled Requests” policy creates an opportunity for an ARIN member to claim need for number resources, wait for those resources to become available via returns or reclamations, acquire them (per 4.1.8.2 of the NRPM), wait a day after the mandatory “hold time”, and then profit from them via a specified transfer transaction.

This waiting list policy freely provides number resources, creating an incentive for profit-taking through fraudulent applications or making misrepresentations to registration services.

ARIN can avoid this problem by prohibiting non-8.2 transfers for blocks distributed under 4.1.8.2 using language very similar to policy elsewhere in the NRPM.

Policy Statement:

Add a second paragraph to 4.1.8.2:

IP allocations issued through 4.1.8.2 are non-transferable via section 8.3 and section 8.4. In the case of a section 8.2, transfer of the IP assignment must be utilized for the same purpose or needs justified used for the original 4.1.8 application.

Timetable for Implementation: Immediate

OUT OF DATE?

Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.