Summary

  • In October 2003, APNIC, ARIN, LACNIC and RIPE NCC created the NRO as an initially unincorporated coordinating mechanism whose tasks depended on unanimous delegation.
  • The 2004 ASO agreement made the NRO perform ICANN’s Address Supporting Organization functions, but global number policy still had to pass through regional processes and ICANN.

A compact, not a world registry

The signature page of the Number Resource Organization memorandum is dated 24 October 2003. The four signatories were the Regional Internet Registries (RIRs) then in operation: APNIC, ARIN, LACNIC and RIPE NCC. Their agreement did not announce a new pool of addresses or a fifth registry. It set up a joint mechanism for matters the registries chose to delegate.

That distinction mattered because number administration already depended on regional institutions. A global proposal could be useful, but the organizations that served networks and applied regional policies needed a way to coordinate without surrendering every local decision to a new center. The compact’s answer was procedural: define what could be done jointly, specify who could represent the group, and make commitments conditional on agreement among the RIRs.

The agreement said the NRO would begin operating when the last founding registry signed. It would initially remain unincorporated. Legal obligations required prior written commitment from all RIR chief executives. The document also disclaimed a partnership, agency or franchise relationship. These clauses were not decorative legalese. They put a boundary around the new voice: representation did not itself transfer a registry’s rights or bind it to every statement made by another party.

From reform proposals to four signatures

The compact followed a reform discussion rather than appearing fully formed. In 2002, the RIRs responded jointly to ICANN’s evolution and reform process. Their submissions explored a clearer division between policy review and address administration; an October blueprint proposed a “Number Resource Registry.” Those were proposals, not the NRO that the CEOs signed a year later. The November 2003 open letter recounted the sequence and explained why the registries wanted a formal place for joint work.

The letter also named a risk as the RIRs saw it then: if ICANN failed as a private corporation, the unallocated number pool could freeze and disrupt the registries’ work. That was a contingency argument, not a prediction that ICANN would fail. A 2012 independent review later said the contingency mechanism had never been needed. The historical point is narrower: the founding parties wanted continuity and a common external interface, while remaining inside the ICANN framework.

The compact divided the work among three bodies. Each RIR board selected one person for the NRO Executive Council. That council could represent the registries on issues specifically delegated to it. It could commit resources only with unanimous agreement and only to the extent that the registries made those resources available. Its chair rotated annually.

The NRO Number Council had a different composition and role. For each RIR, one member came by board appointment and two were selected through the region’s policy forum. The council advised on proposed global number policies and provided a consultation point. Under the 2003 agreement, a proposal could come from an RIR member; the council checked whether the documented regional procedures had been followed and held a public final comment period before advising on ratification. This created a route for community input, but not a claim that every Internet user directly elected the council or owned the resources it discussed.

A rotating secretariat handled administration and publication. While the NRO remained unincorporated, it could have no compensated employees, although the RIRs could contribute staff, money, equipment and services. The operational design mirrored the legal one: shared work could exist without a permanent central staff or an automatic transfer of each registry’s obligations.

The ICANN relationship changed in 2004

The first NRO memorandum was an agreement among the registries. A second instrument was needed to define the NRO’s relationship with ICANN. In April 2004, ICANN and the NRO announced a letter of intent; the announcement said approval depended on comment periods. The final ASO memorandum was executed on 21 October and posted on 29 October 2004.

That agreement changed the institutional interface. The NRO would fulfil the roles and functions of ICANN’s Address Supporting Organization (ASO), and the ASO Address Council would consist of the NRO Number Council. The new arrangement replaced the 1999 ASO memorandum, its 2001 amendment and LACNIC’s later joinder. Number policy now had a named collective counterpart inside the ICANN framework.

Yet the policy route remained regional before it became global. Under the 2004 agreement, a global policy required agreement through every RIR’s policy-development process as well as ICANN’s agreement; it also had to require a specific action by IANA or another ICANN-related body. The proposal moved through regional processes, common wording was assembled and ratified by RIR boards, the Address Council reviewed whether the process had been followed, and the ICANN Board retained ratification authority. A shared council could verify the path and carry the proposal forward; it did not replace the regional forums that produced it.

There is a small dating wrinkle in the public record. The NRO history page says the RIRs delivered their open letter on 31 October 2003, while the letter webpage is dated 6 November. The records support both a reported delivery date and a page date; they do not explain the interval. The signed memorandum’s date is clear: 24 October.

What the compact did—and did not settle

The NRO compact turned coordination into an institution with named representatives, a secretariat and a global-policy procedure. The 2004 agreement connected that institution to ICANN’s ASO. That mattered because a proposal requiring worldwide number-resource action could no longer be treated as only one region’s decision or only an ICANN Board question. The process had to join regional agreement to global implementation.

The agreements did not establish that the NRO owned Internet numbers, controlled how networks routed traffic, or could override each RIR’s regional policy process. They also did not prove that formally open procedures always produced broad participation. The documents show the design of the authority; they do not measure who attended every forum or how representative every decision was. Note 73 by Heng Lu is useful here only as an analytical question about governance and selection. It is not evidence about the NRO’s creation.

The compact’s practical bargain was more limited, and more exact: the registries could speak together when they agreed to delegate an issue, but the common voice remained accountable to the separate institutions that supplied its mandate and resources. For network operators, that boundary affects where a global address policy can be proposed, reconciled and ratified. The NRO made coordination visible; unanimity kept the coordination conditional.

Sources