Recommended Draft Policy 2012-2: IPv6 Subsequent Allocations Utilization Requirement

[ARIN]

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

On 21 March 2012 the ARIN Advisory Council (AC) recommended ARIN-2012-2 
for adoption, making it a Recommended Draft Policy. ARIN-2012-2 will be 
presented at ARIN 31, and will be eligible for last call afterward.

Draft Policy ARIN-2012-2 is below and can be found at:
https://www.arin.net/policy/proposals/2012_2.html

You are encouraged to discuss Draft Policy 2012-2 on the PPML prior to
the upcoming Public Policy Consultation. Both the discussion on the list 
and at the meeting will be used by the ARIN Advisory Council to 
determine the community consensus for adopting this as policy.

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

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

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


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

Date: 26 March 2013

AC's assessment of conformance with the Principles of Internet Number 
Resource Policy:

Policy 2012-2 enables fair and impartial resource administration by 
creating an additional criteria under which LIRs can qualify for a 
subsequent allocation. This policy does not modify the definition of who 
is covered under the existing policy. This proposal addresses a 
technical blindspot in the existing subsequent allocation policy that 
limits initial IPv6 deployment growth. Over the last year, there has 
been significant community support on the mailing list and at meetings 
to rectify this blindspot. Coming to an agreement on specific wording 
that does not open this to abuse has been more difficult.

Policy statement:

The change to the NRPM is the addition of the third bullet in 6.5.3.b.

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.

Rationale/Problem Statement:

Subnet expansion may occur rapidly and unevenly 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


##########


ARIN Staff and Legal Assessment

ARIN Staff Assessment
ARIN-prop - 2012-2 “Subsequent Allocations Utilization Requirement” 
(Updated version)
Date of Assessment: 14 March 2013

1.	Summary (Staff Understanding)
The intent of this proposal is to allow an additional way for ISP's that 
have already begun using their IPv6 space but who may not have 
sufficiently planned for longer term growth, to receive an additional 
allocation.  This policy would allow ISPs who have allocated at least 
90% of their space to serving sites to qualify for an additional 
allocation as long as the block size allocated to each serving site is 
justified based on the number of customers at the largest single serving 
site.

  2. Comments
A.	ARIN Staff Comments

•	The updated text in 6.5.3b adds consistency and clarity to the policy 
by allowing the block size for the subsequent allocation to be based on 
the same criteria used to determine the block size for the initial 
allocation.
•	This policy is clear and implementable as written.

B.	ARIN General Counsel - Legal Assessment
This policy does not create significant legal issues.

3. Resource Impact
This policy would have minimal resource impact from an implementation 
aspect.  It is estimated that implementation would occur within 3 months 
after ratification by the ARIN Board of Trustees. The following would be 
needed in order to implement:
A.	Updated guidelines
B.	Staff training

Proposal Text:

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 cannot 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.

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).