prop-077: Proposal to supplement transfer policy of historical IPv4 addresses

Proposal text	prop-077-v001
Synopsis	This policy proposal seeks to supplement current policy for the transfer of historical Internet resources, by requiring recipients of transferred historical IPv4 address space to justify its use.
Current status	Withdrawn by authors.
Authors	Terence Zhang Yinghao Jane Zhang Wendy Zhao Wei
Relevant forum	Policy SIG
Previous versions	NA
Status at other RIRs	AfriNIC: If an LIR plans to exchange or transfer address space, it needs to contact AfriNIC so that the changes are properly registered. The LIR remains responsible for all the allocations registered in the AfriNIC database until they have been transferred to another LIR or returned to AfriNIC. There is no requirement to justify the transfer. ARIN has two different transfer policies: Mergers and acquisitions Under this policy, organizations must show documentation that justifies use of the resources. However, organizations do not need to meet the current criteria for receiving IPv4 addresses to justify the transfer of historical space as part of a merger or acquisition. The recipient has the option of signing either the Legacy Resource Services Agreement or the standard Resource Services Agreement. Transfers to specified recipients Under this policy, historical resources, like current resources, must first be returned to ARIN. The space can be transferred only if the recipient can demonstrate the need for the resources under current ARIN policies. The recipient must sign the standard Resource Services Agreement. LACNIC permits transfers of historical IPv4 resources in cases of mergers and acquisitions only. Organizations must show documentation that they are not only transferring IP addresses but also equipment and end users of the IP addresses. In these cases, organizations do not need to meet the current criteria for receiving IPv4 addresses to justify the transfer of historical space as part of a merger or acquisition. Once historical resources have been transfered this way, they are considered to be "current". RIPE: Member LIRs can transfer complete or partial blocks of historical or current IPv4 addresses. Such address space must not contain any block that is assigned to an end user. An LIR may only receive a transferred allocation after their need is evaluated and approved by the RIPE NCC according to the existing allocation policies. LIRs that receive a transfer from another LIR cannot re-allocate complete or partial blocks of the same address space to another LIR within 24 months of receiving the re-allocation.
Proposal history
Date	Description
29 July 2009	Submitted to the Policy SIG mailing list for discussion.
27 August 2009	Returned to the authors for further consideration after discussion at APNIC 28.
20 August 2010	Withdrawn by authors.