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 12:59:12 UTC 2026
Good day,
I agree with Owen's main point, and I think your examples actually help
explain why.
A /24 for each NAT64 cluster is a genuine operational need. But if a
network is already running NAT64, it's already deploying IPv6. That's the
whole point of NAT64. Making IPv4 allocations conditional on IPv6
deployment just adds another review step for operators already doing the
work, while those who aren't may simply provide the right explanation and
still qualify for the addresses.
I also see the broker argument differently. Brokers exist because IPv4
addresses are much cheaper through the registry than they're worth in
actual use. Handing out smaller blocks doesn't fix that difference. It just
creates more paperwork, more requests and gives whoever manages the queue
more control over who gets the remaining space. New operators don't
necessarily get cheaper addresses just because the last blocks are handed
out in /21s. The queue simply decides who benefits from the lower registry
price. If we want fewer brokers, I think we should let the market work.
IPv4 addresses don't disappear when the pool runs out. They can still move
to operators who need them, and market prices can encourage unused space to
be put back into use.
You're right that policy requirements don't automatically lead to good IPv6
deployments. But to me, that's an argument against making IPv4 allocations
conditional on IPv6 in the first place, not a reason to keep handing out
smaller blocks.
Let the remaining pool run out. Allocate what's left under simple,
predictable rules, and let the market handle what the registry cannot.
Zenalo
On Thu, 19 Nov 2026 at 12:41, <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: New draft policy proposal PPM Dates
> AFPUB-2026-GEN-003-DRAFT01 (jordi.palet at theipv6company.com)
> 2. Re: Updated Policy Proposal - IPv6 as a criteria in IPv4 Soft
> Landing AFPUB-2026-v6-001-DRAFT03 (jordi.palet at theipv6company.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Nov 2026 11:27:19 +0100
> From: "jordi.palet at theipv6company.com"
> <jordi.palet at theipv6company.com>
> To: rpd List <rpd at afrinic.net>
> Cc: board at afrinic.net
> Subject: Re: [rpd] New draft policy proposal PPM Dates
> AFPUB-2026-GEN-003-DRAFT01
> Message-ID: <770D2836-5DD0-48BB-BA24-6B334264D58B at theipv6company.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Owen,
>
> We can debate forever what is and not in scope of the PDP, but I think it
> was obvious that clashing was not appropriate and the event yesterday was
> the one that had less participation in decades ?
>
> I?ve a suggestion, if the board could agree on that. I can happily
> withdraw the proposal, understanding that AFRINIC (not sure if it was a
> board or staff or joint decision) already took preventing measures for the
> next 4 years with the call for hosting (
> https://afrinic.net/call-for-hosting-2026.html), will the board agree on
> a formal resolution that prevent the clashes at least with other RIRs and
> the IETF?
>
> Of course, I fully understand that the wording of the resolution needs to
> prevent unforeseen circumstances, which is what the proposal (should vs
> must) is doing.
>
> Also, could the staff provide:
> 1) Real attendance data (not registered people), compared with the last
> few years (even pre-Covid)? Excluding staff, board, external support, etc.
> 2) Has the staff or board contacted the IETF to avoid being on the prefer
> not to clash instead of the must not clash list?
>
> Note that, as I explained yesterday, IETF has the dates fixed 8-10 years
> in advance, so even if AFRINIC is not in the ?must not clash? list it is
> irrelevant, unless AFRINIC decides to plan ahead more than 8-10 years in
> advance their dates. So the question is has AFRINIC actual plans to do so,
> or they expect to be only 4-5 years?
>
> In other words, the one that creates the clash is the one that is planning
> late than previous ones, right? Or I?m missing something?
>
> Regards,
> Jordi
>
> @jordipalet
>
> > El 18 nov 2026, a las 20:30, Owen DeLong via RPD <rpd at afrinic.net>
> escribi?:
> >
> > ?
> > Is this even in scope for the PDP?
> >
> > In most regions, the PDP is for matters of registry policy, not registry
> operational logistics.
> >
> > The policy is silly even if it is in scope, but I think we have drifted
> far from the intended scope here.
> >
> > Owen
> >
> >
> >> On Sep 16, 2026, at 02:19, jordi.palet--- via RPD <rpd at afrinic.net>
> wrote:
> >>
> >> ?Hi Hedrik,
> >>
> >> Co-locating is not contrary to clash.
> >>
> >> The proposal is for the PPM, not the full AFRINIC meeting. You can
> co-locate two related events, if you avoid the clash of the specific day
> for the PPM.
> >>
> >> We don?t do the AIS+AFRINIC in such way that the PPM clashes with other
> key parts of the AIS, right?
> >>
> >> Regards,
> >> Jordi
> >>
> >> @jordipalet
> >>
> >>> El 16 sept 2026, a las 10:47, Hendrik Visage via RPD <rpd at afrinic.net>
> escribi?:
> >>>
> >>> +1 on the co-locating with AfriCom/AfriTech - especially as I?m living
> in Cape Town :)
> >>>
> >>> Hendrik Visage
> >>> Director/Owner
> >>> HeViS.Co Systems t/a Envisage Cloud Solutions
> >>> hvisage at hevis.co.za <mailto:hvisage at hevis.co.za>
> >>> GSM/SMS/Signal: +27-84-612-5345 <+27%2084%20612%205345>
> >>> InstantMessenger: https://t.me/hvisage
> >>>
> >>> On 16 Sep 2026, at 8:30, Ben Roberts - AfriNIC via RPD wrote:
> >>>
> >>> +1 Andrew. The nature of these PPM events is that it is necessary to
> hold them alongside other African events in order to make it worth the trip
> for what is actually a short meeting. This year we held one PPM alongside
> the AIS (as has been traditional) and now experimenting with co-locating it
> alongside AfricaCom which is the biggest African industry event of the
> year. I would rather we see how the experiment works before introducing
> policies to tie us in knots by settling to not clash with global meetings
> that very few people from Africa take part in.
> >>>
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On 16 Sep 2026, at 08:58, Andrew Alston <aa at alstonnetworks.net>
> wrote:
> >>>>
> >>>> ?
> >>>> Hi RPD / RPD Chairs,
> >>>>
> >>>> I oppose this policy. While I believe that AfriNIC should endeavor
> to ensure that meetings do not clash, the reality is that this is sometimes
> unavoidable. Furthermore, I stand to be corrected, but I am unsure if
> other organisations have such a policy. Embedding this in our policy
> manual effectively relegates AfriNIC to second-class status compared to
> other global organisations that do not have similar policies prohibiting
> scheduling conflicts with AfriNIC.
> >>>>
> >>>> Furthermore, there may be times when an emergency policy meeting
> needs to be called to address an urgent issue, and this clause could pose a
> serious problem in that scenario.
> >>>>
> >>>> To repeat my stance above, I do not doubt the policy's intent, and
> while clashes should obviously be avoided, but I do not believe that this
> should be made a rule that restricts the PDP to the scheduling whims of
> other organisations.
> >>>>
> >>>> Thanks
> >>>>
> >>>> Andrew
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Sep 14, 2026 at 6:49?PM Hytham El-Nakhal <hytham at tra.gov.eg
> <mailto:hytham at tra.gov.eg>> wrote:
> >>>>> Dear PDWG,
> >>>>>
> >>>>>
> >>>>> We have received a new draft policy proposal named PPM Dates with ID
> AFPUB-2026-GEN-003-DRAFT01 from author Jordi Palet.
> >>>>>
> >>>>>
> >>>>> The proposal contents are published at: <
> https://afrinic.net/policy/proposals/afpub-2026-gen-001-draft01>
> >>>>>
> >>>>> https://www.afrinic.net/afpub-2026-gen-003-draft01
> >>>>>
> >>>>>
> >>>>> We encourage you to take some time to go through the proposal
> contents and provide feedback as follows: -
> >>>>>
> >>>>> ?
> >>>>>
> >>>>> a) Do you support or oppose the proposal?
> >>>>>
> >>>>>
> >>>>> b) If you oppose the proposal, state your reasons.
> >>>>>
> >>>>>
> >>>>> c) Is there anything in the proposal that is not clear?
> >>>>>
> >>>>>
> >>>>> d) What changes could be made to this proposal to make it more
> effective?
> >>>>>
> >>>>>
> >>>>> Kindly, as a way for better following up and archiving, keep the
> name and proposal ID in the subject line of your posts.
> >>>>>
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Haitham el Nakhal & Darwin Da Costa
> >>>>>
> >>>>> AFRINIC PDWG Co-Chairs
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> RPD mailing list
> >>>>> RPD at afrinic.net <mailto:RPD at afrinic.net>
> >>>>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>> _______________________________________________
> >>>> RPD mailing list
> >>>> RPD at afrinic.net
> >>>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>
> >>> _______________________________________________
> >>> RPD mailing list
> >>> RPD at afrinic.net
> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>
> >>> _______________________________________________
> >>> RPD mailing list
> >>> RPD at afrinic.net
> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>
> >>
> >> **********************************************
> >> 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.
> >>
> >> _______________________________________________
> >> RPD mailing list
> >> RPD at afrinic.net
> >> https://lists.afrinic.net/mailman/listinfo/rpd
> > _______________________________________________
> > RPD mailing list
> > RPD at afrinic.net
> > https://lists.afrinic.net/mailman/listinfo/rpd
>
>
>
> **********************************************
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20261119/61968c3a/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 19 Nov 2026 11:39:37 +0100
> From: "jordi.palet at theipv6company.com"
> <jordi.palet at theipv6company.com>
> To: 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: <197BBF1A-ACC7-45EB-A8DE-C41B45A2037A at theipv6company.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Owen,
>
> I?m with you on one side, but also on the side that we like it or not,
> people may need a few more IPv4 addresses, either to prepare the transition
> (for example a /24 in every NAT64 Cluster, and if you have a big network
> you may have several of them), or to connect business customers that still
> require ?real? dual-stack.
>
> Of course this is also the case for newcomers (new ISPs, or end-users that
> previously were not multi homed and prefer not to use IPv4 NAT for the
> multihoming, because they don?t have to use that for IPv6 as well), etc.
>
> So releasing the addresses in big chunks (/18-/21) it is unnecesary if
> you?re also deploying IPv6. 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, which in my opinion is unfair.
>
> Yes, I understand that if we allow releasing big chunks, it looks like we
> enforce people to deploy IPv6 much faster, but experience shows that this
> is not reality and may bring us to very ugly and incorrect deployments.
>
> Regards,
> Jordi
>
> @jordipalet
>
> > El 18 nov 2026, a las 20:30, Owen DeLong <owen at delong.com> escribi?:
> >
> > ?
> > I think everyone here knows I am a strong v6 proponent.
> >
> > This is the wrong approach. Let the v4 pool run out and let that be the
> natural point where v4 becomes difficult to obtain for everyone.
> >
> > All of these gyrations to pretend that v4 can still be available far
> into the future is just prolonging the pain.
> >
> > Issue the addresses, get them into production, and let the market do
> what markets do.
> >
> > Owen
> >
> >
> >> On Nov 9, 2026, at 09:26, Loganaden Velvindron <loganaden at gmail.com>
> wrote:
> >>
> >> ?
> >>
> >>
> >> On Mon, 09 Nov 2026, 15:17 jordi.palet--- via RPD, <rpd at afrinic.net
> <mailto:rpd at afrinic.net>> wrote:
> >>> Hi Saul,
> >>>
> >>> The previous version of this proposal was looking for actual IPv6
> traffic from your customers. The objection was ?what happens if you provide
> IPv6 and your customers disable it in their LANs or computers or whatever?.
> >>>
> >>> This version is just ensuring that you do your job: you enable IPv6,
> for example, in the CPE of the access network, and of course, you assign a
> prefix to it, so if the customer is willing to use IPv6 from their LANs, it
> actually can do it.
> >>>
> >>> The text ?without interference? means the customer ?don?t need to ask
> for it?, it is enabled by default. So only customers actually having
> internal routers that disable IPv6 ?on purpose? (which may happen in
> enterprise networks), or disabling it in devices in the LAN, will not use
> IPv6.
> >>>
> >>> Same in the case of a Data Center. You must provide a prefix to your
> customers, if they use it or not is not measured anymore.
> >>>
> >>> I believe the text is clear, but if you prefer some alternative
> wording, we can improve it. Also, if we had the impact analysis from the
> staff, we could see if they are interpreting it correctly or not.
> >>
> >>
> >> There are a number of reasons why customers choose to disable v6. I've
> encountered a case where the download speed was better on v4 than on v6.
> The enterprise office customer decided to disable v6 to "avoid slow
> internet" despite my objection.
> >>
> >> Im working closely with vendors and not that many put ipv6 on their
> brochure. You have to ask.
> >>
> >> Im involved in an upcoming project on ipv6 for edge. Hopefully I will
> be able to share details soon.
> >>
> >>
> >>
> >>>
> >>> Regards,
> >>> Jordi
> >>>
> >>> @jordipalet
> >>>
> >>>> El 9 nov 2026, a las 11:31, Saul Stein via RPD <rpd at afrinic.net
> <mailto:rpd at afrinic.net>> escribi?:
> >>>>
> >>>> Hi
> >>>> I still don?t support the proposal.
> >>>>
> >>>> Maybe I am not understanding the wording:
> >>>> ?In the case of access networks, the percentage of customers that
> have access to global IPv6 delegations ?without interference required from
> the Network Operator? must be at or above the following thresholds?
> >>>>
> >>>> And
> >>>> ?In the case of content hosting networks, the percentage of assigned
> IPv4 space assigned to those networks ?also covered by IPv6 assignments?
> must reach:?
> >>>>
> >>>> What does this mean in practice?
> >>>> I can offer v6 to all my customers, but if they don?t want to use it,
> then based on my reading on this, I can?t get more IPv4 space?
> >>>> That means my customer base is prejudicing me against getting more v4
> space.
> >>>>
> >>>> If the policy is simply saying we need to be able to offer clients
> native v6 space, then I?ll support it. However the wording needs to be
> clearer.
> >>>>
> >>>> Regards
> >>>> Saul
> >>>>
> >>>>
> >>>> From: Hendrik Visage via RPD <rpd at afrinic.net <mailto:rpd at afrinic.net
> >>
> >>>> Sent: Saturday, 26 September 2026 10:49
> >>>> To: Hytham El-Nakhal <hytham at tra.gov.eg <mailto:hytham at tra.gov.eg>>;
> rpd List <rpd at afrinic.net <mailto:rpd at afrinic.net>>
> >>>> Subject: Re: [rpd] Updated Policy Proposal - IPv6 as a criteria in
> IPv4 Soft Landing AFPUB-2026-v6-001-DRAFT03
> >>>>
> >>>> In support of the proposal.
> >>>>
> >>>> On Wed, 23 Sept 2026, 11:11, Hytham El-Nakhal <hytham at tra.gov.eg
> <mailto:hytham at tra.gov.eg>> wrote:
> >>>>
> >>>> Dear PDWG,
> >>>>
> >>>>
> >>>> We have received an update to the draft policy proposal "IPv6 as a
> criteria in IPv4 Soft Landing" - ID AFPUB-2026-v6-001-DRAFT03 from author
> Jordi Palet Martinez and new co-author Jaco Kroon on 17 September 2026.
> >>>>
> >>>>
> >>>> The proposal contents are published at:
> >>>>
> >>>> https://www.afrinic.net/afpub-2026-v6-001-draft03
> >>>>
> >>>>
> >>>> We encourage you to take some time to go through the proposal
> contents and provide feedback as follows:
> >>>>
> >>>>
> >>>> a) Do you support or oppose the proposal?
> >>>>
> >>>>
> >>>> b) If you oppose the proposal, state your reasons?
> >>>>
> >>>>
> >>>> c) Is there anything in the proposal that is not clear?
> >>>>
> >>>>
> >>>> d) What changes could be made to this proposal to make it more
> effective?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Kind Regards,
> >>>>
> >>>> Haitham El Nakhal and Darwin da Costa
> >>>> PDWG Co-Chairs
> >>>> Policy Development Working Group - AFRINIC
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> RPD mailing list
> >>>> RPD at afrinic.net <mailto:RPD at afrinic.net>
> >>>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> ---
> >>>> Hendrik Visage
> >>>> hvisage at hevis.co.za <mailto:hvisage at hevis.co.za>
> >>>> GSM/SMS/Signal: +27-84-612-5345 <+27%2084%20612%205345>
> >>>> InstantMessenger: https://t.me/hvisage
> >>>> _______________________________________________
> >>>> RPD mailing list
> >>>> RPD at afrinic.net <mailto:RPD at afrinic.net>
> >>>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>
> >>>
> >>> **********************************************
> >>> IPv4 is over
> >>> Are you ready for the new Internet ?
> >>> http://www.theipv6company.com <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.
> >>>
> >>> _______________________________________________
> >>> RPD mailing list
> >>> RPD at afrinic.net <mailto:RPD at afrinic.net>
> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> >> _______________________________________________
> >> RPD mailing list
> >> RPD at afrinic.net
> >> https://lists.afrinic.net/mailman/listinfo/rpd
>
>
>
> **********************************************
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20261119/e5603bc6/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 26
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20261119/e9aa9568/attachment-0001.html>
More information about the RPD
mailing list