2011-1 Previous Version [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.
View the current policy proposal text.
The following version was archived on 19 October 2011
Draft Policy ARIN-2011-1
ARIN Inter-RIR Transfers
Date: 22 September 2011
Policy statement:
Address resources may be transferred in or out of the ARIN region to those who demonstrate need and plan to deploy them for a networking purpose within 3 months. Such transfers will take place between RIRs who share compatible, needs-based policies supporting entities agreeing to the transfer and which otherwise meet both RIR’s policies. Transferred resources will become part of the resource holdings of the recipient RIR unless otherwise agreed by both RIRs.
Rationale: Since individual RIRs now allow transfers, it makes sense to be able to transfer between regions as well. Reasoning….It is explicit about…
in or out of region,
that transfers are between RIRs that support needs-based policies,
that RIRs have to agree,
that parties meet all of both RIR policies
that it is needs based, and the need is for a networking purpose,
that the receiving RIR is entitled to the addresses
I think all these details were raised as objections at one time or another…so it seems best to waste a few more words to be explicit.
It is not explicit about…
block sizes
utilization of prior allocations,
assignments or transfers
RFC 2050
subsequent transfers
Timetable for implementation: Upon ratification by the ARIN Board of Trustees
#######################################################################
The following version was archived on 22 September 2011.
Draft Policy ARIN-2011-1
Globally Coordinated Transfer Policy
Version/date: 23 December 2010
Policy statement:
Any RIR’s resource registrant may transfer IPv4 addresses to the resource registrant of another RIR as long as the two RIRs agree and maintain compatible, needs-based transfer policies that exercise Internet stewardship consistent with the values expressed in RFC2050.
Rationale: Since individual RIRs now allow transfers, it makes sense to be able to transfer between regions as well.
Timetable for implementation: upon ratification by the ARIN Board of Trustees
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.