<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi and tks again,<div><br></div><div>I see your point that seems to easy, but we shall remember that you need to demonstrate the need to Afrinic *every time* you do a request. So if you say, I will build not 1 but 3 DCs, you will need to show contracts, right?</div><div><br></div><div>Is the same as when you request a bigger address block than what policies dictate, you need to justify the need, have network diagrams, etc.. If you need to deploy 4 NAT64 PoPs, you need to show the contracts, even the invoices for the NAT64 boxes, etc.</div><div><br></div><div>All that are operational details, with don’t go into policy text. We want to avoid micromanagement of the RIR as much as possible, only got into the details if they are going to (clearly) do it wrong (or done wrong already previously).</div><div><br></div><div>If a request for 4 /24 for 4 NAT64 PoPs is fraudulent, the service agreement already enable Afrinic to review that and reclaim the space. I don’t think in general, people want to break rules on purpose.</div><div><br></div><div>Also I think asking for demonstrating that it can’t be done with renumbering is too expensive (just the exercise to analyze is it often a big hurdle), renumbering is extremely hard, and imposing this may go against some IPv6 deployments “the deployment cost me x and also I need to check if I can do it with renumbering first, then I just do with the renumbering, at least for some time”.</div><div><br></div><div><div>****** Now, if the staff believes that they need some explicit text to demonstrate the need, please say so before the policy proposal submission deadline, because in that case, we still have time to incorporate that text into a v2.</div></div><div><br></div><div>May be something such as:</div><div><br></div><div>“<span style="color: rgb(209, 94, 20); font-family: -apple-system, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; background-color: rgb(255, 255, 255);">The above requirement is waived for network operators requesting new IP addresses for </span>demonstrated<span style="color: rgb(209, 94, 20); font-family: -apple-system, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; background-color: rgb(255, 255, 255);"> key technical needs – such as redundancy and high-availability sites, IPv6 transition technologies, or expansion to new sites which pose a technical constraint on their current resource pool – and in these cases, the request is treated as a first allocation or request.</span>"</div><div><br></div><div>Repeating myself:</div><div>I think overall, this way to approach what do to with the recovered space helps Africa to improve Internet penetration tied to IPv6 deployment, specially because dual-stack is not longer possible, so this helps IPv6 + IPv4aaS, so it is clearly in support of IPv6 deployment.</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br><br></div>
</div>
<div><br><blockquote type="cite"><div>El 21 may 2026, a las 16:03, Jaco Kroon <jaco@uls.co.za> escribió:</div><br class="Apple-interchange-newline"><div><div>Hi Jordi,<br><br>In principle in support, this could potentially have helped me a few years back to avoid nasty renumbering.<br><br>Having said that, I think this becomes a bit too lenient. Must be "where it can be shown that the new requirement cannot practically be served by existing resources", so in your case where you have four POPs each needing to originate it's own /24, you will require extra resources to set up a fifth POP. The counter argument would be "but you can use /25s internally and just advertise >=/24s to the outside world" - but this would result in sub-optimal routing which is where I stand with you.<br><br>I just think the wording as is could potentially be abused and I'd like to see it a bit more strict in the sense that it must be shown that even with renumbering it cannot be accommodated from existing resources.<br><br>I like that you mention examples, and some of them definitely tickled my curiosity as to why you'd need IPv4 to achieve that, but I don't think that matters, except that these could potentially be used to obtain additional resources prematurely and I'd like a requirement that it must be shown that the current allocations/assignments cannot be utilised to fulfil the technical requirements.<br><br>Kind regards,<br>Jac<br><br><br>On 2026/05/21 15:28, jordi.palet--- via RPD wrote:<br><blockquote type="cite">Hi all,<br><br>This proposal, continuing with the idea of resolving the issues that have been discovered by the staff, is attempting to fix the problem of operators that need additional resources for redundancy, new sites (for example data centers), or even transition technologies.<br><br>The actual soft landing proposal doesn’t cover those cases and only allows obtaining additional resources when 90% of utilizations is reached.<br><br>Of course, I think is clear for all, that you don’t setup a data-center or other kinds of redundancy when your 1st data center is almost full, you actually want to have them being built even at the same time.<br><br>Similarly when you, for example, want to deploy 464XLAT, and you have 4 PoPs where you will locate the NAT64 boxes, you will need some free IPv4 pools (for example 1x/24 and each POP), and you want to do that in all the PoPs, not one, wait for 90% utilization, then the next one, etc., because you want to make sure to provide high-availability. This is a very clear case for me, in my day-job deploying IPv6-only with IPv4-as-a-Service worldwide.<br><br>This is easily achieved by waiving those requests from the 90% utilization and considering them as a “first request” (in fact, it is a first request for a new site).<br><br>The advantage for Afrinic, compared with other RIRs, is that we have recovered 3 millions of IPv4 addresses, so multiple sites allocations for every member, doesn’t mean draining earlier than expected the available pool when we entered in soft landing phases.<br><br>Comments welcome!<br><br>Tks!<br><br>Regards,<br>Jordi<br><br>@jordipalet<br><br><br><blockquote type="cite">El 15 may 2026, a las 17:51, dacostadarwin@gmail.com escribió:<br><br>Dear PDWG,<br><br>We have received a new draft policy proposal - Amendment of Utilisation in Soft Landing, ID AFPUB-2026-IPv4-002-DRAFT01 from author Jordi Palet Martinez. The proposal contents are published at:<br><br>https://afrinic.net/policy/proposals/afpub-2026-ipv4-002-draft01<br><br>We encourage you to take some time to go through the proposal contents and provide feedback as follows :<br><br>a) Do you support or oppose the proposal?<br>b) If you oppose the proposal, state your reasons?<br>c) Is there anything in the proposal that is not clear?<br>d) What changes could be made to this proposal to make it more effective?<br><br>Regards,<br>Vincent Ngundi & Darwin Da Costa<br>AFRINIC PDWG Co-Chairs<br><br><br>_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<br></blockquote><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br>http://www.theipv6company.com<br>The IPv6 Company<br><br>This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br><br><br><br><br>_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<br></blockquote><br>_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<br></div></div></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>