[arin-ppml] Draft Policy 2009-1: Transfer Policy (UsingtheEmergency PDP)

Bill Darte BillD at cait.wustl.edu
Wed Mar 25 17:21:00 EDT 2009


2008-6 had marginal consensus support.  That support was largely due to
three things, I believe.
1. The policy statement was distilled to the most fundamental and
essential language.
2. The rationale made it quite clear what the intent was and as
specifically, what its intend was not.
3. The implementation timetable deferred the implementation until such a
time as there was indeed real scarity.

The 3 year sunset was obviously included to mute the contention that the
transfer policy was intended to be permanent, create a continuing
market, and bolster the legacy IPv4 over emergence of IPv6.  And, the
sunset period would not begin, now, but when an emergency scarcity was
obvious, so the sunset's removal now seems to serve no purpose.  The
term of the sunset was always questionable, but was short expecting that
such and emergency would not endure and if it did, it could be extended.
Removal of the sunset, again, seems to suggest and expectation of the
Board that the policy would now become business as usual rather than an
antidote to a real emergency.

If the intent is to declared that an emergency scarcity of IPv4
addresses exists now and that transfers between individuals can commense
upon ratification and implementation, and that those transfers will
continue ad infinitum until the ARIN community wills the policy to be
recinded, then I believe there needs to be some specific evidence
presented which illustrates that ARIN can no longer "fulfill its mission
and [to] facilitate a continuing supply of IPv4 address resources to its
service community" as the rationale states.

And if that is so, then I suggest that the ARIN BoT and the ARIN
community as a whole needs to ramp up its efforts to effect a movement
to IPv6 in real and substantive ways.

Bill Darte
ARIN Advisory Council
Original Author of 2008-6


<<<<<<<< what it said, for clarity >>>>>>>>>

8.4 Emergency Transfer Policy for IPv4 Addresses

For a period of 3 years from policy implementation, authorized resource
holders served by ARIN may designate a recipient for number resources
they
release to ARIN.

Number resources may only be received under RSA in the exact amount
which can be justified under ARIN resource-allocation policies.

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 reach a threshold of scarcity
recognized by the ARIN Board of Trustees as requiring this policy
implementation. 




More information about the ARIN-PPML mailing list