ARIN After InterNIC: A Nonprofit Born from a Federal Exit

Summary

• ARIN's practical authority began through administrative continuity: Network Solutions transferred tasks, staff, computer infrastructure and registry records after NSF approved a nonprofit transition.
• Incorporation on 18 April 1997 created a Virginia nonstock corporation, and operations began on 22 October 1997, but corporate formation did not itself convey federal power, all asset rights or operator consent.
• The NAIPR debate shows the transition was contested in public, with proponents stressing continuity and community initiative while critics questioned fees, authority and Network Solutions' role.
• The strongest finding is control of the registration function, not statutory regulatory power or ownership of legacy number resources.

The handover began as an operating fact

On 22 October 1997, ARIN began operating as the regional number registry for its service region. The most important fact about that day was not ceremonial. A new legal person was now handling a function that had previously sat inside the NSF-supported InterNIC arrangement operated by Network Solutions. Requests still needed to be processed. Existing records still needed to be maintained. Staff knowledge still mattered. Computer systems still had to work. The Internet did not pause while the legal form changed.

That continuity is the source of ARIN's early practical power. A registry is not made authoritative only by the words in its charter. It becomes authoritative when it has the files, systems, staff, procedures and recognition needed to maintain the unique record on which operators rely. The ARIN transition was therefore an administrative succession before it was a fully explained public mandate.

The question is what moved. Five columns have to be kept separate: the federal arrangement, staff, hardware, registry data and decision authority. If those columns are collapsed, the transition becomes too easy to describe. It becomes a story in which a public function simply became a nonprofit function and the practical continuity proves the legal authority. That is not precise enough.

The federal arrangement explains why the previous function mattered. Network Solutions operated the InterNIC function under a 1993 cooperative agreement with the National Science Foundation. The staff column explains how operational knowledge survived. The hardware column explains how the new registry avoided starting from an empty room. The registry-data column explains why ARIN could maintain existing entries and process future requests. The decision-authority column is harder: it asks what legal, contractual or community authority justified ARIN's control of the function beyond the fact that the function was transferred.

This article is not an argument that ARIN should not have existed. The strongest case for the transition is serious. Separating number registration into a nonprofit reduced the conflict between commercial domain-name operations and number registry administration. Preserving staff and infrastructure limited operational risk. Public discussion around the proposal means the transition was not executed in total silence. But those arguments establish prudence and continuity. They do not by themselves establish statutory regulatory power, title to all legacy resources or consent by every affected network.

The administrative handover created a registry. The hard question is how much authority came with it.

The federal column: approval without a visible public mandate

The InterNIC arrangement matters because ARIN did not emerge from a private market as an ordinary association. It emerged after a federal research-network administrative function had been operated through a contractor. The NSF cooperative agreement with Network Solutions began in 1993. Through that arrangement, Network Solutions accumulated operational responsibility, staff knowledge, systems and records for number registration.

When NSF approved separation of the number registration function into a nonprofit, it solved a practical problem. A contractor that was also central to commercial domain-name operations was an awkward home for a registry function that needed neutrality and durable legitimacy. Moving the number function into a nonprofit could reduce conflict and create a clearer institutional surface for operators.

But approval is not the same as a statutory delegation visible in the public record used here. The fixed evidence does not include the complete NSF approval package, cooperative-agreement amendment or executed transfer instruments. It does not show a statute granting ARIN public regulatory power. It does not show a referendum of affected operators. It does not list alternatives considered and rejected. It does not provide the full legal bridge from a federally supported contractor function to a private nonprofit registry.

This does not mean the bridge did not exist. It means the public claim must be bounded. NSF approval is evidence that the federal sponsor accepted or permitted the separation. It is not, standing alone in the record used here, evidence that ARIN became a regulator in the public-law sense. It explains administrative succession. It does not answer every question about authority.

The difference matters because number registries occupy a peculiar position. They are not ordinary vendors. Their records affect routing, resource eligibility, transfer markets and operator dependency. Yet they are not conventional government agencies. A federal exit can create institutional continuity without creating public-law accountability. It can move a function from a contractor environment to a nonprofit environment while leaving operators to rely on membership rules, contracts, policies and practical necessity rather than statutory remedies.

The federal column therefore supports the transition's origin, not its maximum authority. It shows why ARIN could plausibly inherit a function. It does not show that every network in the region authorised ARIN or that every legacy address holder's legal position was redefined by the move.

Incorporation created a body, not a transfer schedule

ARIN's Articles of Incorporation are essential because they show what the new legal person was. The incorporation record places ARIN as a Virginia nonstock corporation, with purposes, initial directors, principal office and a member concept before operations began. The fixed dates place incorporation on 18 April 1997, with the instrument period extending through the later filing sequence, and operations on 22 October 1997.

That corporate step mattered. A nonstock corporation can hold assets, enter contracts, employ people, maintain accounts, adopt bylaws, receive members and be sued. Without a legal person, the number registry function would remain harder to govern. Incorporation turned a proposed registry into an entity capable of ordinary legal acts.

But incorporation did not itself convey the InterNIC database, contractor equipment, staff obligations, federal permissions or legacy resource rights. A corporate charter creates capacity. It does not fill the capacity with transferred assets. It does not identify which database records were assigned, licensed, copied or placed in custody. It does not show whether all liabilities were assumed. It does not establish title to number resources. It does not demonstrate operator consent.

The Articles list three initial directors at Network Solutions' Herndon address. That fact should be handled carefully. It shows proximity between the contractor environment and the new nonprofit. It is unsurprising in an administrative succession where staff, knowledge and systems had to move. It does not, by itself, prove misconduct. It also does not prove independence. The right inference is narrower: the new corporation was born very close to the operational source from which it would receive the registry function.

That proximity helped continuity. People who knew the work could launch the new body. Records and systems did not have to be rebuilt from scratch. Operators could avoid a discontinuity in request processing. But proximity also raises the need for documentary clarity. If the new corporation begins inside the orbit of the old contractor, the transfer package should say exactly what moved, what did not move and under whose authority.

The incorporation column therefore proves legal capacity. It does not prove the transfer ledger.

Staff continuity was a strength and a concentration

Staff are often treated as incidental to institutional design. In a registry transition, they are central. The people who understand request procedures, historical records, address allocation practices, database quirks and operator expectations carry a large part of the institution's practical authority. If they move, the function can continue. If they do not, the new body may have a charter but no capacity.

The modern controls description states that Network Solutions transitioned tasks, initial staff and computer infrastructure to ARIN after NSF approval. That is a strong continuity claim. It explains how ARIN could begin operations without a long gap. It also explains why operators would accept the new registry as the practical successor. The same people or closely related expertise could answer the same operational questions.

Yet a modern controls report is not a contemporaneous transfer agreement. It summarises history for a security and controls context. It is useful evidence of ARIN's current institutional account and service description. It is not an independent legal audit of what was assigned in 1997. The ARIN retrospective history has a similar institutional-interest limit. It can locate the story and identify records, but it should not be treated as independent proof of legitimacy.

Staff continuity has two faces. One face is risk reduction. A registry with live operational dependencies should not purge the knowledge base simply to signal independence. The other face is concentration. If staff and decision routines move from a contractor environment into a nonprofit with minimal external reset, practical control may shift faster than accountable governance develops.

For operators, the difference may have been invisible at first. Requests could be handled. Existing records could be maintained. Telephone calls and messages could reach people who knew the subject. That is exactly why continuity is powerful. It makes the new institution normal before the authority chain is fully examined.

The staff column therefore supports de facto control. It does not prove that every affected operator agreed to the new arrangement or that every old discretionary practice was reviewed.

Hardware and systems made succession immediate

The hardware and systems column is less dramatic than the authority debate, but it is just as important. A registry cannot operate only from corporate purpose clauses. It needs machines, databases, connectivity, backups, operational procedures, security controls and staff access. If Network Solutions supplied the initial computer infrastructure, ARIN did not start as an empty nonprofit waiting to build a registry. It started with the operational means to run one.

That immediate capacity explains the success of the transition. The number registry function could move without forcing operators into a long administrative outage. A new nonprofit could inherit not only a name and a purpose, but the practical machinery of record maintenance.

It also explains why custody must be separated from title. Having systems or copies of data can establish custody. Custody means the institution can operate the records, process changes and maintain service. Title or ownership is a different claim. The public evidence used here does not provide a full asset schedule stating which hardware, software, records, contracts or rights were transferred, assigned, licensed or retained.

In infrastructure governance, custody often matters more day to day than title. The body with the working database can update records. The body with the systems can process requests. The body with the operational staff can decide what documentation is sufficient. That practical control creates reliance, even if the legal basis remains partly documented elsewhere.

This is why the missing asset schedule matters. It would distinguish contractor equipment from nonprofit equipment, copied data from assigned data, operational custody from property rights, and service continuity from legal entitlement. Without it, public history can say that infrastructure moved. It cannot fully explain the legal character of the move.

The systems column therefore proves operational capability. It does not settle ownership or scope of rights.

The database was the real chokepoint

The registry-data column is the most consequential. ARIN's later newsletter account says that ARIN inherited the InterNIC database of existing IP addresses and AS numbers and responsibility to maintain those records. That sentence captures the power created by succession. The database was not just an archive. It was the record by which existing resources, contacts and future changes would be recognised.

"Inherited" is an operationally useful word and legally limited public evidence by itself. It tells the reader that ARIN took over responsibility for maintaining the records. It does not prove property title in every legacy number resource. It does not show that every legacy holder agreed to new terms. It does not show whether the database was transferred as property, copied under authority, placed in custody, or maintained as part of a recognised registry function.

The difference is not academic. A registry database can contain records about resources that were allocated before the registry itself existed. Maintaining those records is necessary. Claiming ownership over the underlying resources is a different matter. A database entry can establish administrative recognition. It does not automatically establish that the registry owns the number block or can rewrite every legal relationship around it.

This is one of the enduring problems of legacy number governance. The body that maintains the database has practical power over updates, contacts, transfers, accuracy and dispute handling. Legacy holders may experience that power as gatekeeping even where the registry's legal claim is framed as record maintenance. The transition from InterNIC to ARIN therefore did more than move files. It moved the choke point for proof.

That move may have been necessary. Someone had to maintain the records. The public interest in a coherent number registry is obvious. Fragmented or abandoned records would damage operators. But necessity does not remove the need to describe the legal basis accurately. Custody of the InterNIC database made ARIN practically authoritative from its first day. It did not by itself answer title, consent or public-law authority.

The database column is therefore strongest for control and weakest for ownership.

NAIPR was a hearing, not a referendum

The NAIPR discussion record from January 1997 is important because it preserves contemporaneous dispute. It shows that the ARIN proposal was not merely a retrospective institutional narrative. People argued about fees, authority and Network Solutions' role while the transition was being proposed. Proponents described ARIN as a community initiative and continuity solution. Critics questioned whether the new body would impose fees, inherit authority too easily or reproduce contractor power in nonprofit form.

That debate should be treated like a bounded hearing, not a referendum. A mailing list can reveal arguments, objections and assumptions. It cannot establish the views of every affected operator. It cannot adjudicate the factual accuracy of each message. It cannot prove that the proposal had or lacked consent across the service region. Individual messages are advocacy.

Even so, the debate matters. It prevents the history from being written as if the transition were uncontested. Fee objections show that the nonprofit model had distributional consequences. Authority objections show that some entities understood the difference between continuity and mandate. Questions about Network Solutions' role show concern that the old contractor's position might shape the new body.

The proponents' best argument was operational and institutional. A nonprofit could separate number registration from commercial domain-name operations. It could preserve staff and records while giving operators a more focused registry body. It could create a venue for community governance over time. That was a plausible response to the InterNIC chokepoint.

The critics' strongest point was that continuity can harden into authority before consent is measured. If the same operational assets, staff and records move into a new body, the new body may become unavoidable before operators have meaningful alternatives. Fees and policy processes then arrive after control is already in place.

The NAIPR column therefore supports openness of contestation. It does not prove democratic authorisation.

Decision authority arrived before membership maturity

The hardest column is decision authority. By launching operations, ARIN gained the capacity to process requests and maintain records. It also gained practical influence over who could update records, how new requests would be evaluated, and what policies would govern future allocations. That is decision authority in the operational sense.

The legal and community bases for that authority were still developing. Incorporation created the legal person. NSF approval supported the separation. Network Solutions supplied continuity. Public discussion gave the proposal a contested record. Membership and later policy processes developed around the new institution. But administrative control moved before a mature membership structure could demonstrate broad operator consent.

That sequence is common in infrastructure transitions. The service cannot wait for perfect governance. A new body must begin operating, and its legitimacy is built partly by doing the work. Yet the sequence should be named honestly. Later membership processes cannot be retroactively treated as if they authorised every initial transfer. Later policy participation cannot prove that every affected operator consented before the handover.

The missing denominator remains critical. The fixed evidence does not supply a complete affected-operator list, authorisation record or operator vote. It does not show how many legacy holders existed, how many were notified, how many objected, or how many had practical alternatives. It does not show independent evidence of alternatives considered and why a Virginia corporation was selected.

Decision authority therefore rests on a layered basis: federal approval for transition, corporate capacity, contractor-to-nonprofit continuity, database custody, operator reliance and later governance development. That is enough to explain practical authority. It is not the same as statutory public power.

ARIN was born as a nonprofit registry with real administrative control. It was not born as a legislature for number resources.

The transfer ledger remains incomplete

The ledger can now be read column by column.

The federal arrangement moved from NSF-supported InterNIC contractor administration toward a nonprofit registry approved by NSF. The public record used here shows the broad transition but not the complete approval package or cooperative-agreement amendment.

Staff moved as operational capacity. The record states initial staff transitioned from Network Solutions to ARIN. That explains continuity but does not provide all employment instruments, liabilities or independence safeguards.

Hardware and computer infrastructure moved as operating machinery. That made first-day service plausible. The record does not provide a complete asset schedule distinguishing ownership, license, custody and retained contractor property.

Registry data moved as the central chokepoint. ARIN inherited responsibility for maintaining IP address and AS number records. That proves practical custody and control. It does not prove property title in every number resource or operator consent to every future registry condition.

Decision authority moved as a composite of recognition, practical necessity and later governance formation. It was real, because ARIN could process requests and maintain the ledger. It was bounded, because the public record here does not show statutory delegation, referendum or complete transfer instruments.

This asymmetrical ledger is the best description of the transition. The continuity columns are strong. The public-authority column is thinner. The ownership column is narrower than institutional language sometimes implies.

What the nonprofit form fixed

The nonprofit form did solve a real institutional problem. The InterNIC arrangement had concentrated important registration functions inside a contractor environment associated with Network Solutions. By the mid-1990s, commercial domain-name operations and number registration were becoming different kinds of functions. The domain-name side had obvious commercial pressure. The number side required administrative neutrality, continuity and a governance path for operators whose resources depended on accurate records.

Moving number registration into a nonprofit reduced at least three risks. First, it narrowed the institution's purpose. A body created specifically for Internet number registration could be judged against that task rather than against a wider contractor portfolio. Second, it made membership and community governance possible in a more direct form. A contractor can consult users, but a nonprofit can build members, meetings and policy processes around the service. Third, it reduced the appearance that number registry decisions were being made inside a company whose commercial domain-name role might distort incentives.

These benefits should not be understated. Institutional design often improves legitimacy by removing obvious conflicts, even before it has solved every question of representation. A nonprofit with a focused purpose is not automatically democratic, but it is easier to hold to a public-interest service standard than a mixed commercial contractor. The transition also helped separate two kinds of scarcity: names and numbers. Combining both under one contractor would have made the chokepoint more politically exposed.

The nonprofit form also gave operators a future institution to influence. Once ARIN existed as a member-oriented registry, later policy development, elections and member participation could grow around it. That path was more promising than leaving the number function indefinitely inside a federal contractor arrangement. In that sense, ARIN's formation was a governance improvement.

But the improvement has a precise scope. It fixed the institutional container. It did not prove the transfer contents. It created a better body to receive the function. It did not show every asset instrument, every operator notice, every legacy-resource title issue, or every reason for choosing the Virginia corporation. The nonprofit form made legitimacy more achievable. It did not complete legitimacy by itself.

Legacy records were not ordinary customer files

Legacy number records deserve their own treatment because they made ARIN's inheritance different from a normal service-provider customer list. Many resources had been allocated under earlier administrative arrangements. Some holders may have understood their relationship through historical allocation, technical recognition or reliance rather than through a modern membership contract. When ARIN took over maintenance of the records, it became the body that could make those historical relationships visible or difficult.

That kind of custody is powerful. A holder whose record needs correction, transfer, contact update or routing-related recognition must deal with the registry maintaining the record. Even if the holder believes the resource was historically allocated under a different understanding, the practical route to recognition runs through the current database maintainer. The registry's authority therefore grows from operational dependence as much as from formal contract.

This is why database custody must not be equated with ownership of addresses. The number resources themselves are not ordinary physical assets that can be boxed and delivered. They are entries in a coordinated global system. A registry can maintain, recognise and administer those entries without owning them in the way a company owns a server. The public transfer record should therefore distinguish record custody, service responsibility, contractual rights, legacy-holder obligations and any claimed property interest.

The fixed evidence here does not supply a schedule that does that. The later statement that ARIN inherited the InterNIC database and responsibility to maintain records is important. It establishes practical continuity. It does not tell the reader whether all legacy records carried the same legal status, whether all holders were notified, whether any objected, or whether the new registry imposed new conditions immediately or later.

This distinction became more important as number resources acquired market value. In 1997, the registry's immediate problem was continuity. Later, as scarcity and transfers made legacy blocks economically significant, the legal meaning of database custody became more contested. A founding transition that is adequate for service continuity can look incomplete when asked to explain later title, transfer or contract questions.

The lesson is not that ARIN lacked the right to maintain legacy records. The lesson is that maintaining them and owning what they describe are different claims. A serious founding archive would mark that line.

Virginia was a corporate answer, not a regional vote

The Articles made ARIN a Virginia nonstock corporation. That choice produced a practical legal answer. The new body had a state law home, a principal office, initial directors and a recognised corporate form. For contracts, employment, accounts and litigation, that mattered. A registry without a legal home would be harder to operate and harder to hold responsible.

But choosing Virginia did not itself prove regional consent. ARIN's service region was larger than Virginia and larger than the organisations immediately involved in the transition. The public record used here does not provide independent evidence of alternatives considered, why a new Virginia corporation was selected, or what operators outside the initial circle thought about that choice. The choice may have been obvious because Network Solutions and staff were in Herndon. It may have minimised operational risk. It may have been legally convenient. Those are plausible explanations, not proved findings from the fixed evidence.

The difference matters because legal home shapes remedies. If a dispute arose with the new registry, the corporate home would influence where records were held, where directors acted, which corporate law applied and which litigation route was practical. A registry's state of incorporation is not merely an address. It is part of the accountability architecture.

Item 037 can examine Virginia corporate law in detail. The narrower point here is that incorporation supplied a legal person without answering the regional-selection question. A Virginia corporation could be an effective registry for a broad service region. It was not made regional by state law. Its regional authority came from the transferred function, operator reliance, later policy processes and recognition inside Internet governance.

That makes the selection file important. If alternatives were considered, the public should be able to see the operational, legal and accountability reasons. If the choice was driven mainly by continuity with Network Solutions staff and infrastructure, that should be said. Continuity may have been the right reason. It should not be disguised as a measured regional mandate.

The missing operator denominator changes the fairness question

No founding account can prove operator consent without knowing the affected operator denominator. The fixed evidence does not supply that denominator. It does not list all active requesters, all legacy holders, all service providers, all organisations that would become fee-liable, all operators that objected, or all operators that had no notice. Without that list, the public cannot measure the transition's reach.

The denominator matters because different groups experienced ARIN's birth differently. A new requester may have experienced a change in application path. A legacy holder may have experienced a change in record maintainer. A provider dependent on InterNIC-era processes may have experienced continuity. A critic of new fees may have experienced a new financial obligation. A member-oriented operator may have experienced a better governance forum. A non-participating network may have experienced the transition only later, when it needed an update or transfer.

Those experiences should not be averaged into one word. "Continuity" is accurate for service operation. It may not describe every operator's legal or financial experience. "Community initiative" may describe proponents' intent. It may not describe the consent of non-entities. "Federal exit" describes the sponsor's withdrawal from direct contractor dependence. It does not identify every private party's rights.

A proper operator-impact measurement would reconstruct the transition population in categories: legacy holders by type, active applicants, organisations receiving invoices, organisations that participated in NAIPR, organisations that objected, organisations that later became members, and organisations with no visible role. It would then compare processing time, fee incidence, record-update success and dispute outcomes before and after 22 October 1997.

That measurement would still not turn ARIN into a public agency or invalidate its formation. It would make the founding effect visible. It would show who benefited from continuity, who paid new costs, who gained governance routes and who remained outside the decision.

Without the denominator, the fair conclusion is cautious. ARIN's formation was likely the least disruptive way to preserve a critical registry function. It was not shown, in the fixed public evidence, to be the result of authorisation by every operator it would affect.

The transition converted a contractor chokepoint into a member institution

The most generous reading of ARIN's birth is that it converted a contractor chokepoint into a member-oriented institution. That is a real improvement. A contractor operating under federal support can be efficient, but it is not the same as an operator-facing registry with its own governance path. By creating ARIN, the number community gained a body that could be shaped over time by the people who used the service.

That future-facing benefit helps explain why continuity was acceptable. If the staff, systems and records had moved into a body with no path to member participation, the transition would look more like private capture. If they moved into a nonprofit that later developed member and policy processes, the transition can be understood as a bridge from federal-contractor administration to community registry governance.

The bridge metaphor is useful only if it does not erase the first step. The first step was not a mature member vote. It was an administrative transfer. The member institution grew around the function after control moved. That timing matters. It means later governance can improve legitimacy, but it should not be used to rewrite the transfer as if membership created the initial authority.

This is a common pattern in Internet governance. Administrative necessity creates a body. The body works. Its usefulness attracts participation. Participation becomes evidence of legitimacy. Then the institution describes the whole arc as community governance. The arc may be broadly true, but the first step remains administrative continuity.

ARIN's case is therefore neither a simple public delegation nor a simple private takeover. It is a contractor-function succession into a nonprofit that later became the normal institutional home for regional number governance. The succession gave ARIN control. The nonprofit path gave it a route to legitimacy. The missing instruments define the boundary between the two.

The finding: continuity created control, not sovereignty

The ranked finding is straightforward.

First, ARIN's continuity claim is strong. Staff, tasks, systems and registry records moved from the Network Solutions InterNIC environment into a new nonprofit after NSF approval. That explains why ARIN could operate on 22 October 1997 without disrupting a critical registration function.

Second, ARIN's control claim is also strong. Custody of the database and operating infrastructure gave ARIN practical authority over consequential records. Operators had to deal with the body maintaining the unique registry.

Third, ARIN's broader public-authority claim is limited by the public evidence. Incorporation created a Virginia nonstock corporation. NSF approval supported transition. Neither, in the fixed record used here, proves statutory regulatory power, title to all legacy resources or consent by every affected network.

The transfer-document remedy is specific: publish the NSF approval, cooperative-agreement amendment, Network Solutions-to-ARIN asset, staff and data transfer instruments, and any schedule distinguishing custody of records from title or contractual rights in legacy number resources. Redactions for personal or security details need not hide the legal categories.

The operator-impact measurement should reconstruct the affected population at the transition: legacy holders, active requesters, affected service providers, fee-liable organisations, objections, changes in processing time, and disputes before and after 22 October 1997. Without that denominator, public discussion cannot measure who experienced the transition as continuity, new cost, new authority or new remedy.

The archival test is whether the missing instruments show a clean chain: federal approval, contract amendment, asset schedule, database custody, staff transition, liabilities, operator notice and remedy. If they do, ARIN's founding account becomes a well-documented public-sector exit into nonprofit administration. If they do not, the most accurate description remains narrower: ARIN inherited the operating chokepoint and made it work, but continuity did not itself prove every authority claim attached to the ledger.