[Community-Discuss] Notice to all the legacy netblocks holders        in AfriNIC

Wijdane Goubi wijdan.goubi at gmail.com
Fri Feb 12 17:06:34 UTC 2021

Hello Jordi,

So the thing is that, since all of the 5 RIRs have transfer policies
(regardless whether they are intraRIR or interRIR), and since no one has
ever applied space for transfer in the history of RIR, then by the very
definition of the transfer policy, the change of purpose is allowed. If in
some region there is some old and obsolete policy text that forbids change
of purpose for usage, then those should be considered invalid because they
are directly contradicting the newer policy text (transfer policy). Also,
while a proper policy update is preferred in those situations, it is not
necessary, since the later policy text always wins over the old one, as the
newer one represents better the current community needs and wishes.

Besides, change of purpose for usage is allowed in the current AFRINIC
policy text. There is not even an obsolete old policy text in AFRINIC’s CPM
that prevents LIR making their assignment for a different purpose, it only
mentions the sub-allocation, which is a totally different thing. So
basically, change of purpose for usage is always allowed in the AFRINIC

In fact, the design of IP address policy did have the change of purpose in
mind, that is the very reason why we have two distinct definitions of
"allocation" and "assignment", LIR gets allocation, then makes assignment
for each specific user case, while the allocation is for general purpose,
and you need to make the assignment inside the allocation for each user
case to the end users. The Allocation stays with LIR, while the Assignment
comes and goes as the user case existed or not. If change of purpose is not
allowed, then there is absolutely no reason to distinguish them. AFRINIC
should make assignment to each LIR then evaluate every time the user case
changes which is quite impossible and impractical. As an example, if I made
/23 for one web hosting customer and then the customer leaves, I will need
to go through an entire application process again just because the same
server goes to a VPN customer, and this doesn’t happen anywhere in the
world, and currently not with AFRINIC. *Allowing LIR to freely manage its
space usage within the allocation is the very core design of IP address

Moreover, this is the exact reason why RSA is so badly written and
shouldn't contain any resource management clause. The lawyers do not
understand the very concept of Allocation and Assignment, let alone
distinguishing between them. Therefore, allowing lawyers texts to manage
community resources is not only illegitimate, but also lacks of needed
technical understanding of addressing to properly write it, that is why we
now have an RSA which is full of invalid IP management clauses and
contradiction to the policy itself, which needs to be fixed at some point
of time. Not to mention that allowing lawyers to manage the resources
defies the very foundation of the bottom up process.

Le jeu. 11 févr. 2021 à 20:34, JORDI PALET MARTINEZ via Community-Discuss <
community-discuss at afrinic.net> a écrit :

> Hi Widjane,




> I agree with you in some of the points, but not in all them.




> 1. Policies among the RIRs aren’t exactly the same. They tend to

> converge with the time, but not always are 100% the same.

> 2. In fact, in some RIRs, right now, if you asked for resources and

> provided documents about what will be the usage and you change usage,

> you’re under lack of compliance. Note that we aren’t talking about business

> grow. For example, a very simple on, let’s suppose you got resources for an

> organization (assigned resources) and now you want to provide Internet

> services to others, that will be against policies, in all the RIRs. Another

> example, if you got resources in some RIRs you can’t use them to provide

> services outside of that region (at all, example AFRINIC, or depending on

> the % example LACNIC, it depends on the RIR).

> 3. I can agree with your that this is not right in many situations and

> policy should allow it. However, there are technical issues about allowing

> that freely, not just policy issues (and sometimes the policy issues, in

> fact, happen because technical issues).

> 4. AFRINIC is the only RIR, at the time being, that has not adopted

> (ratified and even less implemented) a policy proposal for Inter-RIR

> transfers. However, even in most of the RIRs, the allowed transfers are

> only for IPv4.

> 5. I will love that we could make policy changes in a more dynamic

> way, but specially in AFRINIC, it is being too slow.




> Regards,


> Jordi


> @jordipalet








> El 11/2/21 20:01, "Wijdane Goubi" <wijdan.goubi at gmail.com> escribió:




> Dear community,


> Technically speaking, if a change of the nature is not allowed (as claimed

> by some) this doesn’t make any technical sense at all as there are

> consensus among several RIRs to allow inter RIR transfer and also allows

> intra RIR transfers.


> The logic adopted that the change of nature is not permitted doesn’t sit

> well with the established sections of the policies adopted and used. In

> fact, the logic will bar and limit the ability for an organization to grow

> and expend its services.


> This imposition will also burden the member to go through unnecessary

> bureaucratic demands and expectations whereas the matter could easily be

> resolved. The policy and understanding of business nature needs to be as

> dynamic as the internet is!


> The internet grows and evolves from one form to another, so should the

> policy.

> In fact, RIR never bothers or care with how the space is being used for.


> A post from years ago (

> https://lists.afrinic.net/pipermail/rpd/2017/007222.html ), from both

> ARIN and RIPE explained that once the space is issued, their only concern

> is to ensure accurate registration.


> The video and the section where both ARIN and RIPE NCC are speaking can be

> found on the following link:

> https://youtu.be/XBv44KAgFVQlist=PLLJRUWAm1GCZAGzqiCzX2CRU7oqLDC9e5


> At or around 08:27:50, Andrea Cima from RIPE NCC explains that their

> reviews are called “ARC”, and it is to keep in touch and keep the data up

> to data, registry data, that is the contact details and so on.

> Investigation, that is the part of the “fraud”.


> Whereas, at or around 08:29:50, Leslie from ARIN explains the scope of

> their policy, they only audit in fraud cases and only deregister in case of

> fraud.


> Neither the RIPE NCC or ARIN does a re-evaluation of the resources and

> questions on how the LIRs are currently using their resources.


> There is a global consensus on how spaces are being used currently—as long

> as the allocation process was justified and registration is actual, RIR

> does not care about its current usage.


> _______________________________________________ Community-Discuss mailing

> list Community-Discuss at afrinic.net

> https://lists.afrinic.net/mailman/listinfo/community-discuss


> **********************************************

> IPv4 is over

> Are you ready for the new Internet ?

> http://www.theipv6company.com

> The IPv6 Company


> 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.


> _______________________________________________

> Community-Discuss mailing list

> Community-Discuss at afrinic.net

> https://lists.afrinic.net/mailman/listinfo/community-discuss


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20210212/3e40faba/attachment.html>

More information about the Community-Discuss mailing list