[arin-ppml] Draft Policy ARIN-2019-21: Reserved Pool Replenishment
jsweeting at arin.net
Fri Jan 3 13:48:15 EST 2020
On 1/3/20, 12:25 PM, "ARIN-PPML on behalf of Owen DeLong" <arin-ppml-bounces at arin.net on behalf of owen at delong.com> wrote:
> On Dec 26, 2019, at 16:38 , Fernando Frediani <fhfrediani at gmail.com> wrote:
> There are two points to analyze in this proposal:
> - Any returned, reclaimed or revoked addresses that belong originally to the reserved pools to be returned to them. I think this was pretty obvious and was already done this way and wouldn't be necessary to state it again. Could the author show that this is not the way it is currently done then I am fine to support this part.
Whether it is done this way or not, would be a question for the RSHD and/or John Sweeting. I honestly don’t know the current practice.
(JS)>>Yes, this is the way they are handled in current policy. All special reserved pool IPv4 addresses are returned to the pool they are reserved for.
However, codifying it in policy (it is not currently) is good either way as it provides clarity and ensures that it is done that way unless the community makes a deliberate change to the policy.
> - With regards returning any other returned, reclaimed or revoked resources that were not from the reserved pools to them, although I see the good intent of it I find it difficult to support it as we don't know numbers related to this at the present. The numbers of assignments from these reserved pools, the amount available and the forecast for it are necessary for this analysis.
The beauty of the way this proposal is structured is that it only replenishes those pools up to a historical 3-year supply.
So, for example, if the last three years saw the distribution of 25, 60, and 80 /24 equivalents, then a 3-year supply would be considered to be 165 /24 equivalents. As the sliding three-year look-back window changes, so would the amount of supply required to consider the pool “full”.
> Also it seems that three-year supply a long time for it to be kept. If the numbers mentioned point to the direction of the need of replenishing for these pools then the it may be necessary to review and discuss the supply time better. Without this information I cannot support this part of the proposal yet.
The information is probably available in the statistics on the ARIN web site. However, I agree that having staff provide more details would be useful in informing the discussion here. I will make a formal request.
(JS)>>The stats for 4.4.
Year # IX # CI
2013 12 1
2014 21 0
2015 15 3
2016 7 2
2017 17 8
2018 19 0
2019 18 0
The stats for 4.10
> On 24/12/2019 11:41, ARIN wrote:
>> On 19 December 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-281: Reserved Pool Replenishment" as a Draft Policy.
>> Draft Policy ARIN-2019-21 is below and can be found at:
>> You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion in order to assess the conformance of this draft policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are:
>> * Enabling Fair and Impartial Number Resource Administration
>> * Technically Sound
>> * Supported by the Community
>> The PDP can be found at:
>> Draft Policies and Proposals under discussion can be found at:
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>> Draft Policy ARIN-2019-21: Reserved Pool Replenishment
>> 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.
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> Please contact info at arin.net if you experience any issues.
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML