Draft Policy ARIN-2023-8: Reduce 4.1.8 Maximum Allocation
Trying to distill the various discussions and positions as posted in the PPML
regarding this policy. The text has been updated, to include a clause to
provide protection to existing Waitlist participants' applications that predate
the implementation of the policy.
We (the shepherds) understand that there is not sufficient support without
language providing protection for pre-existing requests, and still seems to not
be sufficient even with that aforementioned clause. We are still seeing very
polarized positions without a clear move towards consensus.
"A company joining ARIN’s IPv4 Waitlist today should expect to wait at least
three years"
"Reducing the maximum allocation from a /22 (1,024 addresses) to a /24 (256
IPv4 addresses) could reduce wait times by almost two-thirds"
- John Sweeting, ARIN CCO - ARIN 52
Waitlist size = 824 (as at September 27, 2024)
This means that the policy, if adopted, will take effect only for new Waitlist
entrants, which evokes further discussion on the potential impact which must be
examined.
Consider the following points:
* [Do Nothing] When accounting for the current IPv4 Waitlist status, there
is an approximately 3+ year wait for the existing requests to be completely
fulfilled;
* [Retroactive Protections] If, as per this draft policy, the size is
reduced to a /24 minimum, rather than a /22, it will still require a similar
3-year lead time before the pending requests can be fulfilled, to then move to
only satisfying requests for /24s.
* [No Protections, Immediate Reductions] If the size is reduced to a /24
minimum for all requests immediately, there will be a significant reduction in
duration of wait times. Should requests for larger sizes consider the
marketplace for fulfillment?
This means that adoption of the policy with the protection clause, there is a
minimum 3-year lag from the date of implementation before any realizable effect
on the size of the Waitlist from this policy. As such, it raises the question
- is this an efficient approach to addressing the perceived problem?
- will this policy lead to a material difference or impact to the availability
and allocation of IPv4 addresses (beyond the affordability factor)?
- should the status quo simply be allowed to obtain?
- should the Waitlist be scrapped and allow the retail space handle IPv4
requests (again, noting the affordability factor)?
We are now seeing 4 feasible options for this Draft Policy:
1. Consider revised policy as written (with proposed retroactive
protections - still 3+-year lag and wait times);
2. Consider policy without any retroactive protections (reduction in wait
times by ⅔s);
3. Do away with the Waitlist completely (new policy would be required);
4. Abandon the policy (essentially, do nothing, no changes to current
operations)
Looking forward to presenting at ARIN 54 in a couple weeks, encouraging lively
discussions (including as a Table Topic) and hope that we can arrive at some
level of agreement to move forward.
**ARIN-2023-8: Reduce 4.1.8 Maximum Allocation**
Revised text is below and can be found at:
https://www.arin.net/participate/policy/drafts/2023_8
---------
Draft Policy ARIN-2023-8: Reduce 4.1.8 Maximum Allocation
Problem Statement:
4.1.8 waiting times are too long, making justifications untimely by the time a
request is met. New entrants to the waiting list are expected to wait three
years for their need to be met under current policy, with a waiting list of
around 700 at this point. Data indicates that reducing the current /22 maximum
further to a /24 would significantly reduce this waiting period, and further
tightening the requirements by replacing the /20 recipient maximum holdings
with a /24, and preventing multiple visits to the waiting list queue.
Policy Statement:
4.1.8. ARIN Waitlist
ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
organization may qualify for is a /24.
Organizations which ever held any IPv4 space other than special use space
received under section 4.4 or 4.10 are not eligible to apply.
Address space distributed from the waitlist will not be eligible for transfer,
with the exception of Section 8.2 transfers, for a period of 60 months. This
policy will be applied to all future distributions from the waitlist to include
those currently listed. Qualified requesters will also be advised of the
availability of the transfer mechanism in section 8.3 as an alternative
mechanism to obtain IPv4 addresses.
Waiting list recipients must demonstrate the need for a /24 on an operating
network.
This policy will apply to waitlist requests received following the
implementation of this policy. Waitlist requests received prior to the
implementation of this policy will not be affected.
Gerry E. George
ICT Consultant and Business Solutions Architect;
Digi Solv , Inc. [P.O. Box 1677, Castries, Saint Lucia]
Mobile : (758) 728-4858 / Int'l Office : (347) 450-3444 / Skype: DigiSolv
Email : [email protected] / LinkedIn :
https://www.linkedin.com/in/gerrygeorge/
Please consider the environment before printing this email. Thank you.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
