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