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. It does not require the implementation of such aggregation in routing, only the implementation of an addressing plan that is subnetted along these topological boundaries to support the ability to aggregate.

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 serving site blocks to serving sites, and has sufficient actual utilization at their serving sites to continue to justify the block size being utilized for all serving sites as 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.

Proposal text:
Modify 6.5.3.b as follows:
An LIR may request a subsequent allocation when they can show utilization
of:
75% or more of their total address space
or
more than 90% of any serving site
or
when 75% of the aggregate has been subnetted, and each subnet contains at least 1* customer or infrastructure allocation or assignment
( *1 can be replaced here with any reasonable number)

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.