Search RPD Archives
[rpd] Updated Policy Proposal - IPv6 as a criteria in IPv4 Soft Landing AFPUB-2026-v6-001-DRAFT03
Zenalo Mguqulwa
mguqulwazenalo at gmail.com
Thu Nov 19 17:44:00 UTC 2026
Hi Noah,
I understand your point about allocating IPv4 addresses based on need. My
concern is that even with published criteria, the registry still has to
assess who qualifies. Someone has to decide whether the stated need is
real, and that rewards whoever documents need best (established operators
with the staff and experience to make the case) rather than whoever serves
the most users. In a region where IPv4 space is already unevenly
distributed, we should be careful not to reinforce those inequalities
through the allocation process.
On leasing, I agree that leasing addresses does not automatically mean they
are being used. However, the registry may not always be able to distinguish
between space held for growth, customers or future leasing, and it should
not be asked to supervise business models. Transferability and market
pricing can help move unused addresses towards operators who need them,
without relying entirely on registry assessments.
I believe the better approach is to apply clear, predictable rules, limit
unnecessary discretion and allow IPv4 resources to move towards productive
use.
Zenalo
On Thu, 19 Nov 2026 at 19:03, <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 (Noah)
> 2. Updated Policy Proposal - IPv6 as a criteria in IPv4 Soft
> Landing AFPUB-2026-v6-001-DRAFT03 (NP Petronella)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Nov 2026 19:59:32 +0300
> From: Noah <noah at neo.co.tz>
> To: 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:
> <CAEqgTWbnbREJG3L=
> HkTCN4mK_czvj8rmf3p+eEr7S6BxFSxqVw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Thu, Nov 19, 2026 at 6:15?PM Mike Burns via RPD <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/f46c72b4/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 19 Nov 2026 17:01:39 +0000
> From: NP Petronella <NPertuniaPetronella at outlook.com>
> To: "rpd at afrinic.net" <rpd at afrinic.net>,
> "jordi.palet at theipv6company.com" <jordi.palet at theipv6company.com>
> Subject: [rpd] Updated Policy Proposal - IPv6 as a criteria in IPv4
> Soft Landing AFPUB-2026-v6-001-DRAFT03
> Message-ID:
> <
> VI3PR09MB653902C466F2902E066741A6A0A4792 at VI3PR09MB653902.eurprd09.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi everyone,
>
> I agree with the concerns Owen DeLong and Mike Burns have raised, and I
> oppose AFPUB-2026-v6-001-DRAFT03.
>
> Jordi is right that some networks still need IPv4 ? for NAT64, for
> dual-stack business customers, for bringing a new network into service.
> That need is real, and I do not dismiss it. What I disagree with is the
> remedy: making access to IPv4 depend on an assessment of the applicant's
> IPv6 deployment. IPv4 requests should be assessed on demonstrated need,
> under clear, published and predictable rules.
>
> The central problem is the role this gives AFRINIC. A registry keeps
> records: who holds which number, under which published procedures. It is an
> address book, and an address book is not an instrument of enforcement. This
> proposal would let staff decide whether an operator's IPv6 rollout is good
> enough before issuing an IPv4 allocation. That is a different function: a
> discretionary gate over an operational decision that belongs to the network
> that carries the cost and the risk. What needs coordinating here is
> uniqueness and accurate records, not an operator's IPv6 roadmap.
> Withholding an administrative service in order to change an operator's
> behaviour is not a technical necessity; it is enforcement, and a voluntary
> registry has no authority of that kind. The registry would gain the power
> to refuse and would bear none of the cost of the delay that follows. Rules
> that carry consequences should be made and enforced by bodies that have
> lawful authority to do so.
>
> The thresholds also do not measure what they claim to measure. For access
> networks, the result depends heavily on customer premises equipment and on
> customers' own choices; an operator can enable IPv6 and still fall short
> because subscribers have switched it off. For hosting providers, having
> IPv6 assignments alongside IPv4 space says little about whether services
> are actually reachable, or used, over IPv6. Either way, the metric can be
> satisfied on paper by a network that has not deployed, and failed by a
> network that has.
>
> The proposal also works against the operators already doing the right
> thing. A network running NAT64 is deploying IPv6; it would now need a
> "credible plan" and a retrospective review to obtain the IPv4 it needs to
> keep that service running. Meanwhile, a convincing plan is not evidence of
> deployment. The test selects paperwork, not progress, and it adds cost and
> delay for the operators who have already made the investment.
>
> On brokers, smaller allocations do not touch the underlying incentive: the
> gap between the administrative cost of registry space and its market value.
> Smaller blocks do not create more addresses. They create more applications,
> more queue position and more discretion over who is served, which rewards
> those best able to work the process and pushes operators with genuine need
> into transfers. Mike is right that AFRINIC-issued space cannot simply leave
> the region ? outbound inter-regional transfers are not available except for
> legacy space, or space previously transferred in, and that limited policy
> has not been implemented ? and that addresses should go to those who need
> them. Owen is right that the remaining pool should be allowed to run out,
> as pools have elsewhere, rather than being prolonged with further
> conditions.
>
> IPv4 should not be the instrument for IPV6 deployment, and holding IPv4
> hostage to an IPv6 scorecard will not produce deployment. It produces
> permission, delay and dependence ? and the operator, not the registry, pays
> for the delay. If we want more IPv6, measure it, train for it and reward
> it, on its own merits and with its own impact assessment. That is a
> separate piece of work. It should not be the price of an IPv4 allocation.
>
> Oppose as drafted.
>
> Nonhlanhla
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20261119/ea49877a/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 32
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20261119/3c480c51/attachment-0001.html>
More information about the RPD
mailing list