<div dir="auto">Dear PDWG,<div dir="auto"><br></div><div dir="auto">I agree with Thandeka and remain opposed to this proposal.</div><div dir="auto"><br></div><div dir="auto">The attempt to dismiss similar objections as “astroturfing” does not answer the substance of those objections. Different participants may independently reach the same conclusion when a proposal introduces requirements that are not supported by demonstrated operational necessity. Similarity of position is not evidence of improper coordination.</div><div dir="auto"><br></div><div dir="auto">The relevant question is not who used comparable language, but whether the proposal protects a genuine technical invariant such as registry accuracy, uniqueness, security, or operational continuity. If it does not, the matter should remain with operators and voluntary operational practice.</div><div dir="auto"><br></div><div dir="auto">Participation should be assessed by the quality of the argument, not invalidated because several people object on the same principled grounds. A mailing list should discuss policy, not police conformity of expression.</div><div dir="auto"><br></div><div dir="auto">For these reasons, I support Thandeka’s objection and maintain my opposition to the proposal.</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Nonhlanhla </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, 18 Jul 2026, 11:56 am <<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: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) and Amendment of<br>
Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02)<br>
(Thandeka Mseleku)<br>
2. Re: IPv6 as a criteria in IPv4 Soft Landing<br>
AFPUB-2026-v6-001-DRAFT01. (Simphiwe Ngubane)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 18 Jul 2026 10:59:07 +0200<br>
From: Thandeka Mseleku <<a href="mailto:mselekuthandeka80@gmail.com" target="_blank" rel="noreferrer">mselekuthandeka80@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Cc: <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) and Amendment of<br>
Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02)<br>
Message-ID:<br>
<CA+mVb0m_TZG5Mn+a0gK=<a href="mailto:kXZ5yCoEMq4yKazG_%2B1GMUouiEpkYA@mail.gmail.com" target="_blank" rel="noreferrer">kXZ5yCoEMq4yKazG_+1GMUouiEpkYA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear PDWG,<br>
<br>
I remain opposed to this proposal.<br>
<br>
The fact that multiple community members express similar concerns should<br>
not diminish the substance of those concerns. What matters is whether the<br>
arguments are technically and operationally sound.<br>
<br>
I continue to believe that policy should reflect demonstrated operational<br>
needs rather than introduce obligations that have not been shown to be<br>
necessary. Registry policies should preserve stability, accuracy, and<br>
neutrality without expanding prescriptive requirements where voluntary<br>
operational practices are already sufficient.<br>
<br>
For that reason, I do not believe this proposal has demonstrated a<br>
compelling justification for the additional requirements it introduces.<br>
Maintaining operator flexibility while ensuring sound resource governance<br>
remains the more proportionate approach.<br>
<br>
BR,<br>
*Thandeka Mseleku*<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260718/90004a03/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260718/90004a03/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 18 Jul 2026 09:55:24 +0000<br>
From: Simphiwe Ngubane <<a href="mailto:NGBSIM008@myuct.ac.za" target="_blank" rel="noreferrer">NGBSIM008@myuct.ac.za</a>><br>
To: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>
Cc: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] IPv6 as a criteria in IPv4 Soft Landing<br>
AFPUB-2026-v6-001-DRAFT01.<br>
Message-ID:<br>
<<a href="mailto:JN1P275MB06001BC72DBF6290E7A7336AB1C52@JN1P275MB0600.ZAFP275.PROD.OUTLOOK.COM" target="_blank" rel="noreferrer">JN1P275MB06001BC72DBF6290E7A7336AB1C52@JN1P275MB0600.ZAFP275.PROD.OUTLOOK.COM</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Good morning Seun,<br>
<br>
To the best of my knowledge I've only posted once or twice on this platform. I'm comparatively knew to the forum.<br>
<br>
In terms of the similarity you allude to, I should think it well spotted as we both, from my understanding, object/ed to the new policy proposal. Fundamentally, as an objection to IPv6 enforcement creep through IPv4 policy.<br>
<br>
Kind Regards<br>
Simphiwe Ngubane<br>
<br>
________________________________<br>
From: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>
Sent: Friday, July 17, 2026 2:10:59 pm<br>
To: Simphiwe Ngubane <<a href="mailto:NGBSIM008@myuct.ac.za" target="_blank" rel="noreferrer">NGBSIM008@myuct.ac.za</a>><br>
Cc: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] IPv6 as a criteria in IPv4 Soft Landing AFPUB-2026-v6-001-DRAFT01.<br>
<br>
CAUTION: This email originated outside the UCT network. Do not click any links or open attachments unless you know and trust the source.<br>
<br>
This response seem similar to the response from <a href="mailto:nndemo@staff.zegu.ac.zw" target="_blank" rel="noreferrer">nndemo@staff.zegu.ac.zw</a><mailto:<a href="mailto:nndemo@staff.zegu.ac.zw" target="_blank" rel="noreferrer">nndemo@staff.zegu.ac.zw</a>><br>
<br>
Regards<br>
----<br>
Sent from my mobile<br>
kindly excuse typos<br>
<br>
On Mon, 13 Jul 2026, 10:42?am Simphiwe Ngubane via RPD, <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>> wrote:<br>
Dear PDWG,<br>
<br>
I agree with Alain?s response because it maintains a necessary distinction between the role of registry policy and the realities of network operations. The purpose of the IPv4 Soft Landing policy should remain centered on the coordination and management of scarce Internet number resources, rather than introducing operational conditions tied to IPv6 deployment.<br>
<br>
I also agree that IPv6 adoption across the region cannot be measured only through deployment statistics. Many operators may already be investing in infrastructure upgrades, staff training, network planning, and transition readiness, even where large-scale IPv6 traffic is not yet visible. Deployment decisions are influenced by operational readiness, commercial priorities, customer demand, equipment lifecycles, and local market conditions, all of which vary significantly across the AFRINIC service region.<br>
<br>
Importantly, the IPv4 Soft Landing policy was developed to address IPv4 scarcity and allocation management. While IPv6 adoption remains an important objective for the long-term sustainability of the Internet, using IPv4 allocation policy as a mechanism to drive deployment risks combining two distinct policy goals. Resource coordination and technology adoption are related, but they are not the same function.<br>
<br>
In my view, policies work best when they remain focused on their narrow coordination purpose while allowing operators the flexibility to determine the most practical technical path for their networks. Linking IPv4 eligibility to IPv6 deployment could unintentionally disadvantage smaller or resource-constrained operators that are actively preparing for transition but are not yet in a position to deploy at scale.<br>
<br>
Encouraging IPv6 through technical cooperation, implementation experience, training, knowledge sharing, and operational forums is likely to produce more sustainable progress than introducing deployment requirements into resource management policies. Long-term IPv6 success depends on the readiness of the broader ecosystem, including network operators, vendors, content providers, transit providers, and end-user environments.<br>
<br>
For these reasons, I support keeping the IPv4 Soft Landing policy technically neutral, operationally realistic, and aligned with the diverse needs of networks across the AFRINIC region. RIRs are most effective when they remain neutral coordinators of Internet number resources while enabling, rather than prescribing, the evolution of network technologies.<br>
<br>
Yours Sincerely,<br>
Simphiwe Ngubane<br>
MSc in Engineering UCT<br>
(My views are my own in given in my personal capacity and do not form part of any affiliation or representation to the University of Cape Town)<br>
Disclaimer - University of Cape Town This email is subject to UCT policies and email disclaimer published on our website at <a href="https://www.uct.ac.za/main/email-disclaimer" rel="noreferrer noreferrer" target="_blank">https://www.uct.ac.za/main/email-disclaimer</a><<a href="https://www.uct.ac.za/main/email-disclaimer" rel="noreferrer noreferrer" target="_blank">https://www.uct.ac.za/main/email-disclaimer</a>> or obtainable from +27 21 650 9111. If this email is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via <a href="https://csirt.uct.ac.za/report-incident" rel="noreferrer noreferrer" target="_blank">https://csirt.uct.ac.za/report-incident</a><<a href="https://csirt.uct.ac.za/report-incident" rel="noreferrer noreferrer" target="_blank">https://csirt.uct.ac.za/report-incident</a>><br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><mailto:<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><<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
<br>
Disclaimer - University of Cape Town This email is subject to UCT policies and email disclaimer published on our website at <a href="https://www.uct.ac.za/main/email-disclaimer" rel="noreferrer noreferrer" target="_blank">https://www.uct.ac.za/main/email-disclaimer</a> or obtainable from +27 21 650 9111. If this email is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via <a href="https://csirt.uct.ac.za/report-incident" rel="noreferrer noreferrer" target="_blank">https://csirt.uct.ac.za/report-incident</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260718/4684f837/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260718/4684f837/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 222, Issue 42<br>
************************************<br>
</blockquote></div>