Summary

  • AFRALO submitted the joint ICANN84 statement to the Board “for information purposes,” although the document asked for a new DNS-business program, support for IXPs, at least one L-Root instance per country where technically needed, more African Fellows and a Think Tank action plan.
  • The 31 August reply mapped several requests to existing ICANN work and referred wider connectivity questions to governments and the broader ecosystem. It did not announce a new program, budget, per-country deployment target, Fellowship quota or formal Think Tank.
  • The accurate public record is a line-item disposition: existing-work alignment, shared responsibility, referral or no stated action—not a binary story in which the Board either accepted or rejected the whole statement.

The cover note sets the procedural ceiling

Hadia Elminiawi, then chair of the African Regional At-Large Organization, sent the joint statement on 6 February 2026 after its discussion at ICANN84 in Dublin. Her cover note says AFRALO approved submission to the Board “for information purposes.” That label matters because AFRALO is a regional channel for the views of individual Internet users. It can formulate advice, convene debate and partner on regional work. Its statement does not by itself appropriate money, direct ICANN org or bind the Board.

The contents were nevertheless operationally ambitious. The statement called for a new regional program to stimulate DNS businesses; financing and support for Internet exchange points; deployment of L-Root or ICANN Managed Root Server capacity in at least one location per country, subject to technical need; higher African participation in Fellowship and NextGen@ICANN; train-the-trainer work; discussion of blockchain domain names and other alternative naming systems; and an action plan leading toward an AFRALO-AfrICANN Think Tank.

Those proposals should not be downgraded to mere talking points. But the reverse mistake is equally serious: recommendations inside an information submission do not become mandates because a Board Chair answers them politely.

The reply classifies more than it decides

Tripti Sinha’s letter, dated 31 August and published on 1 September, begins with strong substantive alignment. It says the emphasis on interoperability and an unfragmented Internet accords with ICANN’s mission and strategic vision. It cites the goals of securing the unique-identifier systems and preserving a single, globally interoperable Internet.

The letter then narrows the operating surface. Challenges affecting Internet development in Africa do not all fall inside ICANN’s remit. Affordable connectivity, it says, requires collective effort by governments and other stakeholders; ICANN’s contribution is limited to its role in the unique-identifier and DNS ecosystem.

That distinction changes how every subsequent citation must be read. The 2023 Africa Domain Name Industry Study is an evidence resource, not the launch of the requested DNS-business program. Coalition for Digital Africa projects involving IXPs and additional L-Root instances show that relevant work exists; they do not create a fresh financing decision or accept the requested geography. Universal Acceptance, Technical Engagement and KINDNS demonstrate standing capacity. They are not a new quota, budget or work order issued in response to the statement.

The reply closes by pointing to the Africa Regional Plan and to continued discussion in the Internet Governance Forum and other multistakeholder forums. That is a route for dialogue. It is not an assignment of responsibility for every call to action.

The line-item disposition on 1 September

The DNS-business request received a pointer to a study that measured the market and made recommendations. No new stimulation program, owner, budget or launch date appears in the reply.

The IXP request sits across a mission boundary. The reply acknowledges Coalition work, while assigning the wider affordability problem to governments and the ecosystem. The pre-existing Coalition project was specific: it sought to strengthen five selected IXPs, supported by an ICANN grant and implemented by the Internet Society. The letter does not announce another grant or extend that scope.

The root-server request is the clearest numerical mismatch. AFRALO asked for at least one L-Root instance per country where technically needed. The reply says ICANN supports deployment of additional L-Root instances. The FY26–30 Africa Regional Plan is narrower still: it proposes additional clusters in “key African countries.” None of these documents establishes a one-per-country commitment or deadline.

The participation request has real alignment but no new quota. The regional plan seeks more African Fellows and NextGen@ICANN participants and tracks participant counts. It also lists insufficient Fellowship funding as a risk. The Board reply points to this existing plan; it does not state how many places will be added, who will select them or what resources will change.

Technical training, Universal Acceptance and DNS security receive the strongest existing-program match. The course catalog already covers DNS operations, DNSSEC, abuse, network security and UA. KINDNS is a voluntary best-practice initiative for DNS operators. These are substantive instruments. Their existence shows a place where recommendations may be pursued; it does not prove that the requested package was adopted.

Alternative naming and the proposed Think Tank remain the largest blanks. ICANN’s strategic plan recognizes alternate name-resolution methods as part of the changing identifier landscape and a risk to a single global root. The reply, however, creates no AFRALO-linked workstream on blockchain names. It does not mention the Think Tank at all. The original statement describes a group “within AFRALO-AfrICANN” and anticipated a first discussion at ICANN85. There is no Board-created ICANN body, charter, budget, owner or deadline in the response.

Existing work is evidence of capacity, not evidence of adoption

There is a fair counterargument. A Board Chair cannot be expected to turn every community letter into a resolution table, and the response may have been intended as recognition rather than adjudication. Existing programs may already provide the most efficient route. Demanding a bespoke initiative for every recommendation could fragment work and duplicate resources.

That argument supports the letter’s restrained form. It does not justify overstating its effect. If the answer is “this is already being handled,” the public record still needs to say which program owns the request, whether its scope actually covers the requested outcome, and what measure would show completion. If the answer is “outside mission,” a named referral is more useful than a general invitation to continue discussion. If no decision was sought, silence should remain silence.

The Board also did not “reject Africa’s digital-divide agenda.” It accepted the relevance of the problem, identified ICANN’s contribution and placed other levers elsewhere. The governance question is not whether the ambitions are worthy. It is which institution can commit what.

A public disposition receipt

For future correspondence of this kind, a short annex could preserve the record without turning advice into litigation. Each row would identify the request, the requester and procedural status; whether the matter is inside ICANN’s mission, shared or outside it; and whether the response is acceptance, existing-work alignment, referral, request for more evidence or no action.

The same row should name the responsible party, any funding or resource decision, measurable target, deadline, follow-up forum and status date. A link to an existing program should identify the exact overlap and the part that remains uncovered. A later decision would update the row rather than rewrite the history.

Applied here, the receipt would show a mixed outcome: strong strategic alignment on interoperability; existing work for DNS research, IXPs, root-server capacity, UA and training; shared responsibility for connectivity; and no operative disposition for a new DNS-business program, a one-per-country L-Root target, an AFRALO-linked alternative-naming workstream or a formal Think Tank.

That record is less dramatic than “accepted” or “rejected.” It is also more useful. It tells African stakeholders where action can be measured, where another institution must act and where a proposal still has no owner.

Sources