<div dir="ltr">Hi,<div><br></div><div>>I think that I speak for the WG, that the intent for the final /8 policy and the waitinglist policy, is to provide IPv4 (at least a small bit) to newcomers .. meaning that how it currently works and how it was >intended .. that this might not align with what the WG initially wanted. <br></div><div><br></div><div>A newcomer can still apply to get an /24 with the current policy, being in a waiting list means you need to wait (it aligns with the current policy). there was no intention to have a fast track or a definite waiting period to get the /24.</div><div>If a newcomer needs IPv4 urgently they can request an existing member to transfer IP address to them, looking at transfer statistics we can see that there are many v4 transfers happening every month.</div><div><br></div><div><br></div><div>Maybe better to find a way to push old members to return their free IPv4 blocks to have more free IP in the pool? This can be done by a change to the current billing method but that needs to be decided by NCC members, not the WG.</div><div><br></div><div>Regards,</div><div><br></div><div>Arash</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 8, 2021 at 1:29 AM Erik Bais <<a href="mailto:erik@bais.name">erik@bais.name</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Marco, <br>
<br>
Thank you for the detailed information of the dispersion about the current and past of the waitinglist. <br>
<br>
To the WG: <br>
<br>
The current workings of the IPv4 Waitinglist is specified in the IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region<br>
<br>
<a href="https://www.ripe.net/publications/docs/ripe-733#5" rel="noreferrer" target="_blank">https://www.ripe.net/publications/docs/ripe-733#5</a> <br>
<br>
Currently there is a First Come First Serve procedure for the waitinglist .. and there are no limitation to allocating v4 space to members that have been already allocated v4 space since the waitinglist started. <br>
<br>
I think that I speak for the WG, that the intent for the final /8 policy and the waitinglist policy, is to provide IPv4 (at least a small bit) to newcomers .. meaning that how it currently works and how it was intended .. that this might not align with what the WG initially wanted. <br>
<br>
If a change would be desired by the WG, it should go through the PDP, meaning that a policy change would be required. <br>
<br>
As WG chairs we would like to see the position of the WG on the topic and what could be seen as a possible solution. <br>
<br>
Regards,<br>
Erik Bais<br>
On behalf of the AP-WG Co-Chair collective. <br>
<br>
<br>
<br>
On 07/12/2021, 10:23, "address-policy-wg on behalf of Marco Schmidt" <<a href="mailto:address-policy-wg-bounces@ripe.net" target="_blank">address-policy-wg-bounces@ripe.net</a> on behalf of <a href="mailto:mschmidt@ripe.net" target="_blank">mschmidt@ripe.net</a>> wrote:<br>
<br>
Dear colleagues,<br>
<br>
In the Address Policy Working Group sessions at RIPE 83, I shared our <br>
observations regarding the IPv4 waiting list policy. [1]<br>
<br>
The intent of this policy was to provide newcomers with a minimal amount <br>
of IPv4 space for as long as possible. However, about half of these <br>
allocations went to members that received several /24 allocations via <br>
multiple LIR accounts.<br>
<br>
As there was interest in reviewing the policy at the RIPE Meeting, I <br>
would like to provide more detail on the provision of IPv4 allocations <br>
over the last two years and the current situation with the waiting list.<br>
<br>
In the last 24 months, we provided 4,178 LIRs with a /24 allocation:<br>
- 2,019 allocations (48%) went to members with a single LIR account<br>
- 452 allocations (11%) went to members with 2-4 LIR accounts<br>
- 298 allocations (7%) went to members with 5-9 LIR accounts and<br>
- 1,409 allocations (34%) went to members with 10 or more LIR <br>
accounts (up to 33 /24 allocations to a single member)<br>
<br>
This trend towards allocations to multiple LIR accounts has accelerated <br>
in the past six months. Between June and November 2021, only 24% of <br>
allocations went to members with a single LIR account, while 54% went to <br>
members with 10 or more accounts.<br>
<br>
We see the same trend with the current waiting list. At the time of <br>
writing, we can see 327 requests for a /24 allocation:<br>
- 83 (25%) are from members with a single LIR account<br>
- 42 (13%) are from members with 2-4 LIRs accounts<br>
- 45 (14%) are from members with 5-9 LIR accounts<br>
- 157 (48%) are from members with 10 or more LIR accounts<br>
<br>
Consequently, there is a significantly longer wait time for members with <br>
a single LIR account.<br>
<br>
Looking at the current market prices for IPv4 in comparison to our <br>
membership fees, even a wait time of several months is acceptable for <br>
organisations that plan to transfer their allocation after the end of <br>
the holding period. Conversely, the long wait time will create <br>
uncertainty for real newcomers, especially if they can’t rely on <br>
IPv6-only networks.<br>
<br>
I hope the WG finds this information useful for further discussion. If <br>
there is consensus to change the current situation, there are several <br>
approaches available – including a review of the waiting list policy and <br>
changing ‘per LIR’ to something else. Other approaches, such as a <br>
different charging scheme or changing the concept of multiple LIRs would <br>
need to be approved by the RIPE NCC membership.<br>
<br>
Kind regards,<br>
Marco Schmidt<br>
Assistant Manager Registry Services<br>
RIPE NCC<br>
<br>
[1] <a href="https://ripe83.ripe.net/archives/video/642/" rel="noreferrer" target="_blank">https://ripe83.ripe.net/archives/video/642/</a><br>
<br>
<br>
-- <br>
<br>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br>
<br>
<br>
-- <br>
<br>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br>
</blockquote></div>