African ITU proposal puts IPv6 in the licence conversation

IPv6 spent years asking nicely. Africa puts the licence form on the table.

Why it matters

An African ITU proposal invites countries to consider IPv6 requirements in telecom licences. It pairs that regulatory opening with deadlines and a harder question: does the network actually work over IPv6?

Daniel Kade25 October 2026 at 21:43 UTCReading Time 2 minLast update: 25 October 2026

The African proposal invites countries to consider IPv6 requirements in licences and to measure whether services work.

Summary

African administrations propose inviting countries to consider IPv6 deployment requirements in telecom licensing and regulatory obligations, where appropriate, with transparency and competition safeguards.
The draft also calls for time-bound national objectives where appropriate and indicators of operational readiness across networks, exchanges, clouds and public services. The adopted 2022 text emphasized cooperation and deployment statistics.

IPv6 has had a long career as the agenda item everybody agrees with before returning to the network that pays the bills. The African proposal to revise ITU Resolution 180 introduces a more pointed possibility: Member States and Sector Members are invited to consider putting IPv6 deployment requirements into telecom licences, regulatory frameworks and operator obligations, where appropriate. It asks for transparent mechanisms tied to accountability and competition. The rubber stamp is hovering; it has not landed on any national licence.

The resolution adopted in 2022 already urged governments to update legacy systems and have public services support IPv6. It asked ITU to work with RIRs and others on training and progress statistics. Those were deployment policies and assistance. The new clause reaches the legal document that determines an operator's terms of entry or operation. A national regulator, rather than the ITU or a registry, would decide whether and how to use that invitation.

The same draft makes the measurement problem harder to dodge. It encourages national objectives with time-bound targets for government networks, public services and major operators. It asks for IPv6 operational readiness indicators and names exchange points, cloud platforms and digital public infrastructure. An allocated address, an enabled interface and a service that completes a real user transaction are three different receipts. The text itself says deployment alone does not establish readiness.

The ITU contribution register lists Addendum 32 as posted on 25 October. PP-26 will consider it in November. A useful national licence clause would have to name the service, test path, deadline and evidence a regulator will accept. A vague “support IPv6” box creates a ceremony. A measurable requirement tells operators what to build and lets customers see whether it works.