prop-096: Maintaining demonstrated needs requirement in transfer policy after the final /8 phase


Proposal text prop-096-v001

This is a proposal to maintain the requirement for recipients of IPv4 transfers to justify their need for address space beyond the current allocation phase and into the final /8 phase.

Current status Implemented.
Author Tomohiro Fujisaki
Co-authors Masaru Akai, Fuminori Tanizaki, Toshio Tachibana, Akira Nakagawa
Relevant forum Policy SIG
Previous versions NA
Status at other RIRs

All other RIRs that adopt the IPv4 transfer policy require demonstrated need at the time of the transfer.

AfriNIC: AfriNIC permits transfers of IPv4 addresses as part of name changes and transfers of tangible assets associated with addresses. Utilization of the addresses must be verified. See Section 8.1, "Introduction" in IPv4 Address Allocation Policies.

ARIN:ARIN policy requires that transfers to specified recipients can take place provided the recipient can demonstrate the need for such resources, as a single aggregate, in the exact amount which they can justify under current ARIN policies. See Section 8.3, Transfers to Specified Recipients in the ARIN Number Resource Policy Manual.

LACNIC: LACNIC policy has a transfer policy that will take effect when LACNIC or any of its NIRs becomes unable, for the first time, to cover an IPv4 block allocation or assignment because of a lack of resources. Under this policy, the recipient of the transfer must be able to justify its need for the IPv4 addresses. See Section, "Transfer of IPv4 Blocks within the LACNIC Region," in the LACNIC Policy Manual (v1.4).

RIPE: The RIPE policy permits transfers of complete or partial blocks of IPv4 allocations. The RIPE NCC will evaluate the real need of the receiving LIR as per the policies for further allocation. For more, see section 5.5, "Transfers of Allocations", in IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region.

Proposal history
25 January 2011 Submitted to the Policy SIG mailing list for discussion.
24 February 2011 Did not reached consensus at APNIC 31 Policy SIG. To be sent back to the Policy SIG mailing list for discussion.
4 March 2011 Returned to the Policy SIG mailing list for further discussion.
31 August 2011 Reached consensus at the APNIC 32 Policy SIG meeting.
1 September 2011 Reached consensus at the APNIC 32 Member Meeting.
6 September – 31 October 2011 Final eight-week comment period.

3 November 2011 Endorsed by the APNIC Executive Council for immediate implementation.
21 November 2011 Implemented.

  • Implementation announcement with call for editorial comment