ARIN-prop-281: Reserved Pool Replenishment [Archived]

Date: 15 November 2019

Proposal Originator: David Farmer

Problem Statement:

While the current level of resources in the reserve pools created in Sections 4.4 and 4.10 presently seem more than adequate for their intended purposes. Nevertheless, even these well-resourced pools will eventually run out. Therefore, we should make arrangements for their replenishment, if or when necessary.

Policy Statement:

Add a new subsection in IPv4 General Principles, Section 4.1;

4.1.X Reserved Pool Replenishment

Any resources allocated from a reserved pool created in Sections 4.4 or 4.10, or any other reserved pools created in the future, that are returned, reclaimed, or revoked will be returned to the reserved pool they were originally allocated from, regardless of the current level of each pool. Further, any other resources returned, reclaimed, or revoked will be prioritized for the replenishment of any reserved pool that falls below a running three-year supply, which is based on the previous three years of allocations from each pool.

Timetable for Implementation: Immediate

Anything Else:

ARIN Staff should regularly report on the levels and projected run-times for each reserved pool and immediately report when any reserved pool falls below a three-year running supply.

A three-year running supply was chosen to provide the ARIN Policy Community adequate time to react through policy, as deemed appropriate at that time, to an imminent run out event for one of the reserved pools.