Summary

  • Resolution 05.26 congratulated and thanked the NRO, AfriNIC, AfriNIC’s organizers, Board, President, staff and members, and other supporting organizations and parties. It praised tireless effort, excellence at the executive, registration and technical levels, and commitment to regional representation, global coordination, openness and bottom-up self-management.
  • The resolution’s normative force is real: its four values can be converted into demanding, evidence-based tests of AfriNIC’s conduct. Its legal and institutional limit is equally real: congratulations and thanks do not grant sovereignty, ownership, territorial jurisdiction, police or punitive power, general regulatory authority, or a mandate to speak for absent states, operators, resource holders and users.
  • The adjacent Resolution 05.25 performed the separate act of recognizing AfriNIC as a Regional Internet Registry. A later instrument, dated 25 April 2005, separately brought AfriNIC into the NRO and specified participation rights and obligations. Keeping those acts apart prevents ceremonial legitimacy from being mistaken for delegated power.
  • NRS, Heng Lu, LARUS and BTW.Media make the continuing stakes clear. Participation can discipline a private coordinator without becoming authorization by everyone; service geography can organize work without becoming territory; and registry dependence can affect live networks without making the registry their owner or ruler.

Two sentences, two institutional acts

The most important word in Resolution 05.26 may be the word that never appears: “recognizes.” The official record places 05.26 immediately beside a different Board clause, Resolution 05.25. The latter performs the recognition act. Resolution 05.26 performs another kind of act altogether. It “congratulates and thanks.” The distinction is not pedantry. It is the line between a decision about status inside a coordination framework and a commendation of the work, service and values associated with reaching that point.

That distinction gives 05.26 its own significance. If it were merely decorative repetition, there would have been no need for a second resolved clause. The Board used 05.26 to memorialize the human and institutional effort behind AfriNIC’s transition, identify those it wished to honour, praise performance at three levels and associate the undertaking with four declared values. The clause created reputational capital. It told the recipients and the wider technical community what qualities the Board considered worthy of public gratitude.

But distinct significance is not unlimited significance. Resolution 05.26 contains no verb granting, delegating, vesting, transferring, licensing or authorizing power. It does not define subjects over whom AfriNIC may rule. It does not identify an electorate that appointed AfriNIC to speak for Africa. It provides no enforcement mechanism, remedy, appeal, duration, succession rule or liability allocation. It does not say that address space belongs to the registry, that a service boundary is territory, or that a membership process produces public law. The clause matters because commendation can guide later accountability.

It cannot bear the radically different weight of a constitution, treaty, statute, property conveyance or popular delegation.

A simple counterfactual exposes the boundary. Had 05.25 existed without 05.26, the operative recognition would still have occurred, but the formal record would have lacked this separate declaration of gratitude and values. Had 05.26 existed without 05.25, the Board would have praised and thanked contributors, but the missing recognition act could not have been supplied by congratulatory language. The two clauses reinforce a common occasion while doing different work. This article is about the second work: what the praise says, what it can demand, and what it can never authorize.

The grammar of gratitude

Resolution 05.26 begins with recipients, not subjects. It thanks the NRO and AfriNIC; AfriNIC’s organizers, Board, President, staff and members; and an open-ended class of other supporting organizations and parties. That list is revealing because it treats institutional creation as cooperative labour. A registry does not appear fully formed through a single executive declaration. Organizers establish it, staff operate it, members participate, peer institutions support transition, and other parties contribute. The Board’s wording distributes credit across that ecology.

The distribution of credit must not be converted into a chain of political representation. A person thanked for organizing is a contributor, not automatically an agent of every network operator. A corporate Board is an organ of the organization, not a legislature for every person within a service region. Members can authorize decisions inside the scope of membership rules and contracts, but membership does not make them proxies for nonmembers. Supporting organizations can endorse a transition without becoming constitutional delegates.

The open-ended reference to “other” supporters is especially resistant to political inflation: the clause neither identifies every one of them nor states how much support each supplied.

This is the stakeholder-principal distinction at the heart of Heng Lu’s controlling account. Stakeholders are real. Their expertise, objections, cooperation, warnings and participation can make technical coordination more accurate and more legitimate within its proper scope. Yet a stakeholder is not automatically a principal, and participation is not automatically an instrument of authorization. One may attend, advise, deliberate or support without acquiring the right to bind everyone who did not. Resolution 05.26 rewards contribution.

It does not solve the agency question of who authorized whom to make which decision for which affected party.

The clause next praises “tireless efforts” and dedication to excellence in services at the executive, registration and technical levels. The three-level formulation is more useful than generic celebration. Executive performance concerns institutional direction and stewardship. Registration performance concerns the integrity and accessibility of the registry function. Technical performance concerns reliable operation and coordination. In a proper reading, the praise acknowledges demonstrated work around the transition and expresses an expectation that competence should continue across the whole service stack.

It is not a perpetual warranty. The Board did not define a metric for tirelessness or excellence, establish a future audit, or promise that every later action would possess the praised quality. Commendation in 2005 cannot immunize conduct in another period from evidence-based scrutiny. Indeed, praise becomes valuable only if it remains possible to ask whether present service still deserves it. Otherwise “excellence” stops being a standard and becomes an inherited badge, detached from performance.

The closing association with the “best traditions of the Internet” is likewise normative rather than incorporative. It places the work in a lineage of cooperative technical practice, but it does not silently import a constitution, body of law or complete catalogue of powers. Traditions can orient conduct. They cannot answer questions the enacted clause leaves unanswered: who the principals are, which decisions fall within scope, which remedies exist, or what happens when an institution departs from the value it once received praise for embodying.

Four values, four tests

The durable center of Resolution 05.26 is its quartet of values: regional representation, global coordination, openness and bottom-up self-management. Their usefulness lies not in treating them as accomplished forever, but in turning each into a question that can be answered with records.

Regional representation requires the greatest care because the language of place can easily become the language of authority. AfriNIC’s service region is an administrative arrangement for number-registration services. It is not a sovereign territory, and “Africa” is not a single corporate principal whose authorization can be inferred from the registry’s name. If an institution claims regional representation, the proper inquiry is concrete: Which constituency is represented? Who selected the representative? By what instrument? Against what denominator? For what subject matter and for how long?

Can the principal withdraw, replace or challenge the representative?

AfriNIC’s application supplied evidence relevant to institutional design. It described a six-subregion Board structure, public meetings and mailing lists. It reported more than 68 organizations signing a founding membership charter and about 40 formal support letters. It separately described about 120 registered participants in an early policy process, including representatives of more than 30 African local Internet registries, and more than 85 participants from 30 countries at a May 2004 meeting in Dakar.

Those figures should neither be dismissed nor combined. They concern different activities and different groups: charter signatories, support letters, registered policy participants, LIR representation, meeting attendance and countries present. None supplies a common continent-wide denominator. The record does not show all organizations that might have signed, all parties approached for letters, all LIRs contacted, all operators or resource holders affected, all states, or all Internet users.

Country presence at a meeting is not the same as delegation by a state; an LIR participant is not a proxy for every customer; a member is not the population. The participation evidence demonstrates organized support and engagement inside a private institutional project. It does not prove that Africa as a political whole transferred authority.

Global coordination is the second value. Its legitimate object is real and important. Internet number uniqueness, consistent records, interoperability, proof, security and continuity depend on cooperation across institutional boundaries. A regional registry cannot maintain useful records in isolation from other registries and the wider coordination system. Resolution 05.26 properly honours the NRO and supporting institutions for work that helped make the transition coherent.

Heng Lu’s running-code boundary supplies the controlling measure. Coordination is justified where it is necessary to keep the common technical layer coherent: protect uniqueness, maintain accurate records, support verifiable claims, preserve security and keep networks operating. Coordination does not become global government merely because its subject is global. Nor does interdependence give a coordinating body superior title over the things recorded. A map can be indispensable without owning the territory it depicts; a ledger can be essential without owning the assets whose status it records.

The NRO’s own documentary sequence demonstrates this narrower structure. Its memorandum of understanding created a coordinating mechanism through which RIRs could act on matters delegated by their written agreement. That is a private inter-organizational arrangement with defined procedures, not a treaty establishing a sovereign. More decisively, AfriNIC’s joinder bears the date 25 April 2005, seventeen days after Resolution 05.26.

The joinder separately recognized AfriNIC as an NRO member, required execution of the memorandum, addressed expenses and conferred specified participation rights, including the selection of three individuals to the NRO Number Council. If thanking the NRO and AfriNIC on 8 April had itself created membership, the later operative instrument would have been doing unnecessary work. The chronology proves separation: gratitude acknowledged coordination; agreement created the membership relationship.

Openness is the third value. It is not simply a statement that a meeting was advertised or a mailing list technically accessible. Genuine openness concerns notice, usable access, intelligible records, the ability to place an objection before decision-makers, and a traceable account of how the objection affected the result. Language, connectivity, time, cost and expertise can all shape who uses a formally open door. A process may be publicly observable while participation remains thin or uneven. Openness therefore cannot certify itself.

ICP-2 helps explain why the word appeared in the institutional setting. The criteria called for an open and transparent bottom-up policy process accessible to interested parties, broad LIR support, fair representation of constituencies, neutrality, technical expertise, adherence to relevant policy, planning, funding, recordkeeping and confidentiality. The IANA evaluation concluded that AfriNIC met all ten conditions and praised its bottom-up self-governance, technical operations, transition and cooperation. Those official materials prove what the criteria required and what the evaluators concluded at the time.

They do not prove a popular mandate, and they do not remove the need to test later conduct against evidence.

For openness to function as an accountability promise, the institution must be able to show more than access in principle. It should be possible to reconstruct notice, submissions, objections, responses, amendments, final reasons and available review. The question is not whether every interested person took part. Universal participation is neither realistic nor necessary for private coordination. The question is whether a party whose legitimate interests were affected had a meaningful route to learn, speak, receive an answer and challenge an error—and whether nonparticipation was later misrepresented as consent.

Bottom-up self-management is the fourth and most easily romanticized value. Within a membership organization, bottom-up processes can be highly legitimate. Members can develop policies, select internal representatives, allocate responsibilities and hold officeholders to rules they accepted. Technical participants can surface operational consequences that a remote executive would miss. Distributed deliberation can resist arbitrary control.

But “self” must be identified before “self-management” can carry meaning. If the self is AfriNIC’s membership, the authority produced by the process is internal and bounded by membership, contract and ordinary law. If the self is a particular policy community, its output binds only to the extent that affected principals actually authorized that community or agreed to the relevant procedure. The phrase cannot expand by rhetorical drift until “community” means every user, state, operator and resource holder in Africa. Absent parties do not become governed merely because participants described their own process as bottom-up.

NRS makes this promise-and-boundary structure explicit in the contemporary debate. Its account treats openness, transparency and bottom-up process as foundational commitments worth defending, particularly when institutional action threatens to become top-down. NRS advocates, researches, convenes and represents members who expressly authorize it. It does not become a replacement registry or sovereign. It does not operate AfriNIC’s registry systems, RPKI, WHOIS or RDAP, appeals, elections, custody or continuity.

That boundary strengthens its critique: it can insist that a coordinator honour its promises without seeking to inherit the coordinator’s function or inflate advocacy into rule.

Taken together, the four values generate a practical matrix. For representation, identify principal, authorization, denominator and scope. For coordination, identify the necessary technical dependency and whether cooperation is reciprocal, auditable and replaceable. For openness, identify notice, records, usable participation, response and review. For bottom-up self-management, trace who can initiate, amend, reject, appeal and exit. Passing these tests improves the accountability of a private registry. It never transforms private accountability into sovereign jurisdiction.

What the official record proves—and what it cannot

The institutional background to the paired resolutions is substantial. The shared recitals identify an application and transition plan, support from incumbent registries and the NRO, provisional recognition, completion of the transition, an updated application, a favourable NRO assessment, and review by the ICANN President of the application and IANA report against ICP-2. These are relevant facts about the occasion. They explain why the Board had reason to celebrate effort and service. They do not alter the operative verbs in 05.26.

The IANA evaluation also provides serious evidence. It reported satisfaction of the recognition criteria and concluded that a very substantial majority were prepared to support AfriNIC. That conclusion matters as an evaluation of readiness and support. Yet the surviving record does not publish a complete continent-wide electorate, a list of all LIRs contacted, a response denominator or a popular vote among African users and states. “Very substantial majority” must therefore remain an attributed evaluative conclusion, not be converted into a mathematically complete claim about everyone affected.

The application described AfriNIC as a non-governmental, not-for-profit, membership-based organization whose structure gave control to members. That description is consistent with private self-management. It is not evidence of public sovereignty. A membership corporation can exercise meaningful authority over its internal affairs and perform necessary technical services while remaining subject to ordinary law, contract, member rights and independent review. Its private form is not an embarrassment to be hidden beneath grander language. It is the honest basis on which its legitimate functions can be defined and protected.

The historical resolution tracker should be handled with similar discipline. It reproduces both clauses and offers summary and implementation metadata, while warning that its summaries, explanations and identifications have no official authority and do not modify or override Board resolutions. It records no implementation actions and does not assign a separate legal effect to the congratulatory clause. That absence is contextual, not dispositive; the authoritative starting point remains what the adopted clause says. But it reinforces the refusal to invent an implementation mandate where the text contains none.

The real-time captioning adds a different kind of evidence: atmosphere and attributed speech. It records emotion around the completed transition, praise for support and technical cooperation, and Mouhamet Diop’s description of AfriNIC as a unique continent-wide institution set up in the interests of the whole continent. Such remarks illuminate what participants hoped the milestone meant. They are not additional words inserted into Resolution 05.26, and Diop’s continental claim is his celebratory assertion, not proof that every African person, government, operator or user appointed AfriNIC.

There is also a documentary caution. The caption transcript’s displayed metadata contains apparent day-and-date inconsistencies. The official minutes and adopted-resolution record establish the meeting date as 8 April 2005. The transcript remains useful for attributed, contemporaneous remarks, but it should not displace the official date and should not be treated as a verbatim-perfect legal record. This is not a minor housekeeping point. Institutional myth often grows when ceremony, recollection and enacted text are blended into one undifferentiated source. Keeping each document in its lane preserves both history and analysis.

Official records, then, have a strong but bounded evidentiary role. They establish exact language, institutional acts, reported claims, evaluation conclusions, documentary chronology and ceremony. They do not self-prove that the institutions describing themselves possessed popular legitimacy, ownership, sovereign authority or wisdom. Those conclusions require an authorization instrument and a lawful basis that the mere existence of official prose cannot supply.

The bookkeeper boundary

AfriNIC’s legitimate institutional core is easier to defend when it is stated plainly. AfriNIC is a private bookkeeper, recordkeeper and coordinator. It maintains registry information, helps protect uniqueness, supports accurate proof about allocations and coordinates the common technical layer needed for network continuity. These functions matter because networks depend on reliable, nonduplicative and intelligible number records. They justify expertise, disciplined procedures and bounded judgment.

They do not confer sovereignty. AfriNIC is not a legislature for Africa, not a territorial authority, not a police or prosecutorial body, not a punitive regulator, not a confiscatory power, not a taxing authority, and not the owner of operators’ networks or assets. Its administrative service region does not become political territory. Its proximity to registry records does not become proprietary title. Its ability to affect an entry does not create a general licence to control the business conduct of the party associated with that entry.

This distinction is the affirmative core of Heng Lu’s Bill of Rights of Uniqueness Coordination and Running-Code Primacy. The common layer should do what the network technically requires: preserve uniqueness, interoperability, proof, security and continuity. It should not acquire discretionary powers simply because the ecosystem has become dependent on its records. Historical habit, repeated institutional language, practical influence and community esteem cannot manufacture authority that no principal delegated.

BTW.Media adds the chronology needed to resist that manufacture. Legal formation, operational handover, ICANN recognition and NRO joinder are separate institutional acts. Service geography organizes administration; it does not turn Internet numbers into territorial property. When those events are collapsed into a founding myth, later readers may imagine a single coronation in which “Africa” transferred a domain to its registry.

The actual sequence is more modest and more defensible: private entities established a service organization, operational arrangements changed, ICANN recognized the registry within its coordination framework, a separate resolution thanked contributors, and a later agreement created NRO membership.

LARUS supplies the operator-side reason this semantic discipline matters. Registry governance decisions can affect allocation, use, reliability, cost and performance in live networks. An entry in a coordination ledger is not abstract to the operator whose routing, financing or customer service depends on it. If ceremonial prestige is inflated into a power to punish, confiscate, veto transfers for extraneous reasons or police commercial conduct, the institution may externalize losses onto networks and customers while invoking “community” as cover.

The party with decision power can then escape liability precisely because the affected parties have been rhetorically dissolved into a collective.

The narrow reading protects AfriNIC as well as operators. A registry burdened with claims of continental sovereignty becomes responsible for conflicts it was never designed or authorized to resolve. Its necessary technical role becomes entangled with political representation, property claims and enforcement demands. By holding AfriNIC to the bookkeeper boundary, the institution can be praised for reliable coordination without pretending to be a government. It can exercise bounded service and contractual judgment without claiming immunity from law or review.

Resolution 05.26 fits perfectly within that boundary. It recognizes labour, celebrates service and states values. Those functions can lower coordination costs by building trust and encouraging continued cooperation. The same reputational capital becomes hazardous only when later actors use it to launder a mandate. The correct response is not to declare the clause meaningless. It is to convert the praise into measurable accountability while refusing the crown.

The strongest case for broader institutional authority

The strongest contrary case deserves to be stated without caricature. Resolution 05.26 was not an offhand compliment. It was a formally adopted Board resolution at the end of a structured process. The four values echoed elements of ICP-2. The application described participation, membership, regional design and public policy processes. The IANA evaluation concluded that all ten criteria were satisfied and reported substantial support. A functioning RIR cannot be a passive filing cabinet: it must make policy choices, apply registration criteria, maintain technical systems, coordinate with peers and exercise judgment.

On this view, the Board placed AfriNIC within a legitimate multistakeholder governance tradition, and the practical authority of that role necessarily reaches beyond mechanical recordkeeping.

Much of that case is correct. Resolution 05.26 is enacted institutional speech and should not be dismissed as empty ceremony. AfriNIC’s work requires judgment, not mere transcription. Private institutions can have legitimate authority over defined matters through contract, membership and voluntary coordination. Normative recognition can create expectations even where it does not use state-style language. The four values should influence how the institution acts.

The error lies in the leap from bounded institutional authority to authority over absent principals. Policy choice inside a registry service is not legislation for a continent. A favourable evaluation is not an appointment by every affected operator. Public participation is not universal consent. Regional design is not territorial jurisdiction. Practical dependence does not create ownership. The operative language remains congratulations and thanks, not grant or delegation. ICP-2 supplies recognition criteria, not sovereign competences. The participation evidence remains split among incompatible denominators.

No state or treaty conferred public power; no instrument in 05.26 identifies subjects, enforcement, remedy or liability.

Nor is the answer to deny all authority. That would erase membership, contract, ordinary corporate competence and the technical necessity of coherent registry decisions. The bounded answer is more exact: AfriNIC may coordinate, keep records, protect uniqueness, apply lawful service rules and manage the internal affairs authorized by its members and agreements. It may not convert those functions into a general power to rule, punish, confiscate or declare ownership. It may not treat the word “regional” as proof that it speaks for every person and institution in the region.

The same limit applies to the NRO, ICANN and the wider technical community. Peer endorsement is evidence of cooperation, not horizontal creation of sovereignty. ICANN could make decisions inside its institutional framework and state what it had evaluated. It could not, by congratulating participants, appoint them as the political principals of Africa. A multistakeholder process can be useful, informed and open without acquiring authority beyond the relationships that support it.

A promise that can be enforced by scrutiny

Resolution 05.26 does not provide a legal enforcement mechanism for its four values. It says nothing about a remedy when representation becomes unrepresentative, coordination expands beyond technical necessity, openness becomes performative, or bottom-up procedure gives way to concentrated control. That silence limits the clause’s direct legal work, but it does not destroy its accountability value.

Public praise creates a record against which institutional conduct can be compared. If AfriNIC invokes the prestige of 2005, it also inherits the burden of explaining how its current practice honours the qualities praised in 2005. “Regional representation” calls for a principal and denominator. “Global coordination” calls for a necessary, auditable function. “Openness” calls for usable records and meaningful response. “Bottom-up self-management” calls for a traceable path from authorized participant to decision, appeal and exit. “Excellence” calls for continuing evidence across executive, registration and technical service.

The evidence limits must remain visible during that scrutiny. The complete identities of all organizers and supporting parties thanked are not established here. The Board supplied no metric for the praised values. Application counts do not share a denominator, and the source record does not independently verify every support letter or claim. The IANA conclusion is authoritative evidence of what the evaluator found, not a complete census. The captioning is contemporaneous but carries metadata and transcription caveats.

The resolution does not settle later policy validity, litigation, succession, property status or changes in corporate governance. Unknowns should remain unknown; silence should never be converted into presumed consent.

This disciplined reading preserves the best of the occasion. People built an institution, completed a difficult transition and supported coordination across a large and diverse service region. The Board chose to thank them. That gratitude can be honoured without transforming it into a myth of origin for powers the text did not give. Indeed, holding the line is the more respectful interpretation: it allows the actual achievement—private, cooperative, technically important institution-building—to stand without borrowing the vocabulary of statehood.

The lasting proposition is therefore double. Resolution 05.26 is more than decoration because its values are standards by which AfriNIC can be judged. It is less than delegation because standards are not powers. The clause promises that a useful private coordinator should remain representative within honest scope, globally cooperative where the network requires it, open in practice and bottom-up among actual principals. It never says the coordinator owns the ledger’s subject matter or rules the people whose networks depend on it.