<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 30, 2021, at 18:00 , Rubens Kuhl <<a href="mailto:rubensk@gmail.com" class="">rubensk@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">AFRINIC approves IPv4 for the purpose of leasing every day. It’s what ISPs do. It’s the definition of an LIR.<br class=""><br class="">Yes, most LIRs are also in the connectivity business and provide addresses (mostly/exclusively) to customers of their connectivity services.<br class=""></blockquote><br class="">Which is why CI informed AfriNIC in their request that they were going<br class="">to have no network and provide connectivity-less services to CI<br class="">customers, right ?<br class=""><br class=""><blockquote type="cite" class="">However, there’s no such policy requirement in the AFRINIC governing documents.<br class=""></blockquote><br class="">All RIRs were subject to RFC 2050, now RFC 7020, which states:<br class="">"1) Allocation Pool Management: Due to the fixed lengths of IP<br class=""> addresses and AS numbers, the pools from which these resources<br class=""> are allocated are finite. As such, allocations must be made in<br class=""> accordance with the operational needs of those running the<br class=""> networks that make use of these number resources and by taking<br class=""> into consideration pool limitations at the time of allocation."<br class=""><br class="">If there is no network, there is no use of such number resources.<br class=""><br class=""></div></div></blockquote><div><br class=""></div>This is a clear misreading of RFC-2050 and later RFC-7020.</div><div><br class=""></div><div>No RIR is subject to them. They are purported to, I quote:</div><div><br class=""></div><div><pre style="font-size: 13.333333015441895px; margin-top: 0px; margin-bottom: 0px;" class=""> This document provides information about the current Internet Numbers
Registry System used in the distribution of globally unique Internet
Protocol (IP) address space and autonomous system (AS) numbers.
This document also provides information about the processes for
further evolution of the Internet Numbers Registry System.
This document replaces <a href="https://datatracker.ietf.org/doc/html/rfc2050" class="">RFC 2050</a>.
This document does not propose any changes to the current Internet
Numbers Registry System. Rather, it documents the Internet Numbers
Registry System as it works today.
</pre><div class=""><br class=""></div><div class="">As such, errata notwithstanding (for example, it misleadingly claims that multi-regional entities interact</div><div class="">with multiple RIRs which is only sometimes true), RFC-7020 can’t be cited as imposing any rules</div><div class="">upon RIRs and any case where its content differs from current reality represents errata in the RFC and</div><div class="">not misconduct by the RIR or its members or customers.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""></div></div></body></html>