<div dir="ltr"><div dir="auto"><div dir="auto"><div><div>Hi Jaco,</div></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 6:44 pm Jaco Kroon via RPD, <<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<p>Simply put:<br>
<br>
AFRINIC as RIR may not make operational decisions without relevant
POLICY controlled by community. </p></div></blockquote></div></div></div><div dir="auto"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p> </p></div></blockquote></div></div><div dir="auto">Some operational decisions do not require policy because they fall within the mandate of AFRINIC internal operations, such as paying for software licenses or infrastructure upgrades.</div><div dir="auto">For policies related to INR, the bottom-up process has always been employed, consistent with the spirit of internet governance principles enshrined in our bylaws, to produce policies that support the registry's governance and operations. However, </div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>As such, if AFRINIC were to
implement contemplated restrictions (by way of operational choice)
without relevant policy, they'd be acting outside of their
mandate.<br></p></div></blockquote></div></div></div><div dir="auto"></div><div dir="auto"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p></p></div></blockquote></div></div><div dir="auto">In 2020, we voted for some amendments to the Bylaws and resource members empowered the AFRINIC board/directors with certain powers. They can exercise these powers regarding policy adoption by invoking Articles 11.4 and 11.5 of the Bylaws at the next PPM...</div><div dir="auto"><br></div><div dir="auto">That being said, top down policy adoption is already in place, as long as we rubber-stamp the said policy....</div><div dir="auto"><br></div><div dir="auto">Ahsante..</div><div dir="auto">Noah</div><div dir="auto"><br></div></div></div>
</div>