[arin-ppml] Revised text for 2012-2 -- IPv6 Subsequent Allocations Utilization Requirement

[Heather Schiller]

Updated text below.. This version incorporates staff suggested change
for wording of 90% of serving site
allocation and removes the modification to 2.14 (definition of a
serving site) that required subnetting according to
the plan justified to ARIN.

The diff from the NRPM is the addition of the 3rd * under 6.5.3.b

I also updated the rationale.  Feedback please.

--Heather



Draft Policy ARIN-2012-2
IPv6 Subsequent Allocations Utilization Requirement

Date:

Policy statement:

2.14. Serving Site (IPv6) When applied to IPv6 policies, the term
serving site shall mean a location where an ISP terminates or aggregates
customer connections, including, but, not limited to Points of Presence
(POPs), Datacenters, Central or Local switching office or regional or
local combinations thereof.

6.5.3. Subsequent Allocations to LIRs

a.      Where possible ARIN will make subsequent allocations by
expanding the existing allocation.

b.      An LIR qualifies for a subsequent allocation if they meet any
of the following criteria:

* Shows utilization of 75% or more of their total address space

* Shows utilization of more than 90% of any serving site

* Has allocated more than 90% of their total address space to serving
sites, with the block size allocated to each
serving site being justified based on the criteria specified in section 6.5.2

c.      If ARIN can not expand one or more existing allocations, ARIN
shall make a new allocation based on the
initial allocation criteria above. The LIR is encouraged, but not
required to renumber into the new
allocation over time and return any allocations no longer in use.

d.      If an LIR has already reached a /12 or more, ARIN will allocate a
single additional /12 rather than continue expanding nibble boundaries.

Original Rationale:

If you are executing to a long term plan, you should be able to continue
to execute on your approved allocation and assignment plan regardless of
the number of regions/groupings you originally planned for. We want to
promote tie downs on nibbles and long term planning.

Updated Rationale:

Subnet expansion may occur rapidly and un-evenly in the early stages
of IPv6 deployment.  Providers may find that
they have put all of their subnets/serving sites into service, and do
not have enough space to add an additional
serving site.  They may have plenty of space available within subnets
to make customer assignments, but can not turn
up a new location (eg city, pop)


Timetable for implementation: Immediately