<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
No comment from my side regarding the staff issue — such things happen everywhere. What really matters is how we deal with these situations.</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
On another note, don’t forget: the early worm gets eaten.</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
So, be the bird if you must be early — not the worm. 😉</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Sami Salih.</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div id="ms-outlook-mobile-body-separator-line" data-applydefaultfontstyles="true" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;" dir="auto">
<br>
</div>
<div style="font-family:Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif;font-size:12pt" dir="auto" id="ms-outlook-mobile-signature">
</div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg" style="font-size: 11pt;" dir="auto"><b>From:</b> Owen DeLong <owen@delong.com><br>
<b>Sent:</b> Thursday, October 16, 2025 6:19:58 am<br>
<b>To:</b> Sami Salih <sami.salih@outlook.com><br>
<b>Cc:</b> jordi.palet@consulintel.es <jordi.palet@consulintel.es>; RPD <rpd@afrinic.net><br>
<b>Subject:</b> Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate<br>
</div>
<br>
<br>
<div dir="auto"><br>
</div>
<blockquote>
<div dir="auto">On Oct 15, 2025, at 10:11, Sami Salih <sami.salih@outlook.com> wrote:</div>
<br>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
In such a complex situation, there are certainly more possibilities than the two you’ve outlined.</div>
<div style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Moving forward, I believe we can build a constructive dialogue if we agree on a few key principles:</div>
<div style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
1. The African context is fundamentally different from that of the global north, so we can’t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious.</div>
</blockquote>
<div dir="auto"><br>
</div>
Less so than most perceive it to be, but yes, to some extent.
<div dir="auto"><br>
</div>
<blockquote>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
2. It’s essential to use available resources wisely, neither reserving large unused blocks nor rushing to exhaust them is a sustainable strategy.</div>
</blockquote>
<div dir="auto"><br>
</div>
The first part, I completely agree with. As to exhaustion, I’d have a great deal of difficulty calling exhausting IPv4 in AFRINIC tomorrow a “rush” at this point. Global IPv4 RIR exhaustion in the other 4 RIRs (note this is not just the global north, all 4,
at least two of which have significant populations south of the equator) exhaustion occurred several years ago.
<div dir="auto"><br>
</div>
<blockquote>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
3. The current statistics already reveal some noticeable imbalances, which suggests we shouldn’t continue in the same direction without adjustment.</div>
</blockquote>
<div dir="auto"><br>
</div>
I guess that depends on what you consider balanced and to what extent you think that resource allocations for IPv4 addresses should be balanced. I will note that if you go to the store on a day when they have a limited supply of $X, the first people to get
there can generally buy $X and those who show up late generally cannot. Most people don’t call this unfair, they just call it “The early bird gets the worm.”
<div dir="auto"><br>
</div>
<div dir="auto">I’m not saying there should or should not be changes in how resource allocations within the AFRINIC service region are balanced, I have no dog in that particular fight. I am, however, saying that from a global perspective and for AFRINIC in
particular, the continuing existence of the IPv4 tree pool is problematic in a number of ways and the longer it sits there, the more of an incentive it will create for fraud, mismanagement, graft, and corruption.</div>
<div dir="auto"><br>
</div>
<blockquote>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
For me, I believe, we don’t yet have a real good need to free the reserved block, but I’m open to discussing any policy proposal that presents a genuine use case to utilize a logical portion of it.</div>
</blockquote>
<div dir="auto"><br>
</div>
See above. The use case is the same as prior legitimate allocations under policy as it existed before global exhaustion.
<div dir="auto"><br>
</div>
<blockquote>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
And to be clear, the staff are doing an excellent job within the framework provided, howver the discussion here is about broader structural issues, not their performance.</div>
</blockquote>
<div dir="auto"><br>
</div>
I think it’s a bit of both. There is definitely a history of staff issuing resources that should not have been issued even under the framework as it existed. I do not know to what extent this conduct has continued or not and I’m not making any accusations.
I am merely stating historic fact here. Certainly some of the staff that remains in registration services are among those who knew or should have known that the fraud was occurring right under their noses and failed to take any effective action at the time.
<div dir="auto"><br>
</div>
<div dir="auto">Owen</div>
<div dir="auto"><br>
</div>
<br>
<br>
</div>
</body>
</html>