Your IP address could not be determined at this time.

Draft Policies and Proposals

Recommended Draft Policy ARIN-2014-17: Change Utilization Requirements from last-allocation to total-aggregate
Status:

Awaiting Board Review

 
Discussion Tracking
Mailing List:
Formal introduction on PPML on 16 May 2014

Origin - ARIN-prop-209

Draft Policy - 16 May 2014

Revised - 14 July 2014

Staff assessment - 19 September 2014

Revised - 20 November 2014

Recommended Draft Policy - 24 December 2014

Last Call - 24 February through 10 March 2015

AC recommended Board adopt - 24 March 2015

 

 

Public Policy Mailing List
ARIN Public Policy Meeting:

ARIN PPC at NANOG 61

ARIN PPC at NANOG 62

ARIN 34
ARIN PPC at NANOG 63

ARIN Advisory Council:

AC Shepherds:
Andrew Dul, Owen DeLong

ARIN Board of Trustees:
Revisions Implementation

Recommended Draft Policy ARIN-2014-17
Change Utilization Requirements from last-allocation to total-aggregate

Date: 19 October 2014

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

This proposal enables fair and impartial number resource administration by removing an impediment to additional allocations seen by some organizations due to the shortening of the assignment window to three months and the gradual reduction of minimum block size over the past 5 years. This draft proposal applies equally to all organizations and now requires that any netblock show at least 50% utilization before an additional block can be allocated or assigned. The policy is clear and implementable as written. This proposal is technically sound. There are no technical issues which are raised by changing the utilization definition within the NRPM. This proposal is supported by the community. Support for this draft proposal has been growing as it has been discussed. Additional support from the community was seen as issues which were brought to the attention of the community by the first staff and legal assessment have been mitigated.

Problem Statement:

Current ARIN policy calculates utilization on a per allocation basis rather than in aggregate. This method of determining utilization may cause some organizations to be unable to qualify for additional address blocks despite attempting to use their resource allocations as best as possible. This issue has been exacerbated in the past couple of years due to the 3-month allocation window which causes organizations to receive smaller non-expandable allocations rather than a larger aggregate.

For example, if an organization has 4 x /22 and 3 of them are utilized 100% and the fourth utilized at 75%, an additional allocation request would be denied. However, an organization with a single /20 utilized at 80% would have less efficient utilization but would be eligible to receive additional space.

Policy statement:

Replace Section 4.2.4.1

ISPs must have efficiently utilized all allocations, in aggregate, to at least 80% and at least 50% of every allocation in order to receive additional space. This includes all space reassigned to their customers.

Replace Section 4.3.6.1

End-users must have efficiently utilized all assignments, in aggregate, to at least 80% and at least 50% of every assignment in order to receive additional space, and must provide ARIN with utilization details.

Timetable for implementation: Immediate

#####

ARIN STAFF ASSESSMENT

Draft Policy ARIN-2014-17
Change Utilization Requirements from last-allocation to total-aggregate
Date of Assessment: November 2014

1. Summary (Staff Understanding)

This policy removes the current requirement to have efficiently utilized all previous allocations and assignments, and 80% of the most recent one, and replaces it with the requirement to have efficiently utilized all allocations and assignments in aggregate, to at least 80% overall, with at least a 50% utilization of every allocated or assigned block.

2. Comments

A. ARIN Staff Comments

Based on staff experience, the 80% utilization rate of the last block has been periodically problematic for smaller ISPs, but not for medium to larger ISPs. Staff has seen situations where a small ISP with a /22 may need to issue a /24 to a customer but not have any available, not be at 80% utilized, and therefore, not be able to request additional space.

This policy could be implemented as written.

B. ARIN General Counsel - Legal Assessment

The policy does not present material legal issues. Allocation rules to address concerns of small ISP's indicate ARIN's continued attempts to balance the needs of stewardship with the needs of different sectors.

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:
-Updated guidelines and internal procedures
-Staff training

4. Proposal/Draft Policy Text Assessed

Draft Policy ARIN-2014-17 Change Utilization Requirements from last-allocation to total-aggregate
Date: 19 October 2014
Problem Statement:
Current ARIN policy calculates utilization on a per allocation basis rather than in aggregate. This method of determining utilization may cause some organizations to be unable to qualify for additional address blocks despite attempting to use their resource allocations as best as possible. This issue has been exacerbated in the past couple of years due to the 3-month allocation window which causes organizations to receive smaller non-expandable allocations rather than a larger aggregate.
For example, if an organization has 4 x /22 and 3 of them are utilized 100% and the fourth utilized at 75%, an additional allocation request would be denied. However, an organization with a single /20 utilized at 80% would have less efficient utilization but would be eligible to receive additional space.
Policy statement:
Replace Section 4.2.4.1
ISPs must have efficiently utilized all allocations, in aggregate, to at least 80% and at least 50% of every allocation in order to receive additional space. This includes all space reassigned to their customers.
Replace Section 4.3.6.1
End-users must have efficiently utilized all assignments, in aggregate, to at least 80% and at least 50% of every assignment in order to receive additional space, and must provide ARIN with utilization details.

 

#####

Older version

Draft Policy ARIN-2014-17
Change Utilization Requirements from last-allocation to total-aggregate

Date: 14 July 2014

Problem Statement:

Current ARIN policy calculates utilization on a per allocation basis rather than in aggregate. This method of determining utilization may cause some organizations to be unable to qualify for additional address
blocks despite attempting to use their resource allocations as best as possible. This issue has been exacerbated in the past couple of years due to the 3-month allocation window which causes organizations to
receive smaller non-expandable allocations rather than a larger aggregate.

For example, if an organization has 4 x /22 and 3 of them are utilized 100% and the fourth utilized at 75%, an additional allocation request would be denied. However, an organization with a single /20 utilized at
80% would have less efficient utilization but would be eligible to receive additional space.

Policy statement:

Update Section 4.2.4.1

ISPs must have efficiently utilized all allocations, in aggregate, to at least 80% in order to receive additional space. This includes all space reassigned to their customers.

Update Section 4.3.6.1

End-users must have efficiently utilized all assignments, in aggregate, to at least 80% in order to receive additional space, and must provide ARIN with utilization details.

Timetable for implementation: Immediate


 


Advanced Search

Relevant Links