<div dir="auto"><p>Dear colleagues,</p>
<p>I support the points raised by Jordi, Seun and Frank about allowing policy authors to also serve as co-chairs.</p>
<p>I don't think someone should have to stop contributing to policy discussions simply because they have taken on a co-chair role. Being involved in writing a policy does not automatically mean that someone cannot be fair when helping to manage the discussion.</p>
<p>I do, however, believe there should be clear guidelines to manage situations where a conflict of interest may arise. For example, if a co-chair has contributed to a particular proposal, they can still share their views and explain their position, but should allow the other co-chair to lead that specific discussion.</p>
<p>I also think the requirements for becoming a co-chair should be clear and fair. Terms like maturity should not be left open to personal interpretation, as this could make the selection process unfair.</p>
<p>We should be creating an environment where people are encouraged to participate and contribute their experience, rather than putting unnecessary restrictions in place.</p>
<p>For me, the most important things are fairness, transparency and giving everyone a reasonable opportunity to participate.</p>
<p>Regards,<br>
Fundiswa Nadia Maseko </p></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 20 Nov 2026, 09:12 , <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Updated Policy Proposal ? IPv6 as a Criteria in IPv4 Soft<br>
Landing ? AFPUB-2026-v6-001-DRAFT03 (Fundiswa Nadia Maseko)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 20 Nov 2026 09:11:11 +0200<br>
From: Fundiswa Nadia Maseko <<a href="mailto:fundiswanadia2@gmail.com" target="_blank" rel="noreferrer">fundiswanadia2@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] Updated Policy Proposal ? IPv6 as a Criteria in<br>
IPv4 Soft Landing ? AFPUB-2026-v6-001-DRAFT03<br>
Message-ID:<br>
<<a href="mailto:CABV0QcT9-QZuHk9XS9yuX1s9NMupZTgQGaMnAHVHtmD9_2OXfQ@mail.gmail.com" target="_blank" rel="noreferrer">CABV0QcT9-QZuHk9XS9yuX1s9NMupZTgQGaMnAHVHtmD9_2OXfQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear colleagues,<br>
<br>
I would like to express my opposition to AFPUB-2026-v6-001-DRAFT03.<br>
<br>
I understand the importance of encouraging IPv6 adoption, and I believe it<br>
is something the industry should continue working towards. However, I am<br>
concerned about making IPv4 allocations dependent on how much IPv6<br>
deployment a member can demonstrate.<br>
<br>
My concern is that this approach may not always reflect what is happening<br>
in practice. Network operators can make IPv6 available and have the<br>
necessary infrastructure in place, but the actual adoption also depends on<br>
customers, their devices and how they use the services provided.<br>
<br>
I also think we need to be careful about introducing requirements that<br>
could unfairly affect existing members who already hold IPv6 resources but<br>
are now being assessed against additional conditions when requesting IPv4<br>
space.<br>
<br>
AFRINIC's policies should be clear, fair and practical to apply. I believe<br>
IPv4 requests should continue to be assessed based on demonstrated need and<br>
established allocation criteria, rather than percentages that may not<br>
accurately reflect an operator's actual efforts or capabilities.<br>
<br>
If IPv6 readiness is going to be a requirement, then the policy should<br>
focus on what the network operator can reasonably control, such as having<br>
IPv6 infrastructure in place and making IPv6 connectivity available to<br>
customers.<br>
<br>
I support the growth of IPv6, but I do not believe that restricting access<br>
to IPv4 resources in this way is the right approach.<br>
<br>
Regards,<br>
Fundiswa Nadia Maseko<br>
<br>
On Fri, 20 Nov 2026, 00:56 , <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> wrote:<br>
<br>
> Send RPD mailing list submissions to<br>
> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of RPD digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. PIER presentation from yesterday (<a href="mailto:jordi.palet@theipv6company.com" target="_blank" rel="noreferrer">jordi.palet@theipv6company.com</a>)<br>
> 2. Re: Updated Policy Proposal - IPv6 as a criteria in IPv4 Soft<br>
> Landing AFPUB-2026-v6-001-DRAFT03 (Mike Burns)<br>
> 3. Re: New draft policy proposal PPM Dates<br>
> AFPUB-2026-GEN-003-DRAFT01 (Owen DeLong)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Thu, 19 Nov 2026 20:01:48 +0100<br>
> From: "<a href="mailto:jordi.palet@theipv6company.com" target="_blank" rel="noreferrer">jordi.palet@theipv6company.com</a>"<br>
> <<a href="mailto:jordi.palet@theipv6company.com" target="_blank" rel="noreferrer">jordi.palet@theipv6company.com</a>><br>
> To: rpd List <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> Subject: [rpd] PIER presentation from yesterday<br>
> Message-ID: <<a href="mailto:1D9A8BE3-B5DB-48C9-B3BB-92D92F5F8ACA@theipv6company.com" target="_blank" rel="noreferrer">1D9A8BE3-B5DB-48C9-B3BB-92D92F5F8ACA@theipv6company.com</a>><br>
> Content-Type: text/plain; charset=utf-8<br>
><br>
> Hi all,<br>
><br>
> Looking at the PIER slides from yesterday.<br>
><br>
> 1. ASN Eligibility<br>
><br>
> The problem seems to me the text in 7.2. It should be shortened to allow<br>
> non-members to get ASNs, *if we want to keep 7.4*.<br>
><br>
> So ?In order to qualify for an AS number, the requesting entity must<br>
> fulfil any of the following requirements?.<br>
><br>
> This way we:<br>
> 1) Avoid conflict with 7.4<br>
> 2) Replacing organization with ?entity? allows non-organizations that may<br>
> also require an ASN.<br>
><br>
> A different discussion is why 7.4 has the text ?and non-members?. I fail<br>
> to recall if that was on purpose of this, or was left from other policy<br>
> changes and we lost track of that. Both LIRs and end-users (non-LIRs) are<br>
> very clear.<br>
><br>
> Could the staff identify if there are cases of non-members ? In the fees<br>
> table, I can?t see how this is invoiced.<br>
><br>
> If ?non-members? was left from previous proposal changes, in addition to<br>
> the change suggested for the 7.2, we shall remove ?and non-members?.<br>
><br>
> In fact, I may be in part ?responsible" (with the community consensus) of<br>
> this mistake in 7.2, as I believe the actual text comes from my policy<br>
> proposal AFPUB-2019-ASN-001-DRAFT04 - Multihoming not required for ASN. I<br>
> can?t find a way for finding the previous CPM versions, and the policy<br>
> archive also doesn?t help, because it doesn?t clarify if a proposal reached<br>
> consensus, what CPM version implemented it, etc. I believe I overlooked<br>
> section 7.4 of the CPM (which had a different numbering on that time or<br>
> maybe this was added later?), because what today is 7.2 was 7.4 and we had<br>
> this text there "7.4.4 Be an AFRINIC member in a good standing (End-User or<br>
> LIR type)?, so I just rephrased it to shorten the text, allow obtaining<br>
> ASNs even if there is no multihoming (that was the main proposal intent)<br>
> and we all (staff and community) missed the sections after 7.4.<br>
><br>
> Could the staff provide a link to previous CPM versions?<br>
><br>
> 2. IPv6 Rectification<br>
><br>
> I proposed first the rectification for IPv6 PA, and then in a different<br>
> proposal for IPv6 PI, as I noticed the same problem because members were<br>
> getting the default prefix size without doing a proper addressing plan (it<br>
> happened also in other RIRs, so I did the same in several of them).<br>
><br>
> This comes from another of my policy proposals ?IPv6 PI Update?, which<br>
> unfortunately can?t find the correct text in the AFRINIC web site. It will<br>
> be nice if the staff can correct the links which seem to be broken or bring<br>
> to nowhere. I can see the emails with the discussion, and when Sami and<br>
> Dewole declared consensus and sent it to the board for ratification, etc.<br>
><br>
> In any case, in my own archives I?ve the text that reached consensus<br>
> (relevant part):<br>
><br>
> AFPUB-2018-V6-004-DRAFT01 - "receive a new block with the new requested<br>
> prefix size, with the commitment to renumber its network and return the<br>
> original block within a period of 6 months;"<br>
><br>
> So both the PA and PI were matching in a 6-months period for the return of<br>
> the previous prefix.<br>
><br>
> However, we overlooked something and we updated it by means of<br>
> "AFPUB-2019-V6-001-DRAFT02: IPv6 PI Clarification?. As part of this change<br>
> the community discussed the 6 months return for the case of IPv6 PI (we<br>
> will need to dig into the mailing list archive for understanding the<br>
> point), and the conclusion was (I believe this is the reason for v2, can?t<br>
> check it because lack of archive in the web site, neither can see the staff<br>
> IA for v1), we agreed to change this *on purpose*:<br>
><br>
> from:<br>
> Receive a new block with the new requested prefix size, with the<br>
> commitment to renumber its network and return the original block within a<br>
> period of 6 months<br>
><br>
> to:<br>
> Receive a new block with the new requested prefix size, with the agreement<br>
> to utilize the new block for all future deployment and deprecate the old<br>
> block through attrition, returning when empty. There is no deadline for<br>
> return at this time<br>
><br>
> So, in conclusion, this was done on purpose! I don?t agree with the slide<br>
> of the staff that indicate that this creates a difference between PA and PI<br>
> holders, because it is a different type of IPv6 prefix, so they aren?t<br>
> members in the ?same? situation.<br>
><br>
> Of course, if the community changed his mind and believes that we should<br>
> have a deadline for the return of the old prefix, I will suggest to change<br>
> it for both the IPv6 PA and IPv6 PI to 12 months, as in my experience this<br>
> worked better in several RIRs where I had the same proposal reaching<br>
> consensus.<br>
><br>
><br>
> 3. Multi-site End-User PI: Multi-country Challenge<br>
><br>
> This is how I see this by means of an example. An end-user has multiple<br>
> locations, in multiple countries. They request, for example a /44, but each<br>
> end-site-location uses a /48. At least this was the intent of the policy<br>
> change (also same proposals as those that I mention in 2 above).<br>
><br>
> What we are missing is that in the case of the IPv6 PA, we have explicit<br>
> requirements for whois registration. However in IPv6 PI we don?t have that.<br>
> I believe if we explicitly indicate that each /48 for each end-site<br>
> location must be registered, that will be fixed.<br>
><br>
> Could the staff clarify if this is the problem or if not, with examples<br>
> how they see it? Also if the problem I described is the right one, if they<br>
> agree that ensuring that each end-site location is correctly registered<br>
> will solve the problem?<br>
><br>
> Regards,<br>
> Jordi<br>
><br>
> @jordipalet<br>
><br>
><br>
> **********************************************<br>
> IPv4 is over<br>
> Are you ready for the new Internet ?<br>
> <a href="http://www.theipv6company.com" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com</a><br>
> The IPv6 Company<br>
><br>
> This electronic message contains information which may be privileged or<br>
> confidential. The information is intended to be for the exclusive use of<br>
> the individual(s) named above and further non-explicilty authorized<br>
> disclosure, copying, distribution or use of the contents of this<br>
> information, even if partially, including attached files, is strictly<br>
> prohibited and will be considered a criminal offense. If you are not the<br>
> intended recipient be aware that any disclosure, copying, distribution or<br>
> use of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited, will be considered a criminal<br>
> offense, so you must reply to the original sender to inform about this<br>
> communication and delete it.<br>
><br>
><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Thu, 19 Nov 2026 17:10:11 -0500<br>
> From: "Mike Burns" <<a href="mailto:mike@sum.net" target="_blank" rel="noreferrer">mike@sum.net</a>><br>
> To: "'Noah'" <<a href="mailto:noah@neo.co.tz" target="_blank" rel="noreferrer">noah@neo.co.tz</a>>, "'Mike Burns'" <<a href="mailto:mike@iptrading.com" target="_blank" rel="noreferrer">mike@iptrading.com</a>><br>
> Cc: 'rpd List' <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> Subject: Re: [rpd] Updated Policy Proposal - IPv6 as a criteria in<br>
> IPv4 Soft Landing AFPUB-2026-v6-001-DRAFT03<br>
> Message-ID: <01ee01dd7872$bf3bb8f0$3db32ad0$@<a href="http://sum.net" rel="noreferrer noreferrer" target="_blank">sum.net</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Hi Noah,<br>
><br>
><br>
><br>
> I said nothing about need at all, except to point out that these addresses<br>
> should go to<br>
> African networks who have a justified need for them.<br>
><br>
><br>
><br>
> And that the benefit to them is direct and plain, unlike the claim that<br>
> brokers would be the beneficiaries.<br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Mike<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> From: Noah <<a href="mailto:noah@neo.co.tz" target="_blank" rel="noreferrer">noah@neo.co.tz</a>><br>
> Sent: Thursday, November 19, 2026 12:00 PM<br>
> To: Mike Burns <<a href="mailto:mike@iptrading.com" target="_blank" rel="noreferrer">mike@iptrading.com</a>><br>
> Cc: <a href="mailto:jordi.palet@theipv6company.com" target="_blank" rel="noreferrer">jordi.palet@theipv6company.com</a>; rpd List <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> Subject: Re: [rpd] Updated Policy Proposal - IPv6 as a criteria in IPv4<br>
> Soft Landing AFPUB-2026-v6-001-DRAFT03<br>
><br>
><br>
><br>
><br>
><br>
> On Thu, Nov 19, 2026 at 6:15?PM Mike Burns via RPD <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>> > wrote:<br>
><br>
> Hi Jordi,<br>
><br>
><br>
><br>
> You wrote:<br>
><br>
> ?If we allow releasing the addresses in big chunks probably the<br>
> beneficiaries will be the brokers, which means that the community lose<br>
> resources (specially newcomers or those that still didn?t started the<br>
> transition), too soon, and they will need to pay much more by means of<br>
> transfers?<br>
><br>
><br>
><br>
> I have not followed this policy closely, so I may be missing something,<br>
> but I don?t understand the logic of your sentence. Addresses go to those in<br>
> need, not to brokers. And these addresses are not able to leave AFRINIC, as<br>
> outbound inter-regional transfers are not permitted unless the addresses<br>
> are legacy, or were in the past transferred into AFRINIC from another RIR.<br>
> And currently, even that limited inter-regional transfer policy has not<br>
> been implemented.<br>
><br>
><br>
><br>
> So help me understand how larger block allocations will somehow benefit<br>
> brokers more than the networks who have demonstrated a need for them.<br>
><br>
> You seem willing to only offer a small allocation to those who need more,<br>
> and thus would force them to go to the market to meet their demonstrated<br>
> need.<br>
><br>
><br>
><br>
> Mike<br>
><br>
><br>
><br>
> A regional internet registry in case of IPv4 addresses has to first a<br>
> foremost ensure that it allocates the finite IPv4 addresses based on need.<br>
><br>
><br>
><br>
> Based-on-need does not mean, that, the RIR just issues large blocks of<br>
> IPv4 addresses anyhow for example to a single entity which then goes around<br>
> years later looking for those who need those finite addresses during period<br>
> of scarcity to lease them out or brokerage the addresses for fee. Based on<br>
> need meant, you get addresses and use them on real networks to provide open<br>
> protocol internet services.<br>
><br>
><br>
><br>
> While some large parts of the Africa's region, as in countries, fall under<br>
> what Ben refers to as IP address poverty line, there are entities hording<br>
> large blocks of IPv4 addresses proudly.<br>
><br>
><br>
><br>
> In-fact the RIR's are meant to be stewards.<br>
><br>
> Managers of need based IP address allocation especially for our case in<br>
> Africa.<br>
><br>
> And also act with a great sense of responsibility, care and foresight.<br>
><br>
><br>
><br>
> Countries and their operators are planning to deploy IPv6 and they hardly<br>
> have any IPv4 addresses for translators. We look at the west and see<br>
> successful IPv6 adoption, but this success is supported by IPv4 address as<br>
> well.<br>
><br>
><br>
><br>
> Noah<br>
><br>
> [1]<br>
> <a href="https://www.digitaleconomy.ke/post/ipv4-address-allocation-in-africa-are-you-above-or-below-the-ip-address-poverty-line" rel="noreferrer noreferrer" target="_blank">https://www.digitaleconomy.ke/post/ipv4-address-allocation-in-africa-are-you-above-or-below-the-ip-address-poverty-line</a><br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20261119/99fb654c/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20261119/99fb654c/attachment-0001.html</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Thu, 19 Nov 2026 14:55:03 -0800<br>
> From: Owen DeLong <<a href="mailto:owen@delong.com" target="_blank" rel="noreferrer">owen@delong.com</a>><br>
> To: "<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
> Cc: rpd List <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> Subject: Re: [rpd] New draft policy proposal PPM Dates<br>
> AFPUB-2026-GEN-003-DRAFT01<br>
> Message-ID: <<a href="mailto:8F9F816A-417C-45E5-8DF0-6F57033CE4B5@delong.com" target="_blank" rel="noreferrer">8F9F816A-417C-45E5-8DF0-6F57033CE4B5@delong.com</a>><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20261119/8254efed/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20261119/8254efed/attachment.html</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of RPD Digest, Vol 226, Issue 35<br>
> ************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20261120/60ba95e3/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20261120/60ba95e3/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 226, Issue 37<br>
************************************<br>
</blockquote></div>