Summary
- Address governance had extensive pre-1999 ancestry: IANA and the central Internet Registry, the IAB, federal and intercontinental bodies, RIPE and the RIPE NCC, APCCIRN/APNG and APNIC, InterNIC, ARIN, and recurring cooperation among registries.
- Those institutions drew authority from different sources—technical appointment, federal sponsorship, regional agreement, administrative delegation, service contracts, or corporate membership. Their participants, applicants, members, operators, and number holders were not one constituency.
- Two documented trails show proposals becoming regional arrangements in stages, but neither RFC publication nor registry operation supplies a holder-wide mandate. Some acceptance and implementation steps survive only in retrospective institutional accounts and must remain qualified.
- Review existed before the ASO: RFC 2050 prescribed hierarchical appeals, and the RIPE NCC had a regional arbitration procedure from January 1998. Neither mechanism created a holder-selected global reviewer with authority over IANA or every RIR.
- “No prehistory” is defensible only in a narrow sense. No evidenced predecessor combined global address-policy advice with the 1999 instrument’s RIR-based selection, voting, ICANN Board appointment, and removal circuit; even that instrument did not create direct holder sovereignty.
Section 2 of the founding ICANN-ASO Memorandum of Understanding allowed each signing regional Internet registry to remove one of the Address Council members it had selected, provided the decision came through an open and transparent regional process. Nine years earlier, RFC 1174 had proposed a consequential but different chain: the Internet Activities Board recommended; the Federal Networking Council received the recommendation; the Internet Assigned Numbers Authority and Internet Registry would retain central functions; and the Internet Registry would delegate blocks to organisations approved by the Coordinating Committee for Intercontinental Research Networking.
Both records allocated institutional roles. The later instrument joined those roles to a published circuit for selecting and removing members of a global address-policy council.
Address governance itself was already mature by October 1999. Europe had built RIPE and a staffed coordination centre. The Asia-Pacific region had established APNIC. North American number registration had moved through InterNIC to ARIN. Federal agencies, technical boards, research-network bodies, registries, local registries, service providers, and operators had coordinated address distribution across borders for years. By November 1996, RFC 2050 could describe an operating hierarchy of IANA, regional registries, and local registries, along with shared allocation guidelines and an appeal route.
The narrower inquiry concerns the source and reach of authority. Which bodies possessed technical competence or delegated administrative power? Which offered access to participants or corporate rights to members? Which were authorised by a defined population of operators or number holders to appoint, instruct, review, or remove the people administering addresses? Those questions lead through overlapping histories rather than one institutional line.
Four propositions hide inside “prehistory”
The first proposition is ancestry. Institutions performed functions that the ASO would later encounter. IANA allocated identifiers and recognised delegated registries. The central Internet Registry processed and recorded number assignments. The IAB issued architectural and policy recommendations. Federal and intercontinental bodies coordinated sponsors and research networks. Regional forums developed administrative practices. Regional registries allocated resources and maintained records.
The second is routine coordination. Proposals circulated; regional institutions formed; address blocks moved into delegated administration; allocation criteria were compared; and registry staff worked across institutional boundaries. The July 1995 IEPG meeting minutes, item 13, a contemporary operational record, document Mark Kosters presenting work on the successor to RFC 1466: classless allocation, upstream-provider addressing, gradual allocations, reassignment information, utilisation thresholds, audits, and distributed registration services. This was active policy coordination with practical consequences.
The third proposition is representation. An engineer at an IEPG meeting, an Internet Society member, an APNIC member, a federal official, a registry applicant, and a listed network contact occupied different positions. Knowledge, participation, corporate voting, service use, and authority to act for all affected organisations require separate evidence.
The fourth is independently enforceable review. Here the question is whether an affected organisation could obtain reconsideration outside the administrative chain that made the decision, or remove an administrator through a constituency-based process. Several pre-1999 institutions supplied review or removal within bounded jurisdictions. RFC 2050 specified appeals to parent registries. RIPE NCC members could dismiss their Executive Board and use a service-related arbitration process. Successive IAB procedures introduced nomination, confirmation, and recall rights for their own defined constituencies.
These four propositions set the method for the rest of the inquiry. Functional ancestry can coexist with fragmented representation. Repeated coordination can operate through delegation rather than election. A regional corporate remedy can be valuable without extending globally. Missing rosters, case files, or eligible-population counts limit measurement; they leave informal oversight, sponsor control, professional constraint, and bilateral escalation open as historical possibilities.
What the October 1999 instrument actually added
The surviving ICANN-ASO Memorandum of Understanding carries two dates that belong to different records. Its execution block says that it was executed on 18 October 1999 by ICANN, APNIC, ARIN, and the RIPE NCC. The ASO’s retrospective institutional chronology identifies 19 October 1999 as the date of formal establishment and signing. Attribution preserves the distinction without inventing a reconciliation.
The MoU’s first section defined the ASO as a consensus-based advisory body within ICANN, created an Address Council, and required an annual open General Assembly. Section 2 assigned each of the three signing RIRs the selection of three Address Council members. The procedure required public nominations, publication of willing nominees, an open and transparent regional selection, and exclusion of RIR employees from council seats. It specified terms, majority voting for ordinary council action, a quorum representing at least two-thirds of the signing RIRs, and removal by the selecting RIR through an open and transparent regional process.
Sections 3 and 4 separated two further capacities. The Address Council appointed people to designated ICANN Board seats from candidates produced through an open call and RIR nominations. Once appointed, those people served as full ICANN directors rather than instructed ASO delegates. The council also advised the ICANN Board and considered global policies concerning address space, autonomous system numbers, and related reverse-DNS spaces. A proposal required support from at least two-thirds of the Address Council before reaching the ICANN Board.
Sections 5 and 6 required an open General Assembly at least annually, public formal communications, publicly archived policy discussions, advance agendas, and published minutes, subject to protection of confidential allocation information. Section 7 placed contracts between ICANN and individual RIRs beyond the ASO’s remit. The institution thus combined public advisory and appointment functions with a clear perimeter around regional registry business.
Section 9 contained the instrument’s explicit representation criteria. A proposed RIR was expected to demonstrate broad support among ISPs in its region, include a “significant percentage” of the regional ISPs that would receive assignments from it, maintain procedures open to interested parties, and ensure fair representation of regional constituents. These were formal conditions rather than measured results. The text supplied neither a numerator nor an eligible-population denominator for “broad,” “significant,” or “fair,” and it established no one-holder-one-vote franchise.
The ASO’s retrospective says that a functioning global-policy system among RIRs preceded the organisation. That institutional account is important counterevidence to a creation-from-nothing narrative, although it cannot reconstruct every participant in every regional decision. The 1999 instrument was later superseded by the 2004 ICANN-NRO arrangement; that bounded note prevents the earlier design from being mistaken for the present structure.
The innovation lay in the combination: RIR selection of a global council, council voting on global advice, council appointment of ICANN directors, and RIR removal of council members. Address holders did not acquire ownership of the system, individual allocations remained outside the council’s review jurisdiction, and the selecting intermediaries were the RIRs rather than a universal electorate.
The central registry branch rested on delegation
The contemporary starting point is RFC 1174, IAB Recommended Policy on Distributing Internet Identifier Assignment and Connected Status, issued in August 1990 as an informational statement of the IAB’s official view rather than an Internet standard. Its overview says that it transmitted two recommendations from the IAB chair to the FNC chair. Sections 1.2 and 1.3 capture the institutional arrangement at that moment.
IANA, performed at USC’s Information Sciences Institute, possessed discretionary authority to delegate parts of identifier administration. Number and autonomous-system registration work had been lodged with the Internet Registry at SRI International’s Network Information Center. The proposed method retained both central functions. The Internet Registry would remain the principal registry, maintain central records, allocate blocks to organisations approved by CCIRN, and delegate further assignment authority. Candidate registries were expected to meet IANA and the Internet Registry and document their procedures.
RFC 1174 recommended that method. It recorded IANA’s existing delegation discretion and the Internet Registry’s existing function, while leaving approvals and particular delegations to subsequent action. Applicants supplied information to the registry, and network contacts maintained records. Selection of the IAB, the IANA operator, and the registry contractor followed separate institutional routes.
The administrative system still carried practical force. Unique identifiers lose value when allocated inconsistently. Registries could refuse, reduce, refer, or audit requests. Routing operators independently determined which routes they would accept, so registration and reachability remained distinct. Administrative judgement, routing choice, sponsorship, and professional relationships constrained the system from different directions.
The institutional setting changed with InterNIC. ARIN’s retrospective history says that Network Solutions received the Internet Registry function before NSF originated InterNIC in 1993 under a cooperative agreement covering IP-address and autonomous-system registration. The U.S. Government Accountability Office’s official decision B-327398, dated 12 September 2016, separately records that the NSF-Network Solutions cooperative agreement became effective on 1 January 1993 and supported InterNIC services. The GAO decision date is 12 September 2016; 1 January 1993 is the effective date of the agreement described in that decision.
InterNIC’s applicants used a registration service. NSF sponsored the arrangement, Network Solutions performed the contracted work, IANA retained a coordinating role, and applicants and contacts dealt with registration staff. Contractual oversight, administrative escalation, technical coordination, and professional discipline could all shape performance. Collective appointment or removal of the contractor by the worldwide population of number holders lies outside the rights recorded in these instruments.
The IAB’s selection rules changed repeatedly
The IAB is a genuine ancestor of the ASO’s policy-advice function, but the people who selected its members and the procedures they followed changed substantially. The record supports one early snapshot followed by four bounded procedural regimes.
Appointment by the existing board in May 1990
RFC 1160, The Internet Activities Board, published by Vint Cerf in May 1990 as an informational history and description, records the procedure then in force. Section 2 describes the IAB as a coordinating committee for Internet design, engineering, and management. It set standards, managed the RFC process, reviewed the IETF and IRTF, undertook strategic planning, and resolved technical questions.
At that date, the chair appointed new IAB members with the advice and consent of existing members; the members elected the chair. RFC 1160 listed professional affiliations while characterising members as researchers and professionals concerned with the Internet’s technical evolution. Employer identity provided context rather than a recorded instruction derived from address holdings.
This evidence establishes a May 1990 snapshot. It supplies the procedure observed at that date, not a continuous appointment series through August 1992. Selection was internal to the IAB, and the affected population of address users was neither enumerated nor given a vote in the document.
Internet Society petitions from August 1992 to March 1994
RFC 1358, Charter of the Internet Architecture Board, issued in August 1992, introduced another arrangement. Section 2 stated that IAB members served as individuals rather than organisational representatives. Nominations could come from the IAB, the Internet Society president, the Society’s Board of Trustees, or a petition signed by at least one per cent of current Internet Society members, capped at 150 signatures when membership exceeded 15,000. The trustees approved nominations by a three-fifths vote.
Removal was also specified. A four-fifths vote of trustees could replace a member in the Society’s interests. A petition signed by five per cent of voting Internet Society members could trigger replacement, subject to confirmation by a majority of trustees. Trustee review occurred at three-year intervals.
Those provisions created concrete nomination and removal rights for Internet Society members. Operators, registry applicants, and address holders formed other populations. RFC 1601 replaced this charter in March 1994.
IETF nomination from March 1994 to October 1996
RFC 1601, Charter of the Internet Architecture Board, issued in March 1994 as an informational document, replaced RFC 1358. Under §1.1, the IETF nominating committee nominated voting IAB members and the Internet Society Board of Trustees appointed the twelve full members. The committee consisted of a chair designated by the Internet Society, seven people selected randomly from volunteers who had attended two IETF meetings during the previous two years, and non-voting institutional liaisons. IAB members continued to serve as individuals.
RFC 1601 left behind the Society-member petition mechanism for recalling full IAB members. It did provide for internal removal of the IAB chair by a two-thirds vote of IAB members. Selection now rested on recent IETF meeting participation, random choice for the nominating committee, and trustee appointment.
RFC 2027 from October 1996 to February 1998
RFC 2027, IAB and IESG Selection, Confirmation, and Recall Process, became Best Current Practice 10 in October 1996. Sections 2–4 described a nominating committee with a non-voting chair appointed by the Internet Society president, ten voting volunteers selected randomly from a pool of people who had attended at least two of the previous three IETF meetings, and two non-voting liaisons. Internet Society trustees, sitting IAB members, and sitting IESG members were excluded from the volunteer pool. Any member of the IETF community could nominate any community member, including through self-nomination. The Internet Society Board of Trustees confirmed IAB candidates, with agreement from at least half of the sitting confirming body required for confirmation or rejection.
Section 5 allowed anyone to request recall of a sitting IAB or IESG member by submitting a written justification to the Internet Society president. The president appointed the recall committee chair while the merits remained with the committee. A body constituted under the nominating-committee rules investigated, heard from the member concerned, consulted third parties, and required three-quarters of those voting to recall the member.
This regime ran from October 1996 to February 1998, when its successor expressly obsoleted it. Its constituency remained rooted in the IETF community, recent meeting attendance, and Internet Society confirmation.
RFC 2282 from February to the end of 1998
RFC 2282, IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees, became BCP 10 in February 1998 and expressly obsoleted RFC 2027. It retained the principal architecture: a non-voting chair appointed by the Internet Society president; ten voting volunteers randomly drawn from people who had attended at least two of the previous three IETF meetings; public calls for volunteers and nominees; nomination of IETF community members by others or themselves; trustee confirmation of IAB candidates; and recall initiated by anyone through a justified request.
The confirming body still needed agreement from at least half of its sitting members. Recall continued through a committee created under the nominating-committee rules, with the requester and subject excluded from membership and a three-quarters vote required for removal.
Section 6 identifies the changes from RFC 2027. The previous year’s nominating-committee chair became a third non-voting liaison. The chair had to announce the eligible volunteer pool before random selection and publish in advance the method by which the ten voting members would be selected. That method had to be independently verifiable as fair and unbiased. Further guidance called for consultation with a broad base of the IETF community and clarified responsibility for reviewing an appropriate half of the IAB and IESG positions each year.
RFC 2282 governed from February 1998 through the end of 1998 for the period examined here. Its transparency provisions improved the inspectability of selection while preserving the materially continuous IETF-based constituency. Across the five documented snapshots and periods, the IAB moved from internal appointment to Internet Society petitions and then to IETF nomination, trustee confirmation, and formal recall.
Federal coordination changed shape in 1990
RFC 1160 distinguishes federal periods that a combined “FNC/FEPG since 1988” label would obscure.
Before 1990, key managers from DARPA, NSF, the Department of Energy, NASA, and other federal organisations formed the informal Federal Research Internet Coordinating Committee. FRICC coordinated government support for Internet development and sponsored much of the research described in the RFC. Its observed constituency consisted of federal organisations and programme managers responsible for networking research and development.
RFC 1160 says that FRICC was reorganised in 1990 under a wider federal science-and-technology initiative, creating the Federal Networking Council and its working groups. The FNC included former FRICC members and additional U.S. government representatives. It coordinated agencies supporting the Internet and linked their work to federal science policy. Its constituency was agency-based from 1990 onward.
The Federal Engineering Planning Group enters the address record at a more precise point. RFC 1466, Guidelines for Management of IP Address Space, issued in May 1993 as an informational proposal, says in its abstract that the FEPG reviewed the document on behalf of the FNC. That establishes a technical-review role for the group in the May 1993 policy episode. A complete membership rule, appointment procedure, and removal instrument remain unknown.
These bodies could influence sponsored programmes and technical arrangements through government authority and programme responsibility. Their decisions applied through that institutional remit. Global applicants occupied a different constituency, while sponsor oversight and other federal controls would require additional period-specific records to measure.
CCIRN and IEPG made international coordination operational
RFC 1160 describes the Coordinating Committee for Intercontinental Research Networking in its 1990 setting as including the FNC and counterparts in North America and Europe. It was co-chaired by the executive directors of the FNC and RARE and served cooperative planning among major research-networking bodies.
RFC 1174 §1.3 assigned CCIRN a proposed gatekeeping function: the Internet Registry would allocate blocks to organisations that CCIRN approved. That recommendation made intercontinental approval part of the proposed distribution architecture. Particular approvals and delegations still depended on later records.
The RIPE 7 minutes, 13–14 November 1990, items 7 and 8 add contemporary detail. They report that a European CCIRN delegation had been selected and that RIPE would be represented. They also record a shift toward treating CCIRN members as experts covering fields rather than delegates of specific networking organisations. The document identifies institutional participation without supplying a complete electorate or a measurable share of affected operators.
The same minutes describe the first IEPG meeting at Santa Fe on 22–24 October 1990. Participants presented the networks they represented; CCIRN approved revised terms describing IEPG as a technical body; and its tasks included registries, global address-registration coordination, routing, DNS, operations, and coordination among network information and operations centres.
By July 1995, the IEPG meeting record shows participants discussing registry guidelines, routing records, APNIC operations, and a successor to RFC 1466. The minutes identify attendees, affiliations, recommendations, and active technical work. They reveal international reach and policy consequence, while eligibility, participant instructions, and the full population of affected operators remain outside the record.
Europe joined operator access to corporate control
Europe provides the strongest counterexample to any sweeping claim that regional administrators operated without accountability.
RIPE-001, RIPE Terms of Reference, published on 29 November 1989, created a forum for administrative and technical coordination of pan-European IP networking. It encouraged all parties operating wide-area IP networks to participate, promoted interconnection, sought agreement on common operating practices, and required RIPE documents to be public. Collaborating networks retained executive authority within their own organisations.
That was an invitation to an identifiable class—operators of wide-area IP networks—rather than a corporate electorate. Its significance lies in access, deliberation, publication, and the agreements participants pursued. Total eligibility and attendance at particular decisions were unmeasured.
RIPE-019, RIPE Network Coordination Center, published on 16 September 1990, was explicitly a proposal. Sections 2–4 placed a prospective NCC inside RIPE: RIPE would define tasks, the centre would report to RIPE, participating organisations would contribute work, and RIPE would review operations. The proposed centre would act as a delegated registry, allocate blocks to local registries, collect registration information, and coordinate with the central Internet Registry.
Acceptance unfolded in identifiable steps. The RIPE 8 minutes, 27 February–1 March 1991 record agreement that the NCC should be centralised and that a legal host should be sought, preferably RARE. RIPE-039, Procedures To Set Up The RIPE NCC, published on 10 June 1991, says RIPE 8 decided to ask RARE to provide the legal environment and that the RARE Council of Administration accepted the request on 16–17 May 1991. The RIPE 9 minutes, 11–13 June 1991 record formal approval of the NCC activity plan and approval in principle of the setup paper.
This sequence contains a proposal, regional agreement, legal-host acceptance, and organisational implementation. RFC 1466 adds evidence of working practice: by May 1993, the RIPE NCC had received a Class C block and agreed to apply the RFC’s allocation guidelines. Authority accumulated through several institutions rather than a single regional vote.
The corporate phase introduced another set of rights. RIPE-176, RIPE NCC Articles of Association, was published on 25 November 1997, while its introduction says that the Dutch articles were deposited with the Amsterdam Chamber of Commerce on 12 November 1997, formally establishing the association. Legal establishment and publication therefore occurred on separate dates.
Articles 7 and 8 provided for member nomination of Executive Board candidates, with written support from at least five members, followed by appointment at the General Meeting. The General Meeting could suspend or dismiss a board member at any time by at least two-thirds of votes cast. Articles 15 and 16 vested residual powers in the General Meeting, allowed members holding at least two per cent of possible votes to place resolutions on the agenda, and assigned votes by membership category: one vote for enterprise and small members, two for medium members, three for large members, and a formula for supranational members. Corporate voting was therefore weighted by category.
Article 11 required the Executive Board to adopt an arbitration procedure for disputes over management decisions under standard service agreements after consulting members. The contemporaneous RIPE-174, RIPE NCC Conflict Arbitration Procedure, version 1.1 dated 25 November 1997, says that the procedure had been approved by the Executive Board and would take effect when the association began providing RIPE NCC services on 1 January 1998. It covered service-related conflicts between contributors and the RIPE NCC and between contributors. Each party selected an arbiter from an approved pool; those arbiters could choose a third; and the procedure set time limits for rulings.
By January 1998, Europe therefore possessed several distinct controls: open RIPE participation, corporate appointment and dismissal of the RIPE NCC board, General Meeting powers, service-related arbitration, and hierarchical allocation appeal under RFC 2050. Each applied to a particular kind of decision. The available records leave the arbitration docket, outcome rate, and enforcement history unknown, but the procedure itself was operative within the RIPE NCC service jurisdiction.
Asia-Pacific authority accumulated in phases
The early Asia-Pacific sequence is documented partly through later institutional reconstruction, so its strongest findings concern the stages that can be identified rather than a complete regional electorate.
APNIC’s official retrospective, The Asia Pacific Network Information Centre—1993–2013, reconstructs a January 1993 APCCIRN meeting in Honolulu at which attendees discussed and accepted a regional NIC proposal. It says the updated pilot was adopted at the September 1993 APCCIRN meeting, began operating on 1 September under APCCIRN’s auspices with JPNIC support, and was expected to report back to that body. The history also attributes to IANA a public recognition of APNIC on 1 April 1994 through delegation of 202/8 and 203/8.
The retrospective cites earlier minutes and project documents, but the underlying January decision record and IANA delegation notice are absent from the records examined here. The exact selector, eligible population, form of the first acceptance, and administrative terms of delegation therefore remain attributed to APNIC’s reconstruction. RFC 1466 independently supplies the proposed central-to-regional architecture.
The same retrospective preserves a February 1995 organisational account. It says APNIC’s own description traced pilot authority first to APCCIRN and then to APNG, while acknowledging that APNG was informal, lacked legal authority, and did not claim to represent the whole region. According to that reconstruction, APNIC’s consultative committee looked to IANA as the source of administrative authority. This describes how APNIC understood its early warrant; it offers no measured regional assent.
Contemporary operational evidence is firmer. The July 1995 IEPG minutes, item 11 report that APNIC was issuing autonomous system numbers and operating a small routing registry while considering coordination with other registries. Those activities establish use of a delegated regional service. The motives and full population of organisations relying on it remain unknown.
Corporate and membership stages then added formal rights. The archived APNIC By-laws, APNIC-087 version 001, originally published in June 1998, say that APNIC Pty Ltd’s directors created the APNIC special committee on 24 June 1998. They also record an earlier Seychelles body established on 18 May 1996 and specify that membership in that body conferred no automatic rights under the June 1998 rules.
Under the June 1998 version, paid members could elect Executive Council members, review or amend council decisions by a two-thirds vote of the entire membership, and petition for special meetings. Voting strength varied by membership tier. The first five-person Executive Council was appointed by the Director General. At the first annual meeting, members would elect four people—two replacing initial members and two expanding the council—while later seats would be filled through member nominations and elections. Removal of an Executive Council member required two-thirds of the votes of the entire paid-up membership.
These were substantial corporate controls for members qualified under the by-laws. National registries, downstream customers, legacy holders, operators, and end users formed overlapping but different populations. APNIC’s retrospective places the first explicit formal policy-development document after the period examined here. The pre-1999 picture is consequently one of operational delegation joined by developing membership governance, with early selection and policy procedures only partly recoverable.
ARIN changed regimes during 1997 and 1998
North American regionalisation passed through several governance stages in a short period.
The underlying federal record is locatable. The draft minutes of the FNC Advisory Committee meeting of 15 April 1997, agenda item 5, pages 12–13 identify Randy Bush, then a member of ARIN’s proposed Board of Trustees, as the presenter. The minutes attribute to him the description of IP addresses as a “public trust of a finite resource” and ARIN as a proposed nonprofit counterpart to APNIC and the RIPE NCC. The statement came from an institutional proponent presenting to the committee rather than from a formal FNCAC determination about title or authority.
ARIN’s Articles of Incorporation record the original filing of 18 April 1997 and amendments through 7 August 1997. ARIN’s institutional history supports the month-precision statement that it began operations in December 1997.
The 30 June 1998 amended by-laws placed corporate authority and operating procedures with the Board, while allowing implementation to be assigned to the president. The Advisory Council acted “purely in an advisory capacity.” Its first members were nominated and elected by the Board. Within twelve months of incorporation, the Board was required to submit a revised process to the general membership for approval, including member nomination and election of Advisory Council members, while retaining oversight of that process.
Removal changed between two dated records. The Advisory Council minutes of 21 June 1998, under “Bylaw Changes” record that the existing by-laws contained removal rules for officers and trustees while omitting Advisory Council members. The council debated and recommended amendments. That omission describes the rules as observed on 21 June.
The Board minutes of 30 June 1998 record adoption of two independent routes. First, an affirmative vote by a majority of the voting members of the full Advisory Council could remove an Advisory Council member, with notice and an opportunity for the member to participate in the meeting. Second, four-fifths of all voting trustees then in office could separately remove an Advisory Council member. Each body therefore possessed its own removal route after 30 June. The council’s advisory role in policy and the Board’s general fiduciary authority remained analytically distinct from these member-removal procedures.
Member election became practical later that year. The ARIN II Members Meeting record of 16 October 1998 describes a forthcoming election to fill Advisory Council seats, with each member organisation receiving one vote for each vacancy. It identifies a defined corporate electorate at a defined time. Applicants, nonmembers, legacy holders, and other affected operators remained separate populations.
ARIN thus supplies real evidence of regional accountability in formation. Its first council was board-selected; the by-laws required a transition toward member nomination and election; the council advised on policy; the Board retained corporate authority; and, after 30 June, a majority of the voting members of the full Advisory Council could remove a council member while four-fifths of all voting trustees then in office held a separate removal route.
A compact matrix of authority, remedy, and unknowns
The matrix keeps seven questions separate: who selected the body; what status its output held; who implemented it; how an individual decision could be reviewed; how officers or members were appointed or removed; whether the body controlled IANA or another RIR; and which constituency measurements remain unknown. Each row carries its operative locator. “Unknown” marks a documentary gap rather than a finding about informal practice.
| Body and sourced period | Selector and eligible constituency | Output and status | Implementation actor | Individual-decision review | Internal appointment or removal | Power over IANA or another RIR | Denominator or unknown |
|---|---|---|---|---|---|---|---|
| IANA and central IR, RFC 1174 §§1.2–1.3, August 1990 | Sponsored technical and contractual arrangements; applicants used registry services | Informational IAB recommendation plus recorded delegation and registration roles | IANA at USC-ISI; IR at SRI-NIC | Unknown in this source | Holder route unstated | IANA held delegation discretion | Applicant, objection, and holder populations unknown |
| IAB, RFC 1160 §2, May 1990 snapshot | Chair appointed with existing-member consent; members elected chair | Technical, architectural, and policy decisions | IAB and subsidiary bodies | Allocation review outside stated remit | Internal appointment and chair election | Policy influence; corporate registry power unstated | Snapshot only |
| IAB, RFC 1358 §2, August 1992–March 1994 | IAB, ISOC president, trustees, or qualifying ISOC-member petition; trustees approved | Informational charter | IAB and technical bodies | Allocation review outside stated remit | Trustee removal; ISOC-member petition route | RIR authority unstated | ISOC membership was the defined constituency |
| IAB, RFC 1601 §1.1, March 1994–October 1996 | Seven recent-IETF attendees selected by lot; ISOC trustees appointed IAB | Architecture and standards oversight | IETF NomCom, trustees, IAB | Allocation review outside stated remit | IAB could remove its chair; full-member recall unknown | IAB designated IANA; RIR corporate control unstated | Eligibility rested on IETF attendance |
| IAB, RFC 2027 §§2–5, October 1996–February 1998 | Ten recent-IETF-attendee volunteers selected randomly; ISOC president appointed chair; trustees confirmed | BCP 10 selection, confirmation, and recall | NomCom, trustees, recall committee | Allocation review outside stated remit | Anyone could request recall; three-quarters vote required | RIR corporate authority unstated | Volunteer pool was IETF-based |
| IAB, RFC 2282 §§2–6, February–December 1998 | Same ten-volunteer IETF pool; pool and random method announced; trustees confirmed | Revised BCP 10; expressly obsoleted RFC 2027 | NomCom, trustees, recall committee | Allocation review outside stated remit | Anyone could request recall; three-quarters vote required | RIR corporate authority unstated | Added liaison and selection transparency; constituency materially continuous |
| FRICC, RFC 1160 introduction, pre-1990 | Federal networking programme managers | Informal federal coordination and sponsorship | Participating agencies and programmes | Unknown | Agency procedures unspecified | Global registry authority unstated | Complete roster and terms unknown |
| FNC, RFC 1160 introduction, from 1990 | U.S. federal agencies and representatives | Inter-agency coordination | Agencies and supported programmes | Global allocation appeal unknown | Federal institutional controls | Influence over sponsored functions | Global operators lay outside the agency constituency |
| FEPG, RFC 1466 abstract, May 1993 episode | Selector unknown; reviewed for FNC | Technical review supporting an informational proposal | FNC-related engineering participants | Unknown | Unknown | Independent authority unstated | Roster, vote, and eligible population unknown |
| CCIRN, RFC 1160, RFC 1174 §1.3, and RIPE 7 items 7–8, 1990 | Research-network bodies and regional delegations | Cooperative planning; proposed candidate-registry approval | Member bodies and, where accepted, IANA/IR | Unknown | European delegation documented; wider rules incomplete | Proposed approval gate for candidate registries | Operator and holder denominator unknown |
| IEPG, RIPE 7 item 8, October 1990 and July 1995 minutes | Technical participants and institutional representatives | Operational coordination and recommendations | Registries and operators choosing to implement | Unknown | Removal instrument unknown | Corporate registry authority unstated | Minutes identify attendees rather than an eligible electorate |
| RIPE, RIPE-001, November 1989 and RIPE-019 §§2–4, September 1990 | Participation invited from wide-area IP operators | Regional agreements and proposed NCC task definition | Participating networks; later NCC staff | Discussion and RIPE review | Open forum rather than closed corporate electorate | IANA authority unstated | Eligible and participating counts unknown |
| RIPE NCC under RARE, RIPE 8, 1991, RIPE-039, RIPE 9, and RFC 1466, May 1993 | RIPE defined tasks; RARE supplied legal setting | Delegated regional registry and coordination centre | NCC staff and local registries | Hierarchical escalation; regional details varied | RIPE review rather than association voting | Operated within central delegation hierarchy | Operator, local-registry, and holder counts unharmonised |
| RIPE NCC association, RIPE-176 Arts 7, 8, 11, 15–17 and RIPE-174, effective 1 January 1998 | Members nominated; General Meeting appointed board | Dutch association with weighted voting | Board, management, registry staff | RFC 2050 appeal plus service arbitration | General Meeting could dismiss board by two-thirds cast | Other-registry removal power unstated | Members were service parties rather than all affected users |
| APCCIRN/APNG and APNIC pilot, APNIC retrospective pp. 3–8, 1993–1995 | APCCIRN acceptance and IANA delegation attributed retrospectively | Regional pilot and administration | APNIC staff and national registries | Complete procedure unknown | APNG legal capacity qualified in reconstruction | Relied on IANA delegation | Underlying first decision and delegation notice unavailable |
| APNIC earlier membership phase, APNIC retrospective and APNIC-087 savings clause, 1996–June 1998 | Earlier corporate and membership arrangements | Developing regional administration | Secretariat and council structures | Remedy details unknown | Earlier membership conferred no automatic June 1998 rights | Other-RIR authority unstated | Membership, attendance, and holder populations differed |
| APNIC under APNIC-087, June 1998 | Paid members by tier; first council appointed, later seats elected | Member governance; council managed between meetings | Executive Council and Director General | Allocation review incompletely documented | Two-thirds of entire paid-up membership could remove a council member | Other-registry authority unstated | Weighted membership was not a regional census |
| InterNIC, GAO B-327398 and ARIN history, 1993–December 1997 | NSF cooperative agreement with Network Solutions | Contracted registration service | Network Solutions staff | Sponsor and administrative paths incompletely documented | Sponsor-contractor control; applicants lacked a corporate vote | Holder-derived control over IANA unstated | Request and objection files incomplete |
| ARIN, amended by-laws Art. VIII and 21 June 1998 AC minutes, incorporation–21 June snapshot | Initial Board and board-selected first Advisory Council | Nonprofit registry; council advisory; Board fiduciary | Board, president, staff | Administrative review | AC-member removal omission recorded on 21 June | Other-RIR authority unstated | Membership rights still developing |
| ARIN, 30 June 1998 Board minutes, amended by-laws, and ARIN II, 16 October 1998, 30 June–December 1998 | Board retained corporate authority; member elections developed | Corporate governance with advisory policy input | Board and staff, advised by council | Regional administrative review | Full AC majority could remove an AC member; separately, four-fifths of voting trustees could do so | Other-RIR authority unstated | Members, applicants, legacy holders, and operators differed |
| Inter-registry coordination, RFC 2050 §§1–6, November 1996 | Registry and technical authors; no separate corporate selector | BCP 12 description of current practice | IANA, RIRs, and local registries | Parent-registry appeal ending at IANA | Common global removal body unstated | IANA retained the top-level role described by the RFC | Authorship supplied no holder-consent measure |
| ASO comparison, 1999 MoU §§1–9, October 1999 | Each signing RIR selected three council members | Advisory body, global-policy advice, Board appointments | Address Council, RIRs, ICANN Board | Individual allocations outside stated remit | Selecting RIR could remove its council member | Section 7 limited ASO involvement in RIR contracts | Section 9 criteria were formal but unmeasured |
The institutional picture is plural rather than empty. Technical appointment, federal sponsorship, regional agreement, administrative delegation, member voting, contractual arbitration, and hierarchical appeal all appeared before 1999. The distinctive gap concerns their combination at global scope and the source of authority to select those who spoke for the address-policy system.
Decision trail one: Europe moved from proposal to operation
Europe’s regional registry emerged through several dated decisions rather than a single act.
Recommendation. RFC 1174, issued in August 1990, proposed retaining IANA and the central Internet Registry while distributing blocks and further assignment authority to approved regional organisations. Its status and §1.3 identify an informational IAB recommendation and a proposed distribution method.
Regional design. RIPE-019, published in September 1990, proposed a dedicated coordination centre, defined its relationship to RIPE, and assigned it a prospective delegated-registry function.
Agreement and legal setting. The RIPE 8 minutes record agreement in early 1991 that the centre should be centralised and that a legal host should be sought. RIPE-039 records the RARE Council of Administration’s acceptance on 16–17 May 1991. The RIPE 9 minutes then record formal approval of the activity plan and approval in principle of the setup paper.
Delegation and implementation. The initial IANA delegation instrument remains an archive gap. RFC 1466 supplies a later contemporary observation: by May 1993, the RIPE NCC had received a regional block and agreed to apply the stated guidelines. Operational delegation is established by that date even though the initiating administrative document remains unavailable.
Residual central authority. RFC 1466 kept the Internet Registry as the default where no regional registry existed, allowed applicants to approach it directly, and preserved central responsibility for parts of the address space. Regionalisation therefore operated inside a delegated hierarchy.
Practice and later control. RIPE records and RFC 1466 show regional allocation and coordination with local registries. The stated design rationales included proximity, language, local knowledge, scalability, and systematic address management. RIPE NCC members later acquired appointment, dismissal, agenda, voting, and arbitration rights through the association. The sequence moved from technical recommendation to regional agreement, hosted operation, and member control without collapsing those stages into one source of authority.
Decision trail two: Asia-Pacific practice crossed an archival gap
The Asia-Pacific trail begins with an informational plan and becomes observable as an operating registry, while two early institutional steps remain dependent on retrospective evidence.
Recommendation. RFC 1466, May 1993, expressly “proposes a plan.” Its abstract reports general consensus among the FEPG acting for the FNC, the IEPG co-chairs, and RIPE in support of its recommendations. The record supplies no common roster, vote, objection set, or eligible-population denominator for that reported consensus.
Selection rationale. Section 2 argued that regional registries could serve a diverse population through language and knowledge of local customs. It proposed that networking authorities in a region legitimise the candidate, that the organisation be established and stable, and that it commit to IANA and Internet Registry guidelines. “Networking authorities” remained an institutional category rather than a defined electorate.
Regional acceptance. APNIC’s retrospective history attributes acceptance of the initial proposal to attendees at the January 1993 APCCIRN meeting and adoption of an updated pilot to the September meeting. The underlying first decision record is unavailable here, leaving the exact selector, eligible constituency, and form of January acceptance unresolved.
Operative delegation. The same retrospective dates IANA’s delegation of 202/8 and 203/8 to 1 April 1994. In the absence of the underlying notice, that date remains an attributed institutional reconstruction. RFC 1466 establishes the proposed Pacific block and central authority structure, rather than proving the later administrative act.
Exception and residual authority. RFC 1466 kept the Internet Registry as the root and default registry, permitted direct requests where necessary, and reserved central discretion over significant parts of the address space. APNIC’s regional authority sat within this wider uniqueness-preserving hierarchy.
Observed practice. The July 1995 IEPG minutes record APNIC issuing autonomous system numbers and participating in registry coordination. RFC 2050, issued in November 1996, identified APNIC as one of three operating regional registries. These contemporary observations establish activity after the attributed delegation while leaving the early electorate and delegation notice as specific documentary gaps.
RFC 2050 described working rules and hierarchical appeal
RFC 2050, Internet Registry IP Allocation Guidelines, published in November 1996 as Best Current Practice 12, is the strongest contemporary evidence that the regional system had become operational. Its IESG note said the document accurately represented current registry assignment practice while withholding endorsement or recommendation of the policy. It replaced RFC 1466 after operational experience.
Section 1 described three objectives: conservation, routability, and registration. It recognised tension between conservation or routability and the interests of individual users or service providers, and it explained that allocation could not guarantee routability. The hierarchy ran from IANA to regional registries to local registries. At that date, the document identified InterNIC, the RIPE NCC, and APNIC as regional registries.
Sections 2–4 described discretionary administration: justification of need, gradual allocation, reassignment records, engineering plans, utilisation evidence, audit, verification, and possible invalidation of assignments obtained through false information. Downstream registries were expected to follow regional guidelines. Registry staff were consequently exercising judgement over access to a scarce and operationally interdependent resource.
Section 6 supplied an express appeal. An organisation dissatisfied with an assigning registry could appeal to its parent. The assigning registry had to provide relevant documentation. Further appeals could move through parent registries, with IANA available after other avenues had been exhausted. Each registry was expected to document its procedure.
This remedy remained inside the delegation hierarchy: a higher registry reviewed a lower registry’s decision. Case counts, outcomes, withdrawals, and cross-regional comparisons are unknown. The applicant also had no role in selecting the ultimate IANA reviewer under the RFC.
The RIPE NCC’s 1998 arbitration procedure occupied a different institutional space. It covered specified regional service disputes and allowed each party to participate in choosing arbiters. Its jurisdiction followed RIPE NCC service agreements, while RFC 2050 governed escalation through the registry hierarchy. Together they show that pre-ASO review was real, differentiated, and bounded.
Participation had several denominators
A meeting roster measures recorded attendance at one meeting. A representation rate additionally requires the eligible population for the same institution, date, region, and procedure.
A mailing list measures visible senders and messages. Readers, private exchanges, organisations represented by one employee, and people without access sit outside that numerator. Message volume is an activity measure rather than a vote share.
A registration contact identifies someone responsible for administrative or technical information about a resource. That role may include maintaining a record without conferring power to elect a registry board. A policy participant, conversely, might never appear as a resource contact.
An applicant requests a service. Allocation decisions can bind applicants operationally, while appointment of the administrator arises through another relationship. A contractor performs work for a sponsor; a funder may impose conditions without acting as the representative of every beneficiary.
Membership creates firmer institutional rights. RIPE NCC, APNIC, and ARIN rules gave members powers over budgets, boards, meetings, policy structures, or officer removal. Definitions and voting weights differed. Members could also be local registries or providers serving many downstream organisations, so a corporate vote cannot be translated directly into a count of affected users or resource holders.
IETF attendance created eligibility for nominating-committee service under RFC 1601, RFC 2027, and RFC 2282. Internet Society membership supplied petition rights under RFC 1358. These were defined constituencies with meaningful rights. Address holders, operators, applicants, employers, and technical contributors overlapped with them only to an unknown degree.
Complete comparable rosters are unavailable for FRICC, FNC, FEPG, CCIRN, IEPG, RIPE, APCCIRN, APNG, APNIC, or early inter-registry decisions. Nor is there a harmonised list of all affected operators and number-holding organisations at each decision date. The surviving numerators and denominators therefore cannot produce a global participation rate.
Uncertainty runs in both directions. Operators visibly participated through regional forums, registries, technical bodies, sponsors, and implementation choices. The breadth of their authorisation remains unmeasured. The evidence supports neither universal consent nor universal exclusion.
The record establishes substantial pre-ASO governance
The strongest evidence against a literal reading of the title is concrete.
RFC 1174 documented a multi-body recommendation involving the IAB, FNC, IANA, the Internet Registry, and CCIRN. RIPE-001 created a public regional forum for wide-area IP operators. RIPE-019 and subsequent RIPE records show that a proposed coordination centre was debated, given a legal environment, staffed, and used. RFC 1466 recorded a RIPE NCC block and proposed a systematic regional plan.
RIPE 7 documented intercontinental work on registries, routing, DNS, and operations. APNIC’s retrospective reconstructs a regional initiative, pilot, and delegation, while the 1995 IEPG minutes independently show APNIC operating. RFC 2050 brought registry staff from InterNIC, APNIC, RIPE, and ISI into a common description of current practice. ARIN’s 1997–1998 records show active negotiation over corporate authority, member election, and two independent routes for removing Advisory Council members.
The system also contained constraints that formal organisation charts only partly capture: sponsor oversight, service agreements, repeated interaction, professional reputation, public technical criticism, routing operators’ independent choices, and bilateral escalation. Several institutions added documented regional remedies. The missing element was a single published global appointment and review circuit authorised by a common population of affected holders.
Four institutional properties clarify the result.
Competence is the ability to perform the work: evaluate requests, maintain unique records, preserve routing scalability, and coordinate delegations.
Participant access is the opportunity to attend, speak, nominate, comment, or contribute expertise.
Delegated authority is recognised power to administer a defined part of the address system.
Accountable control is the capacity of a defined principal to select, instruct, review, and remove an agent.
Before 1999, the first three were widespread. Accountable control appeared in fragments: within successive IAB procedures; regionally through RIPE, RIPE NCC, APNIC, and ARIN rules; contractually through sponsors and service arrangements; and administratively through registry appeals. Each fragment belonged to a particular constituency and jurisdiction. Their combined effect was a functioning distributed system rather than one holder-authorised global address-policy institution.
A four-part verdict
On ancestry, the title is literally false. IANA, the central Internet Registry, the IAB, FRICC and the FNC, CCIRN and IEPG, RIPE and the RIPE NCC, APCCIRN/APNG and APNIC, InterNIC, ARIN, and cross-registry cooperation all belong to the institutional genealogy. They supplied administrative functions, technical recommendations, regional organisations, and operating experience that the ASO inherited.
On coordination, the evidence is equally clear. Recommendations were published; regional plans were adopted in stages; legal hosts and corporate forms were created; blocks entered delegated administration; registries operated; common guidelines described current practice; and applicants could appeal upward. Some administrative links survive only through retrospective accounts, especially in the early APNIC sequence, but sustained coordination is visible in contemporary records.
On representation, the answer is plural. Internet Society members, qualified IETF participants, federal agencies, RIPE participants, RIPE NCC members, APNIC members, and ARIN members acquired real rights under particular procedures. Their constituencies differed from one another and from the full population of operators and number holders. A common numerator and eligible-population denominator for a pre-1999 global mandate remain unavailable.
On review, remedies existed within bounded jurisdictions. RFC 2050 moved appeals through parent registries to IANA. RIPE NCC service disputes entered arbitration from January 1998. Corporate members appointed or removed regional officers under specified rules. At ARIN after 30 June 1998, an affirmative vote by a majority of the voting members of the full Advisory Council could remove an Advisory Council member; separately, four-fifths of all voting trustees then in office could remove an Advisory Council member. Sponsors and professional relationships may have imposed additional constraints whose frequency and effect cannot now be reconstructed. The unevidenced element is a global reviewer selected by affected operators or holders and empowered to override address administrators as a class.
The Address Supporting Organization therefore had no exact prehistory. Its functional ancestors were numerous, and its coordination history was deep. What had not appeared in one institution was the 1999 combination of RIR-based council selection, collective global-policy advice, voting, ICANN Board appointment, and RIR removal.