Summary

  • AFRINIC began operating as a fully functional registry for the African region on 21 February 2005 [1], but African local internet registries remained legally members of the RIPE NCC under the RIPE NCC Standard Service Agreement until that membership and the agreement were terminated on 31 December 2005 [2][3].
  • The transition therefore ran on two clocks: an operational cutover completed in a single day, and a legal close-out that took another ten months — with couriered AFRINIC contracts [1], a fee-credit arrangement for members who had already paid the RIPE NCC for 2005 [1], and a year-end transfer of unpaid fee claims and membership data to AFRINIC [3].
  • Formal authority over registration and accounting documentation and DNS administration moved earlier, in letters signed by APNIC, ARIN and the RIPE NCC at AFRINIC-2 in Maputo on 27 April 2005 [4][5].
  • The layered structure was documented in financial terms: the RIPE NCC's 2005 annual report records 201 kEUR of unearned revenue from African members at year-end 2004 and states that payments received were transferred to AFRINIC during 2005 [3].
  • None of the located public instruments contains the underlying contract texts themselves: the Standard Service Agreement, the couriered AFRINIC contracts and the data-transfer agreement are known only second-hand through RIPE NCC, NRO, AFRINIC, ICANN and IANA accounts.

Prior BTW coverage of the RIPE NCC to AFRINIC transition has read the 2004–2005 instrument chain as a sequence of recognitions, asked what continuity guarantee the handover did not create, and traced which forum today supervises the registry that received that authority; the linked directory entry for this transition collects that coverage [17]. This article asks a narrower question those pieces left open: what, provision by provision and date by date, the contractual tail actually did.

Between the operational cutover and the legal termination there were more than ten months in which two organisations each held a piece of the same member relationship. Reading that overlap from the available instruments shows where contractual authority persisted separately from operational authority — and why that separation matters when the registry's current governance is contested.

The two clocks

The RIPE NCC's service-announcements archive records the first clock precisely. On 9 February 2005 the RIPE NCC announced that AFRINIC "will begin operating as a fully functional RIR for the African region from 21 February 2005" [6]; on 23 February 2005 it confirmed that the transition was completed and that LIRs in the AFRINIC service region could request IP address space, AS numbers and reverse delegation from AFRINIC and enter objects in the AFRINIC Whois Database [1].

From 22 February the AFRINIC WHOIS was online, the RIPE NCC LIR Portal was disabled for African LIRs, and requests sent to APNIC, ARIN or RIPE NCC hostmasters were redirected to AFRINIC [7].

The second clock runs to the end of the year. The RIPE NCC's own 2005 annual report states that the organisation "ended the membership of all its members from the African continent on 31 December 2005," that the termination was "executed in accordance with the RIPE NCC Articles of Association," that "the RIPE NCC Standard Service Agreement was also terminated for African countries on 31 December 2005," and that all claims for payment of outstanding service fees and all membership data were then permanently transferred to AFRINIC [3].

The same report places co-evaluation of African resource requests between September 2004 and February 2005 and notes that RIPE NCC kept historical data for archiving [3].

Between those clocks sits the interim instrument. The RIPE NCC's retrospective transition page states it plainly: "Until ICANN's final recognition of AFRINIC, LIRs in the African service region were still legally members of the RIPE NCC. All assignments and registrations were done under the terms of the RIPE NCC Standard Service Agreement" [2]. The same page records the practical mechanism: as of January 2005, LIRs in the AFRINIC service region received an AFRINIC contract by courier, and after ICANN's final recognition all services transferred and LIRs needed to sign a contract with AFRINIC to receive services [2].

LIRs that had already paid their membership fee to the RIPE NCC for 2005 did not have to pay AFRINIC for 2005 [2].

What moved when

The date sequence can be stated exactly:

  • 30 September 2004: the ICANN Board gave provisional approval to the AFRINIC application, expecting the transition plan to be completed and a revised application submitted [8][9].
  • September 2004 – February 2005: RIPE NCC and AFRINIC co-evaluated African resource requests, covering more than 400 requests; in early 2005 all data and documentation relating to assignments in the African part of the RIPE NCC service region were transferred to AFRINIC, with essential management software supplied jointly by the RIPE NCC and ARIN [3][7].
  • 21 February 2005: AFRINIC began operating as a fully functional RIR [1][2]; on the same day the NRO Chairman, who was also the RIPE NCC's CEO, and the AFRINIC CEO jointly communicated the NRO's favourable assessment of AFRINIC's readiness for final recognition [10]. Operationally, whois updates from African members were frozen from 14:00 and reverse zones relating to transferred domain objects were frozen at 11:00 UTC, so nserver changes were not reflected in reverse DNS [2][7].
  • 8 April 2005: the ICANN Board recognised AFRINIC as a fully approved and recognised Regional Internet Registry for the Africa service region (resolution 05.25) [9][11]. The IANA report of the same date states that AFRINIC had "demonstrated full capability to migrate existing RIR service agreements to AfriNIC" over the transition period [11] — a capability finding, not a list of executed instruments.
  • 27 April 2005: at AFRINIC-2 in Maputo, APNIC, ARIN and the RIPE NCC signed letters transferring to AFRINIC formal authority for the parts of the region they had previously served, including all registration and accounting documentation and DNS administration; AFRINIC signed a joinder to the NRO Memorandum of Understanding at the same meeting [4][5].
  • 31 December 2005: the RIPE NCC terminated African membership and the Standard Service Agreement for African countries; outstanding fee claims and membership data moved permanently to AFRINIC [3].

Read in order, the sequence shows authority separating into layers that did not all move together. Operational service authority moved on 21 February 2005. Formal custodial authority over documentation and DNS moved on 27 April 2005. Recognition authority attached on 8 April 2005. Contractual authority — the member's legal relationship and the service agreement — remained with the RIPE NCC until 31 December 2005. The financial residue confirms the layering: 201 kEUR of unearned revenue from African members was still on the RIPE NCC's books at year-end 2004, and payments received were transferred to AFRINIC during 2005 [3].

The instruments that are not public

The IANA report's capability language is honest about its own limits: it certifies that AFRINIC demonstrated the ability to migrate service agreements, but does not list the individual instruments or their execution dates [11]. The NRO statement describes the Maputo letters' scope — registration and accounting documentation, DNS administration — without reproducing them [4].

The RIPE NCC's transition page describes the couriered AFRINIC contracts, the Non-Disclosure Agreement and the agreement that transferred data be "collected, processed, and transferred in accordance with the laws applicable [to the RIPE NCC]" [2], but the contract texts themselves do not appear in any located public source. AFRINIC's own meeting minutes record the 27 April 2005 document transfer as a performed event [5], not as contract text.

This gap is not a reason to doubt the accounts; RIPE NCC, NRO, AFRINIC, ICANN and IANA independently describe the same events within consistent dates. But it does mean that what the interim member relationship actually said — remedies, termination rights, liability for registration errors during the frozen transition window — cannot be read provision by provision from public documents. What can be established is the frame: which organisation the member legally owed membership obligations to, which agreement governed registrations, when each of those ended, and what was transferred at the end.

Sources