[arin-ppml] Policy Proposal 107: Rework of IPv6 assignment criteria - Updated text

[David Farmer]

Here is some updated text including language allowing a /48 for each 
site of an organization with multiple sites and fixing the Community 
Network language. I have an outstanding question about how the community 
wants to deal with non-connected networks. But, I'm leaving the current 
language for now as it is most consistent with current policy.

Feed back please.

----

Template: ARIN-POLICY-PROPOSAL-TEMPLATE-2.0
1. Policy Proposal Name: Rework of IPv6 assignment criteria
2. Proposal Originator
    a. name: David Farmer
    b. email: farmer at umn.edu
    c. telephone: 612-812-9952
    d. organization: University of Minnesota
3. Proposal Version: 1.0
4. Date: 1/14/2010
5. Proposal type: modify
new, modify, or delete.
6. Policy term: Permanent
temporary, permanent, or renewable.
7. 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 number of sites and the number of subnets 
needed to support a site.

Organizations with multiple sites are encouraged to consider the use /56 
sub-assignments for smaller satellite sites.  Not withstanding this, 
organizations may request a /48 for each site in their network, with the 
overall allocation rounded up to the next whole prefix as necessary.  A 
subnet plan demonstrating a utilization of 33,689 or more subnets is 
necessary to justify an additional /48 for any individual site, beyond 
this the 0.94 HD-Ratio metric is used.

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. Currently being Multihomed or immediately becoming Multihomed and 
using an assigned valid global AS number, 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 sites and 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 non-connected network.  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 sites and 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 by documenting that they meet the criteria specified 
in section 2.11.  A Community Network is considered a single site and a 
larger initial assignment may only be justified based on the number of 
subnets necessary to serve the community in question.

6.5.9. Subsequent assignments

Subsequent assignments may be made when the need for additional sites or 
subnets are justified with reasonable supporting documentation. 
Organizations with multiple sites are encouraged to consider the use 
/56s for smaller satellite sites.  Not withstanding this, organizations 
may request a /48 for each site, with the overall allocation rounded up 
to the next whole prefix as necessary.  A subnet plan demonstrating a 
utilization of 33,689 or more subnets is necessary to justify an 
additional /48 for any individual site, beyond this the 0.94 HD-Ratio 
metric is used.  When possible, subsequent assignments will be made from 
an adjacent address block.

8. 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 Internet connected 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.
• Organizations with multiple sites are allowed to request a /48 for 
each site, with a suggestion to use /56s for smaller sites.
• While HD-Ratio is not completely eliminated it really only applies to 
situations that an individual site of an organization needs more that a /48.
• Community networks are assumed to justify an assignment in and of 
themselves, but they should be considered a single site, otherwise they 
should get an ISP allocation.

9. Timetable for implementation:  Immediate

END OF TEMPLATE

-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota	
2218 University Ave SE	    Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================