<div dir="auto"><div>This response seem similar to the response from <a href="mailto:nndemo@staff.zegu.ac.zw">nndemo@staff.zegu.ac.zw</a></div><div><br></div><div dir="auto">Regards </div><div data-smartmail="gmail_signature">----<br>Sent from my mobile<br>kindly excuse typos </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 13 Jul 2026, 10:42 am Simphiwe Ngubane via RPD, <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
Dear PDWG,</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
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.</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
Yours Sincerely,</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
Simphiwe Ngubane </div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
MSc in Engineering UCT</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(33,33,33)">
(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) </div>
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" target="_blank" rel="noreferrer">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" target="_blank" rel="noreferrer">https://csirt.uct.ac.za/report-incident</a>
</div>
_______________________________________________<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>
</blockquote></div>