Summary

  • IANA notices dated 12 April 2005 recorded the allocation of 41/8 and AS36864-AS37887 to AFRINIC, four days after the ICANN Board recognised it as a regional Internet registry. ICANN’s public announcement followed on 14 April; the notice date and announcement date describe different points in the record.
  • The allocations placed 16,777,216 possible IPv4 addresses and 1,024 AS numbers in AFRINIC’s registry-level inventory. They did not amount to simultaneous assignments, guaranteed routes, property deeds, territorial authority or an inherent licence to police and punish network operators.
  • Administrative control was nevertheless substantial. AFRINIC could maintain the regional record, apply its procedures, assess requests and determine the sequence of later issuance. A January 2006 notice that allocations from 41/8 would begin in February shows a roughly ten-month interval between receipt of the block and announced downstream use.
  • April 2005 was AFRINIC’s first allocation of these resource types after recognition, not its first number-resource inventory of any kind. IANA’s current IPv6 registry dates 2001:4200::/23 to 1 June 2004, before full recognition.
  • The durable public value was a coherent uniqueness ledger and a regional distribution function. That role can create economic dependence and operational certainty without making AFRINIC a sovereign, an owner of operators’ networks, or a police force, prosecutor or court.

At the boundary of 41.0.0.0, the public record changed before it can be shown that any network did. On 12 April 2005, IANA notices recorded one IPv4 block, 41/8, and one range of 16-bit Autonomous System Numbers, AS36864 through AS37887, as allocations to AFRINIC. Those entries were operationally important. They gave a newly recognised regional registry fresh inventory from which later requests could be served. But the records do not show sixteen million addresses becoming customer connections that day, or 1,024 networks beginning to exchange routes.

They record the movement of administrative custody in a hierarchy designed to keep number use coherent.

That distinction is the event’s real significance. It avoids two tempting but opposite mistakes. One is to treat an IANA allocation as if it were a deed to a digital territory, with AFRINIC becoming the owner or ruler of everything inside the ranges. The other is to dismiss the transaction as an inconsequential database edit. Neither account survives the evidence.

The registry entry did not grant sovereignty, yet control over a recognised inventory and its downstream issuance could affect when operators gained resources, how their registrations were maintained, and whether other participants could rely on a single, non-conflicting account of who had received what.

Three dates, three institutional steps

The chronology begins on 8 April 2005. At its meeting that day, the ICANN Board adopted resolutions recognising AFRINIC as a regional Internet registry providing IP address registration and related services for the Africa service region. At the same meeting, the Board approved the global policy governing IANA allocations of IPv4 address blocks to regional registries. Recognition supplied the institutional predicate: AFRINIC was now the registry through which new regional inventory would enter the established distribution system.

Recognition was not the allocation itself. Four elapsed calendar days later, on 12 April, two signed-text notices attributed to IANA recorded the separate transfers. One concerned 41/8. The other concerned AS36864-AS37887. The notices described each as AFRINIC’s first allocation of that resource type following recognition. The current IANA IPv4 and ASN registries corroborate the ranges and record an April 2005 date, while the notices preserved in the NANOG archive supply the exact day.

ICANN then made a public announcement on 14 April. It said AFRINIC had received its first allocation of numbering resources after recognition and identified IP addresses and AS numbers. That announcement came two elapsed days after the allocation notices and six days after the recognition decision. It is therefore accurate to say that the selected event was publicly announced on 14 April, but inaccurate to move the allocation notices to that date. Publicity and the underlying recorded act belong in the same sequence, not in the same timestamp.

The distinction is more than archival tidiness. A press notice can explain an event without constituting it. A registry row can preserve a month without revealing the exact transaction time. A signed-text allocation notice can identify a day while leaving internal approval and database timestamps unknown. The record supports a confident sequence—recognition on 8 April, allocation notices on 12 April, public announcement on 14 April—while not supporting a forensic account of the precise hour, request dossier or database operation.

Official documents carry another boundary. The Board minutes prove what the Board resolved. The IANA report proves the assessment and transition work that IANA recorded. The allocation notices prove what IANA announced it had allocated, subject to the unresolved historical verification of their archived signatures. The current registries prove the administrative state they display at the evidence cutoff. ICANN’s announcement proves what ICANN publicly said.

None of those institutional statements becomes, merely because it is official, independent proof that AFRINIC acquired political legitimacy from every African network, property title under every legal system, or sovereign jurisdiction over a continent.

What entered AFRINIC’s inventory

The IPv4 allocation was 41.0.0.0/8, labelled 041/8 in the IANA registry. A /8 fixes the first eight bits of a 32-bit IPv4 address and leaves 24 bits variable. The resulting arithmetic is two to the power of 24, or 16,777,216 possible addresses, spanning 41.0.0.0 through 41.255.255.255. That number measures the mathematical capacity of the block. It is not a count of customers, working interfaces, usable retail addresses, assignments or routes on 12 April.

The ASN allocation ran from 36864 through 37887. Counting both endpoints gives 37,887 minus 36,864 plus one, or 1,024 AS numbers. Again, this is the capacity of an inventory range. It does not show that 1,024 autonomous networks received numbers or operated on the allocation date. AS numbers can identify autonomous routing domains when issued and used, but a block’s placement in regional inventory is upstream of any particular operator’s deployment.

These two ranges occupied different technical categories, yet their institutional movement was parallel. IANA maintained top-level pools and, under the prevailing system, allocated inventory to recognised regional registries. AFRINIC received the capacity at the regional layer. Local registries, resource members and end networks would later request and use portions. Networks participating in BGP would make decentralised decisions about which route announcements to accept, reject and propagate. A global registry entry was an important input into that ecosystem, not a command capable of forcing every router to act.

RFC 2050, the contemporaneous operational guidance later made Historic and replaced by RFC 7020, described the hierarchy from IANA to regional registries, onward to local registries and then to end users. It connected registration with uniqueness and troubleshooting, and expressly warned that allocation did not guarantee routability. That warning is decisive against any account in which IANA’s 12 April notices somehow switched on universal reachability. The sealed record does not identify the first route from 41/8, the first recipient of a portion of it, or the first assignment from the ASN range.

Nor did all the capacity move into downstream hands at once. An AFRINIC notice issued in January 2006 said the registry had received 41/8 in April 2005 and would begin allocating IPv4 space from that block in February 2006. The source gives months, not exact transaction timestamps, so the interval is properly described as about ten calendar months. It nevertheless supplies a concrete separation between custody and onward issuance. For much of that interval, the /8 existed as AFRINIC-held regional inventory rather than as a block already allocated in its entirety to customers or member networks.

This lag reveals the mechanics that a headline can conceal. A top-level allocation increases the stock available to a registry. The registry must then apply procedures, evaluate requests, reserve or sequence capacity as appropriate, enter downstream records and support the coordination services attached to those records. Recipients must configure networks, originate or authorise routes, arrange connectivity and bear the customer and infrastructure consequences of use. Routing peers must decide what to accept. No single step substitutes for the others.

The economic effect therefore travelled through a chain: available inventory, administrative processing, registered issuance, operator deployment and decentralised route acceptance. The fresh /8 and ASN block could reduce dependence on predecessor arrangements and give the regional registry supply to distribute, but the sealed evidence does not quantify a reduction in approval time, administrative cost or operating expense. It also supplies no defensible 2005 market price. Any dollar valuation would require evidence and a method not present in this record; later transfer-market prices cannot simply be projected backwards.

“First” requires a qualifier

The IANA notices used a bounded description: these were the first IPv4 and ASN allocations to AFRINIC after it had been recognised as an RIR. ICANN’s later announcement likewise framed the resources as the first post-recognition allocation. That formulation should be preserved, because a persistent IANA record defeats the broader claim that AFRINIC had never before received number-resource inventory.

The IANA IPv6 unicast registry dates 2001:4200::/23 to 1 June 2004, more than ten months before the April 2005 recognition and paired notices. A /23 contains 512 possible /32 units, although that arithmetic matters here only as a scope marker. This article is not a history of AFRINIC’s IPv6 holdings. The earlier record establishes one narrow proposition: April 2005 cannot accurately be described as the registry’s first resource of any kind.

Transition further complicates any casual use of “first.” Before and around recognition, predecessor regional registries supported the movement of existing records and responsibilities for African networks. The global IPv4 policy approved in April 2005 explicitly separated such transitioned IPv4 space from the new /8 due to a newly recognised RIR. In other words, 41/8 represented new post-recognition inventory, not a relabelling of every address already used by an African operator and not the entirety of the resource base AFRINIC would administer.

That policy distinction is central to the event. A newly recognised registry was to receive one new /8 regardless of projected utilisation, independently of address space transferred from established registries during the formal transition. The rule explains why recognition could be followed quickly by a large top-level allocation without implying that sixteen million immediate end-user demands had already been proved. It also prevents the new block from being folded into a different story about inherited records. The transition and the fresh inventory are related, but they are not the same institutional object.

The ASN record is less complete about procedure. The notice and the persistent registry support the range, recipient and date, but the sealed sources do not expose the 2005 request calculation, the approval criteria or the contemporaneous method by which a block of 1,024 numbers was selected. The inclusive count is certain; the institutional reasoning behind that size remains unknown. A careful account holds both statements at once.

The power AFRINIC actually received

AFRINIC’s role can be understood by separating layers of control. At the global inventory layer, the IANA function maintained unallocated pools, selected blocks under policy, updated top-level registries and allocated inventory to recognised regional registries. At the recognition layer, the ICANN Board identified AFRINIC as the RIR serving the Africa service region within that coordination system. At the regional layer, AFRINIC held inventory, maintained downstream registration, operated coordination services including WHOIS and reverse DNS, and applied its procedures to resource requests.

Below that layer, resource members, local registries and end networks requested resources, configured equipment, served users and bore the capital, migration, customer and operational consequences of deployment. At the routing layer, autonomous networks decided which BGP announcements to accept and propagate. At the public-law layer, states, legislatures and courts retained whatever authority applicable law gave them. The allocation notices did not collapse those layers into AFRINIC.

The controlling rule is straightforward: a registry coordinates a uniqueness ledger; it does not thereby rule the people whose networks appear in that ledger. AFRINIC’s legitimate core in this event was keeping a coherent regional record, preventing conflicting issuance and distributing inventory through a recognised process. The phrase “Africa service region” described the scope of that service. It did not convert the service area into territory owned by the registry or create a political electorate whose sovereignty could be transferred through an ICANN resolution.

The same boundary applies to ownership. Nothing in the checked recognition resolutions, allocation policy, notices, registries or contemporary guidance states that AFRINIC acquired property title to every individual address or ASN within the allocated ranges. Nothing says that it owned the networks, routers, customer relationships or capital deployed by later recipients. That is a bounded finding about these documents, not a universal judgment on every possible contract or national property law. A comprehensive jurisdiction-by-jurisdiction analysis was not part of the record and cannot be inferred from documentary silence.

Punishment power is equally absent. IANA transferred inventory and administrative custody, not the offices of legislature, police, prosecutor and judge. AFRINIC could take narrow technical and administrative actions necessary to keep one registry coherent, subject to the authority and process actually applicable to it. But a later claim to penalise an operator would require a separate contractual or legal basis. It cannot be conjured from the fact that 41/8 and AS36864-AS37887 once entered AFRINIC’s pool.

This is not a detached “lens” placed over otherwise neutral facts. It is the analytical rule needed to state the institutional event truthfully. The ledger records a relationship between a pool and its administrative custodian. It does not manufacture the operator’s physical network, compel the routing system, transfer state jurisdiction or erase the separate economic interests of resource users. Confusing these objects produces false conclusions about what happened on 12 April.

Why administrative custody was not trivial

The strongest contrary case deserves more than a dismissive footnote. AFRINIC was not simply one optional copy of a database. Formal recognition placed it inside the exclusive hierarchy through which new regional IPv4 and ASN inventory was distributed. IANA did not allocate 41/8 to every African operator independently; it allocated the block to AFRINIC. The registry could decide when to begin issuance, assess whether requests met the applicable procedures, maintain recognised allocation records and support reverse-DNS and registration functions on which ordinary network administration relied.

The January 2006 notice makes that control concrete. AFRINIC’s possession of the /8 in April did not force its immediate release. The registry announced the later month in which it would begin allocating from the block. That sequencing power could matter to organisations planning network growth, addressing infrastructure or seeking autonomous routing identities. Accurate registration could matter to troubleshooting and commercial confidence even though it did not guarantee a route. Future top-level eligibility could also depend on how inventory and need were measured under the policy framework.

Administrative dependence can therefore be economically consequential without being sovereign. An operator may own or finance equipment, serve customers and make routing arrangements while still needing a registry to process a request and maintain the recognised record. Delay, error, institutional failure or overreach at that layer can impose real costs. The sealed record does not quantify those costs in 2005, but the control structure explains how they could arise.

Calling the role “custody” must not be used to make it sound passive. Custody here includes stewardship of a scarce and useful inventory, discretion bounded by procedures, control of the sequence of downstream issuance, and responsibility for coherent records. It created a regional administrative dependency and gave AFRINIC practical influence. Operators’ willingness to rely on the shared record could amplify that influence because coordination works best when participants believe that one set of entries will not conflict with another.

Yet dependence is not title, and influence is not law. The fact that a registry’s record is operationally important does not make its corporate entity the owner of the resources in a political sense. The fact that a recognised hierarchy uses one registry as an interface does not grant it jurisdiction over every network or user in its service region. The fact that inconsistent records would be harmful does not authorise the registry to become an all-purpose enforcer.

The correct response to the contrary case is therefore concession with boundaries. AFRINIC obtained real, exclusive administrative control within the IANA-to-RIR distribution chain. That control affected access, timing, provenance and coordination certainty. The documents still do not contain a deed to the range, an automatic route instruction, a transfer of continental sovereignty or a delegation of coercive public power. The event was important for precisely what it was, not for the state-like qualities later rhetoric might project onto it.

A ledger with economic effects

Number registries exist because globally coordinated use benefits from uniqueness. If two unrelated recipients were given conflicting authoritative claims to the same range, network operations and troubleshooting would become harder. A coherent chain from IANA inventory through an RIR record and onward issuance reduces that coordination risk. The value lies in dependable differentiation: participants can see that a resource has moved from a global pool to a regional pool and later to a particular recipient without pretending the record is the network itself.

For African operators, a functioning regional registry could bring request processing, record maintenance and support closer to their service context than predecessor arrangements. The evidence establishes the institutional transition and regional service model, not a measured performance gain. It would be speculative to assign a percentage reduction in latency or cost. Still, the new inventory gave AFRINIC independent post-recognition supply from which it could serve eligible requests, rather than relying solely on transferred records or resources already embedded in earlier arrangements.

The /8’s headline capacity can obscure constraints between potential and use. Some addresses might be reserved or unavailable for particular downstream purposes; procedures would govern issuance; recipients would need technical and commercial reasons to request space; networks would need to configure and route what they received. Thus 16,777,216 is the exact mathematical size of 41/8, not a claim about immediately usable customer supply. The same caution applies to the 1,024 ASNs, which represent an inclusive range rather than 1,024 operating networks.

The event also created institutional exposure. The more operators depend on an accurate registry for allocations, registration, reverse DNS and provenance, the greater the cost if that function becomes unreliable. Continuity of the ledger is therefore a public coordination interest distinct from the perpetual survival of any one corporate gatekeeper. AFRINIC was the responsible institution in this event, but the enduring object worth protecting is the coherent record and the orderly ability to administer it.

That separation matters because institutions can be mistaken for their functions. If the registry corporation and the uniqueness ledger are treated as identical, any challenge to the institution can appear to threaten the existence of the resources themselves, while any assertion by the institution can appear to carry the authority of the whole coordination system. The 2005 record supports neither leap. It shows AFRINIC receiving custody within a system; it does not say the ledger could never be transferred, nor does it specify a successor mechanism for institutional failure.

The operator’s position remains separate. Recipients carry the costs of equipment, staff, customers, renumbering, routing and business interruption. A registry entry can support their use and clarify provenance, but it does not absorb those investments or risks. Political-property language can hide this division by treating a block registered to a regional institution as if the institution owned every downstream productive use. The more accurate account keeps inventory control, registered issuance, network operation and legal rights analytically distinct.

What the record proves—and what it leaves open

The core allocation facts are unusually strong. The two contemporaneous notices identify the exact ranges and date. Current IANA registries corroborate both ranges and the April 2005 registration month. The Board record establishes recognition four days earlier, and ICANN’s announcement explains the event two days later. The global policy explains the special new-/8 rule, the IPv6 registry supplies the pre-recognition exception, and the January 2006 notice demonstrates the separation between receipt and onward allocation from 41/8.

The archived signed-text messages still have a provenance limitation. Their contents are attributed to IANA and align with independent official records, but this research did not complete a historical PGP key-chain verification. It would be wrong to claim that the signatures were cryptographically verified. That uncertainty is material to message-level authentication but less so to the underlying block facts, which the official registries and ICANN announcement independently support.

The internal transaction trail is also absent. No checked source supplies the original requests, an approval dossier, exact database timestamps or a time-zone-normalised execution record. These gaps prevent a minute-by-minute custody chain. They do not undermine the high-confidence conclusion that the notices were dated 12 April and the registries record the blocks to AFRINIC in April 2005.

For 41/8, the first downstream act remains unidentified. The January 2006 notice says allocation would begin in February, but it does not name the precise first recipient, prefix or timestamp, and the sealed record does not contain an independently observed first BGP route. The announced interval is therefore about ten months, not an exact measurement from a known database transaction to a known route event.

For the ASN range, the missing procedure matters if the question is why 1,024 numbers were selected. The record confirms the endpoints and total. It does not reconstruct the calculation or policy applied to the request. A complete transition ledger is similarly missing: sources describe movement of records and responsibilities and show at least one earlier IPv6 block, but they do not itemise every IPv4, IPv6 and ASN resource transferred from predecessor arrangements with precise custody dates.

Legal and financial questions remain bounded. No checked instrument characterises the top-level allocations as conveyances of property title, but the evidence is not a universal survey of private law, member contracts or national legislation. No source provides a reliable contemporaneous market or shadow price, so the blocks’ 2005 dollar value is unknown. No complete sample of request decisions, exceptions and appeals establishes exactly how much discretion AFRINIC exercised in practice during 2005 and 2006.

These uncertainties should shape language, not paralyse judgment. We can say that AFRINIC received the ranges; we cannot say when every internal keystroke occurred. We can calculate capacity; we cannot equate it with deployed use. We can identify a documentary absence of title and sovereignty; we cannot issue a worldwide property-law ruling. We can recognise administrative dependence; we cannot attach an invented price to it. Precision is not timidity. It is what prevents the evidence from being made to carry claims it never contained.

The exact institutional fact

The 12 April allocation was the first clean demonstration of AFRINIC’s new post-recognition supply role. The 8 April resolutions had identified the registry within the coordination system. The allocation notices then placed fresh IPv4 and ASN inventory under its administration. The 14 April announcement made that change public. The later 41/8 notice showed that inventory custody preceded downstream release.

What changed was the control surface of the uniqueness system. IANA remained responsible for the top-level pool and global registry. AFRINIC became responsible for regional inventory and subsequent records and procedures. Recipients would control deployment. Autonomous networks would control route acceptance. States and courts retained distinct legal authority. This division made coordinated supply possible without requiring a fiction that one institution owned the Internet’s operations across Africa.

The allocation thus created neither a kingdom nor an empty symbol. It gave AFRINIC consequential but bounded administrative custody: enough power to affect supply, sequence and certainty, but not a mandate to rule, own or punish. That is the narrow fact the 2005 record can bear, and it is more illuminating than either exaggeration available to it.