[ppml] Policy Proposal 2005-1: Provider Independent IPv6 Assignments for End-sites
ARIN welcomes feedback and discussion about the following policy
proposal in the weeks leading to the ARIN Public Policy Meeting
in Orlando scheduled for April 18-20, 2005.
According to the ARIN Internet Resource Policy Evaluation Process
the Advisory Council will evaluate policy proposals after the Public
Policy Meeting. The feedback and discussion of policy proposals
on the Public Policy Mailing List will be included in the AC's
The policy proposal text is below and can be found at:
Subscription information for the ARIN Public Policy Mailing List can be
The ARIN Internet Resource Policy Evaluation Process can be found at:
ARIN's Policy Proposal Archive can be found at:
Member Services Department
American Registry for Internet Numbers
Register for ARIN XV and NAv6TF Summit, April 17-21, 2005, Orlando, FL
E-mail memsvcs at arin.net
### * ###
Policy Proposal Name: Provider Independent IPv6 Assignments for End-sites
Author: Owen DeLong
Policy statement: to be added to NRPM Section 6, IPv6, a new sub-section:
6.11 Assignments to End-Sites with Autonomous System Numbers
Any end-site which meets the current criteria for assignment of an
autonomous system number (ASN) shall also qualify for one IPv6 prefix
assignment of the minimum size justified under the ARIN guidelines for
assignment by an LIR. If the organization grows to require more space, it
will not be entitled to an additional block, but rather may obtain a new,
replacement block of sufficient size to meet its needs in exchange for
making the commitment to return its existing block within 24 months, so
that it may be reassigned.
There is a legitimate and growing need for provider independent addressing
for end-site organizations. While there were and are technical reasons for
limiting this in the IPv4 world, they need to be solved in the IPv6 world,
or, we will not see widespread adoption of IPv6.
This policy does not promote extreme growth in the routing table, as it
would provide support for fewer than 70,000 IPv6 prefixes if every
organization that currently has an ASN were to get an assignment, grow,
and, be in the 24 month renumbering period. Realistically, it is
unreasonable to think that this policy would contribute even 10,000 routes
to the IPv6 table in the near term future.
This policy provides for reasonable IPv6 provider independent assignments
without creating a land-grab, explosive routing table growth, or a IPv6
All such assignments under this policy shall be subject to the same
renewal criteria as IPv4 end-user assignments with a fee structure to be
set by ARIN in the usual and customary way.
Concerns were expressed about being able to reclaim this space and about a
land rush. Should an IPv6 land rush occur under this policy (an ASN land
rush would be required first), the ARIN BOT has emergency authority to
suspend this or any other policy in the interests of the internet with
appropriate review at the next public policy meeting. As to reclamation,
it is quite clear in the Registration Services Agreement:
4. Conditions of service ...
(d) Changes to Services. Applicant acknowledges and agrees that ARIN
fulfills a critical role in the continued evolution of the Internet and,
accordingly, ARIN may, in its sole and absolute discretion, change,
modify, suspend, or make improvements to any aspect of the Services,
temporarily or permanently, at any time without specific notice to
Applicant, and ARIN will not be liable for doing so. ARIN will have the
right from time to time to change the amount of the fees or institute new
fees relating to the Services, as set forth in Section 6, but such changes
to fees will only take effect upon the renewal of the Services.
Also, according to subsequent sections of the agreement, ARIN may simply
choose not to renew the agreement with 30 days notice to the applicant.
Either of these actions makes reclamation quite possible.