[arin-ppml] Policy Proposal 2008-6: Emergency Transfer Policy forIPv4 Addresses

[Scott Leibrand]

I think I can answer #1: Bill proposed 2008-6 as an alternative to 2008-2, 
so that in case 2008-2 fails to reach consensus, we have a bare-bones 
alternative on the docket at L.A. that could be advanced if there's 
consensus for something simpler.

My own hope is that we'll discuss both a revised 2008-2 (based on survey 
results and further discussion here) and 2008-6 at L.A., make any 
remaining minor edits to 2008-2 to bring it in line with consensus 
(perhaps revising it to be more like 2008-6 on some points), and hopefully 
have the consensus to adopt 2008-2 at that point.  I guess we'll see if we 
can develop that level of consensus around the issue or not.

I'll let Bill respond regarding the specifics of his proposal.

-Scott

Milton L Mueller wrote:
> I am having trouble understanding this proposal and seek clarification. 
> 
> 1. How does this "emergency" transfer proposal relate to Policy Proposal
> 2008-2, the other transfer policy proposal? Is it considered a
> supplement to that proposal or a substitute for it?
> 
> 2. How does one engage in a transfer "without the active involvement of
> ARIN as an intermediary" when the recipient of the transfer must
> "document operational need in accordance with current ARIN policy" and
> sign an RSA "covering those resources in advance of transfer"? 
> 
> Milton Mueller
> Professor, Syracuse University School of Information Studies
> XS4All Professor, Delft University of Technology
> ------------------------------
> Internet Governance Project:
> http://internetgovernance.org
>  
> 
>> -----Original Message-----
>> From: arin-ppml-bounces at arin.net 
>> [mailto:arin-ppml-bounces at arin.net] On Behalf Of Member Services
>> Sent: Tuesday, August 26, 2008 8:50 AM
>> To: ppml at arin.net
>> Subject: [arin-ppml] Policy Proposal 2008-6: Emergency 
>> Transfer Policy forIPv4 Addresses
>>
>> On 21 August 2008, the ARIN Advisory Council (AC) concluded its review
>> of "Emergency Transfer Policy for IPv4 Addresses" and accepted it as a
>> formal policy proposal for discussion by the community.
>>
>> The proposal is designated Policy Proposal 2008-6: Emergency Transfer
>> Policy for IPv4 Addresses. The proposal text is below and can 
>> be found at:
>> http://www.arin.net/policy/proposals/2008_6.html
>>
>> All persons in the community are encouraged to discuss Policy Proposal
>> 2008-6 prior to it being presented at the ARIN XXII Public Policy
>> Meeting. Both the discussion on the Public Policy Mailing List
>> and at the Public Policy Meeting will be used to determine 
>> the community
>> consensus regarding this policy proposal.
>>
>> AC shepherds for this proposal are Owen DeLong and Stacy Hughes.
>>
>> The ARIN Internet Resource Policy Evaluation Process can be found at:
>> http://www.arin.net/policy/irpep.html
>>
>> ARIN's Policy Proposal Archive can be found at:
>> http://www.arin.net/policy/proposals/proposal_archive.html
>>
>> Regards,
>>
>> Member Services
>> American Registry for Internet Numbers (ARIN)
>>
>>
>> ## * ##
>>
>>
>> Policy Proposal 2008-6
>> Emergency Transfer Policy for IPv4 Addresses
>>
>> Author: Bill Darte
>>
>> Proposal Version: 1.0
>>
>> Submission Date:  August 15, 2008
>>
>> Proposal type: New
>>
>> Policy term:  Temporary
>>
>> Policy statement:
>>
>> 8.2.1 Emergency Transfer Policy for IPv4 Addresses
>>
>> For a period of 3 years from policy implementation, transfer of ARIN
>> IPv4 addresses between two entities in the ARIN region, without the
>> active involvement of ARIN as an intermediary, will be considered
>> legitimate and will be documented accordingly under the following
>> conditions:
>>
>> 1.  Transfer takes place from a holder of IPv4 addresses recognized by
>> ARIN as the legitimate and exclusive holder of those resources.
>>
>> 2.  Transfer takes place to a recipient that has documented 
>> operational
>> need in accordance with current ARIN policy and that signs an RSA with
>> ARIN covering those resources in advance of transfer.
>>
>> 3.  Transfer of addresses takes place in such a way that the original
>> contiguous block(s) are not disaggregated into more than 4 resultant
>> network blocks each being greater than or equal to the current minimum
>> sizes specified in applicable ARIN policy.
>>
>> 4.  Transfer is complete and unrestricted and is supported by
>> documentation that ARIN deems satisfactory.
>>
>>
>> Rationale:
>>
>> In order for ARIN to fulfill its mission and to facilitate a 
>> continuing
>> supply of IPv4 address resources to its service community when ARIN
>> resources are no longer adequate, and to preserve the integrity of
>> documentation and ARIN services for those resources, this 
>> policy may be
>> implemented.  Its intent is to preserve the current tradition of
>> need-based allocation/assignments for those still needing 
>> IPv4 resources
>> during a transition period as the industry adopts IPv6. This policy is
>> not intended to create a 'market' for such transfers and does not
>> introduce or condone the monetization of address resources or 
>> a view of
>> addresses as property.  It does recognize that organizations making
>> available unused or no longer needed address resources may 
>> incur certain
>> costs that might be compensated by those acquiring the 
>> resources.  This
>> policy is intended to be transient and light-weight and does not
>> encourage a sustained or continuing role for IPv4, but rather helps to
>> mitigate a transitional crisis that may emerge while the 
>> industry adopts
>> IPv6 in accordance with the recommendation of ARIN's Board of 
>> Trustees.
>>
>> Timetable for implementation:
>>
>> This policy, once ratified by the ARIN Board of Trustees, would be
>> implemented when either the free-pool of IANA addresses is 
>> exhausted or
>> IPv4 address resources in the ARIN Region reaches a threshold of
>> scarcity recognized  by the ARIN Board of Trustees as requiring this
>> policy implementation.
>>
>>
>>
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.