Policy Proposal 107: Rework of IPv6 assignment criteria

[Member Services]

ARIN received the following policy proposal and is posting it to the
Public Policy Mailing List (PPML) in accordance with Policy Development
Process.

This proposal is in the first stage of the Policy Development Process.
ARIN staff will perform the Clarity and Understanding step. Staff does
not evaluate the proposal at this time, their goal is to make sure that
they understand the proposal and believe the community will as well.
Staff will report their results to the ARIN Advisory Council (AC) within
10 days.

The AC will review the proposal at their next regularly scheduled
meeting (if the period before the next regularly scheduled meeting is
less than 10 days, then the period may be extended to the subsequent
regularly scheduled meeting). The AC will decide how to utilize the
proposal and announce the decision to the PPML.

In the meantime, the AC invites everyone to comment on the proposal on
the PPML, particularly their support or non-support and the reasoning
behind their opinion. Such participation contributes to a thorough
vetting and provides important guidance to the AC in their deliberations.

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

The ARIN Policy Development Process can be found at:
https://www.arin.net/policy/pdp.html

Mailing list subscription information can be found
at: https://www.arin.net/mailing_lists/

Regards,

Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Policy Proposal 107: Rework of IPv6 assignment criteria

Proposal Originator: David Farmer

Proposal Version: 1.0

Date: 1/14/2010

Proposal type: modify

Policy term: Permanent

Policy statement:

6.5.8. Initial assignments

6.5.8.1. Initial assignment size

Organizations that meet at least one of the following criteria are
eligible to receive a minimum assignment of /48.  Requests for larger
initial assignments, reasonably justified with supporting documentation,
will be evaluated based on the 0.94 HD-Ratio metric.

All assignments shall be made from distinctly identified prefixes, with
each assignment receiving a reservation for growth of at least a /44.
Such reservations are not guaranteed and ARIN, at its discretion, may
assign them to other organizations at any time.

6.5.8.2. Criteria for initial assignment to Internet connected end-users

Organizations may justify an initial assignment for connecting their own
network to the IPv6 Internet, with an intent to provide global
reachability for the assignment within 12 months, and for addressing
devices directly attached to their network infrastructure, by meeting
one of the following additional criteria.

a. Having a previously justified IPv4 end-users assignment from ARIN or
one of its predecessor registries, or;

b. Multihoming using an assigned Autonomous System Number (ASN), or;

c. By providing a reasonable technical justification indicating why
other IPv6 addresses from an ISP or other LIR are unsuitable and a plan
detailing the utilization of subnets for one, two and five year periods.


6.5.8.3 Criteria for initial assignment to non-connected networks

Organizations are encouraged to consider the use of Unique Local IPv6
Unicast Addresses (ULA, See RFC 4193) for a network that is not
currently connected and/or planning not to connect to the Internet.  Not
withstanding this, organizations may justify an initial assignment for
operating their own non-connected IPv6 network and for addressing
devices directly attached to their network infrastructure, by meeting
one of the following additional criteria.

a. Having a previously justified IPv4 end-users assignment from ARIN or
one of its predecessor registries, or;

b. By providing a reasonable technical justification indicating why an
assignment for a non-connected networks is necessary, including the
intended purpose for the assignment, and describing the network
infrastructure the assignment will be used to support.  Justification
must include why ULA IPv6 addresses are unsuitable and a plan detailing
the utilization of subnets for one, two and five year periods.

6.5.8.4 Criteria for initial assignment to Community Networks

Organizations may justify an initial assignment for operating a
Community Network only for the purpose of providing free or low-cost
internet connectivity to the residents of their local service area.

By documenting the service area they intend to serve, certifying that
the community network staff is 100% volunteers, and otherwise meeting
the definition of a Community Network.

6.5.9. Subsequent assignments

Subsequent assignments may be made when the need for additional subnets
are justified.  Justification will be determined based on the 0.94
HD-Ratio metric.  When possible, subsequent assignments will be made
from an adjacent address block.

Delete current 6.5.9 Community Network Assignments as it is incorporated
in 6.5.8.4.

Rationale:

This proposal provides a complete rework of the IPv6 end-user assignment
criteria, removing the dependency on IPv4 policy, while maintaining many
of the basic concepts contained in the current policies.  The order of
the subsections of 6.5.8 was rearranged moving the initial assignment
size to 6.5.8.1 and subsequent assignments to 6.5.9.  This will
facilitate adding future criteria without additional renumbering of
current policies.

The initial assignment criteria include the following general concepts;

• When Internet connectivity is use to justify resources it is implied
the resources should be advertised to the Internet, within some
reasonable time frame after they are received.
• IPv4 resources may be use to justify the need for IPv6 resources.
• Internet multihoming is sufficient justification for an end-user
assignment in and of itself.
• Other end-users must justify why an ISP or LIR assignment is not
sufficient for their needs.
• Non-connected networks must describe the purpose and network
infrastructure the assignment will be supporting, including why ULA is
not sufficient for their needs.
• Community networks are assumed to justify an assignment in and of
themselves.

Timetable for implementation:  Immediate