Recommended Draft Policy ARIN-2012-2: IPv6 Subsequent Allocations Utilization Requirement [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
Status: NRPM 6.5.3
Tracking Information
Discussion Tracking
Mailing List:
Formal introduction on PPML on 22 February 2012
Origin - ARIN-prop-159
Draft Policy - 22 February 2012 (with staff assessment)
Draft Policy - 25 February 2012 (with staff assessment) correction
Remains on AC’s docket - 30 April 2012
Revised - 26 September 2012
Updated staff assessment - 12 October 2012
Remains on AC’s docket - 31 October 2012
New Policy Development Process - 14 January 2013
Recommended Draft Policy - 26 March 2013
Last call - 29 April through 13 May 2013
AC recommended Board adopt - 17 May 2013
Implemented - 24 July 2013
ARIN Public Policy Meeting:
ARIN Advisory Council:
AC Shepherds:
Heather Schiller and Cathy Aronson
- 16 February 2012
- 8 March 2012
- 25 April 2012
- 17 May 2012
- 14 June 2012
- 19 July 2012
- 16 August 2012
- 20 September 2012
- 26 October 2012
- 15 November 2012
- 20 December 2012
- 25 January 2013
- 21 February 2013
- 21 March 2013
- 24 April 2013
- 16 May 2013
ARIN Board of Trustees:
Revisions:
Implementation:
24 July 2013
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
-
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. -
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.
- 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 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).
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.