Summary
- A Regional Internet Registry service area is not a choice-of-law rule. It identifies the normal service institution, not the one legal system governing every act connected to a holder or address block.
- The standard contracts choose different anchors: RIPE NCC selects Dutch law and internal arbitration; APNIC selects Queensland law and courts; ARIN uses Virginia and United States law with defined venue variations and government accommodations; LACNIC was designed around Uruguayan contract law; AFRINIC’s agreement is anchored in Mauritius.
- Those clauses improve predictability between registry and holder, but they do not determine the holder’s corporate existence, every insolvency question, telecom licensing, sanctions, data protection, customer claims or the rights of third parties who never signed the contract.
- Rome I illustrates the correct method for European contractual disputes: respect party choice within scope, identify exclusions and defaults, and preserve overriding mandatory rules. It is not a global code and should not be applied mechanically outside its field.
- Cross-border registry governance needs a conflict map for each disputed act: parties, contract version, chosen law, forum, corporate domicile, operating locations, mandatory rules, affected third parties, remedy and enforceability.
The address has no passport
An IP address may be announced from routers in several countries within minutes. Traffic using it may cross a dozen legal systems before reaching a customer. The company shown in the registry may be incorporated elsewhere, controlled by a parent in another state and financed by creditors in still another. The Regional Internet Registry serving the record may be a corporation or association formed under the law of a country where the holder has no employees at all.
This is ordinary multinational networking, but the legal language around number resources often compresses it into one geographic label. The holder is described as an ARIN, RIPE, APNIC, LACNIC or AFRINIC member. From that administrative fact, observers may infer that the law of the region applies or that the address somehow belongs legally to the place where the registry categorises it.
Neither inference works. A service region is not a sovereign territory, and an address is not a movable entity that carries a jurisdictional tag. Applicable law follows legal relationships and connecting factors: contract choice, incorporation, habitual residence, place of performance, location of regulated activity, customer harm, insolvency proceedings and forum rules. Different questions can produce different answers in the same dispute.
The registry contract is nevertheless crucial. It can identify the law governing the bilateral service relationship, select arbitration or courts, define notice, incorporate policies and allocate risk. For a holder deciding where to challenge a suspension, invoice, transfer refusal or contract termination, the clause may be the first place to look.
The mistake is not to take that clause seriously. The mistake is to make it answer everything. A Dutch-law service agreement does not turn a Kenyan telecom licence into a Dutch licence. A Queensland forum clause does not necessarily bind a customer who never signed it. A Virginia arbitration clause does not decide the existence of a foreign company in liquidation. The method must begin by identifying the question before selecting the law.
Five institutions, five domestic anchors
The RIR system is global in function but domestic in legal form. RIPE NCC is a Dutch membership association. APNIC is an Australian company. ARIN is based in Virginia in the United States. LACNIC was established in Uruguay. AFRINIC is a Mauritian company. Their regions contain many states, but each institution needs a home legal system for corporate capacity, internal organs, contracting and ordinary accountability.
That domestic anchor is not an embarrassment. A legal person without a governing company or association law would be much harder to hold to account. Directors need powers and duties. Members need rules for meetings and votes. Contracts need a method of formation. Courts need a way to determine whether the organisation exists and who may act for it.
The governance problem is one of scope. The incorporation law governs the registry as an entity. It does not automatically govern every member as an entity. The service agreement may extend the registry’s home law to contractual obligations between the parties. It cannot, merely by doing so, erase rules that another state applies mandatorily to activity within its territory or decide the rights of strangers to the agreement.
The resulting structure is layered rather than territorial. At the centre is a bilateral registry relationship. Around it sit the holder’s corporate law, the laws of operating subsidiaries, regulatory licences, employment and customer obligations, security and data rules, tax, sanctions and insolvency. A serious analysis asks where those layers meet and which one controls the disputed issue.
This is why comparing the contracts is more useful than comparing coloured region maps. The clauses show what the institutions actually ask members to accept. They also reveal exceptions, procedural differences and areas left untouched. The map tells a holder where it normally applies. The agreement tells it what the registry says will govern that relationship.
RIPE NCC: Dutch law meets a foreign member’s legal identity
The RIPE NCC Standard Service Agreement, RIPE-812, makes the cross-border structure visible on its first page. RIPE NCC is identified as a membership association under Dutch law, registered in Amsterdam. The member must supply its own name, address, legal form and registration details.
That pairing matters. The agreement does not absorb the member into the Netherlands. It recognises two legal persons with different origins. To conclude the agreement, a member supplies a recent extract from a commercial register or equivalent document proving registration with its national authorities. The registry therefore relies on the member’s home legal system to establish that the counterparty exists and that an authorised representative can sign.
Article 11 then selects Dutch law for agreements between RIPE NCC and the member and sends disputes arising from the Standard Service Agreement to the RIPE NCC Conflict Arbitration Procedure. This provides a common contractual baseline across a service area spanning more than 75 countries. Without it, each disagreement could begin with a costly argument over the default applicable law.
The clause still has a defined entity: agreements between RIPE NCC and the member. It does not say Dutch law governs the member’s incorporation, every use of addresses, every customer contract or every regulatory obligation. Other provisions acknowledge this indirectly. The member must provide national registration evidence, and the agreement contemplates statutory provisions that may prohibit an organisation from becoming a member.
The arbitration route is also not identical to a national court of general jurisdiction. It is an agreed procedure for disputes within its stated scope. Questions about the validity of a foreign company’s appointment of an administrator, a regulator’s licence order or a third party’s property claim may not become RIPE arbitration questions simply because an address record is involved.
The RIPE text therefore supports two propositions at once. Dutch law is a genuine and important contractual anchor. The holder remains a foreign legal and operational actor for many other purposes. Treating only the first proposition as true would convert a useful choice-of-law clause into an implausible extraterritorial code.
APNIC: Queensland law and an exclusive court clause
The Standard APNIC Membership Agreement, APNIC-079, uses a more conventional court-based formulation. Clause 5.2 states that the agreement is governed by Queensland law and, subject to the dispute-resolution document, the member and APNIC submit irrevocably to the exclusive jurisdiction of Queensland courts.
For APNIC, which serves 56 economies, the attraction is clear. One standard law and forum can reduce variation in bilateral membership disputes. Staff can administer a common agreement, and members can identify the presumptive place for litigation rather than guessing among dozens of legal systems.
The same agreement contains a limiting phrase that should not be ignored. Rights, duties and remedies operate to the extent not excluded by law. That wording does not provide a full conflicts analysis, but it recognises that contractual drafting operates inside a legal environment. A term may face mandatory limits, public policy, consumer or competition rules, procedural law or another non-derogable rule depending on the forum and facts.
The exclusive-jurisdiction clause binds the parties who agreed to it within its scope. It does not automatically bind every National Internet Registry entity, non-member account, downstream assignee, creditor or customer. APNIC publishes distinct documents for different relationships. Before relying on APNIC-079, an analyst must confirm that this agreement governed the holder and event at the relevant date.
Dynamic incorporation adds another cross-border issue. The membership agreement incorporates APNIC documents and provides mechanisms through which obligations can evolve. A holder may have signed years before a disputed policy change. The governing-law clause can tell a Queensland court which contract law to use, but the court may still need to decide whether the later document became binding, whether notice was sufficient and whether the consequence fits the incorporated terms.
Queensland law is thus a stabilising common denominator, not a claim that Queensland regulates all networks in Asia and Oceania. It governs the contract because the parties select it and APNIC is anchored there. The source of the rule is agreement and domestic law, not the geographic reach of the APNIC map.
ARIN: one governing law, several dispute locations
The ARIN Registration Services Agreement, version 14.0, demonstrates that a contract can choose one governing law while adapting dispute mechanics to holder location. Section 14(k) selects the law of the Commonwealth of Virginia and, where applicable, United States law for the agreement and the parties’ performance.
The dispute provision then distinguishes venues. It uses binding arbitration after negotiation and identifies different locations depending on the holder’s principal place of business: Washington, D.C. for United States holders, Ottawa for Canadian holders, and Miami for holders elsewhere in ARIN’s service region, unless the parties agree to another location. Specified Virginia courts remain available for temporary or preliminary relief intended to preserve the status quo.
Canadian court references also appear for defined proceedings, and version 14.0 includes an accommodation for a national, state or local government authority whose laws strictly require the law of its jurisdiction or domicile to apply, provided ARIN receives acceptable written substantiation. These are narrow exceptions, not a general domicile rule. They are still significant because they acknowledge that a uniform standard agreement can encounter public bodies that cannot freely accept another state’s law.
ARIN’s structure separates three ideas often collapsed in casual discussion. Governing law answers which substantive contract law the agreement selects. Arbitral seat or hearing location identifies where the dispute process occurs. Court venue identifies where particular judicial relief may be sought. Those answers can point to different places without contradiction.
The clause also does not say that Virginia law governs every issue involving included number resources. A holder incorporated in Canada remains a Canadian legal person. Its directors’ authority, insolvency status, telecom licences and customer duties may be governed elsewhere. An award rendered under the contract may need recognition and enforcement where assets or parties are found.
ARIN’s tailored locations show a practical response to extraterritorial membership. They improve accessibility relative to requiring every holder to appear in one city. But they also make careful reading essential. “ARIN law” is not a category. There is Virginia substantive law, federal law where applicable, arbitration procedure, location-specific mechanics, government exceptions and the laws governing the holder outside the contract.
LACNIC: Uruguayan law was a design choice
LACNIC’s legal anchor was explicit before the registry became fully operational. Its application for formal recognition said legal advisers would adapt ARIN’s Registration Services Agreement to Uruguayan contract law. That statement is important because it records an intentional act of legal localisation.
The emerging registry was not simply inheriting a neutral global contract. It was taking a predecessor form and making it suitable for a legal person established in Uruguay. The regional service relationship would therefore be carried by host-state private law even though members and networks were spread across Latin America and the Caribbean.
The historical page has a date inconsistency that should remain visible. Its heading labels the application 28 November 2002, while the recognition chronology and related official records place the application on 28 November 2001. The discrepancy does not change the contractual point, but it cautions against building a precise chronology from a page label alone.
The recognition application is not a substitute for the current LACNIC service agreement. It proves design intent at establishment. It does not establish the exact governing-law, forum, arbitration or amendment terms binding every present member. A live dispute would require the executed or applicable agreement version and any incorporated procedures.
Even with that limitation, the document defeats a common misconception. LACNIC did not acquire a free-floating law from “Latin America.” It needed Uruguay’s legal system to support its contracts. The service region supplied the population served; the host state supplied the legal framework of the institution and agreement.
That distinction also protects diversity inside the region. Brazil, Argentina, Mexico, Caribbean states and other jurisdictions do not merge legally because one registry serves them. Their companies remain formed under domestic law, and their networks remain subject to local public rules. Uruguayan contract law can coordinate the registry relationship without becoming the civil code of a continent.
AFRINIC: Mauritius in the contract, Africa in the operations
The AFRINIC Registration Service Agreement dated 27 November 2017 identifies AFRINIC as a not-for-profit organisation based in Mauritius. It states that the parties will perform obligations in compliance with laws in the jurisdictions where they operate as well as the laws of Mauritius, which govern the agreement.
That wording is unusually useful for this analysis. It places host law and operating-jurisdiction law in the same clause. Mauritius governs the contract, but the parties do not thereby stop being subject to legal provisions where they operate. The text resists the false choice between one governing law and all other law.
The agreement also contains provisions on bankruptcy or insolvency, intervention, revocation, notices and disputes. Their presence shows why conflicts can become acute. If a foreign member enters insolvency, AFRINIC may have contractual rights triggered by that event. At the same time, the insolvency forum may claim control over the company’s estate, management powers and creditor process. The two legal systems may characterise the registry relationship differently.
A contract clause cannot by itself decide that collision in every country. The forum hearing the case will apply its own conflicts rules, insolvency statutes, public policy and procedural law. It may respect the Mauritian choice for contractual questions while applying the insolvency law of the main proceeding to the debtor’s status and estate.
The 2017 agreement should also be used with a version warning. It is primary evidence of the terms in that document, not proof that no later text, court order or special arrangement applies. Given AFRINIC’s institutional and litigation history, version and execution evidence are particularly important.
Still, the contract offers a sound conceptual formula: host-state law can govern the registry agreement while local laws continue to govern operations. That is not a defect to be eliminated. It is the normal condition of a cross-border service relationship.
Rome I shows how choice and limits coexist
For disputes heard in participating European Union states, Regulation (EC) No 593/2008, known as Rome I, provides a disciplined framework for contractual obligations. It applies from 17 December 2009 and should be read within its civil-and-commercial scope and exclusions.
Article 2 gives the Regulation universal application: the law identified under its rules can be the law of a non-EU state. Article 3 recognises party choice. Article 4 supplies defaults where no effective choice resolves the question. This means a European court does not reject Virginia, Queensland, Mauritian or another selected law merely because it is foreign.
Party choice is powerful, but Rome I does not make it absolute. Article 9 preserves overriding mandatory provisions—rules regarded as crucial to safeguarding a country’s public interests and applicable regardless of the law otherwise governing the contract. The law of the forum retains its overriding mandatory rules, and in specified circumstances effect may be given to such rules at the place of performance.
The Regulation also has exclusions. Corporate status and internal company questions are not simply ordinary contractual obligations under Rome I. Evidence and procedure are generally outside its field. Arbitration agreements and choice-of-court questions involve other legal instruments and doctrines. Non-contractual claims may fall under different rules.
Rome I therefore models the right intellectual sequence. First classify the issue. If it is a covered contractual obligation, identify the parties’ choice. Then examine whether another provision, exclusion, overriding mandatory rule or public-policy limit changes the result. Do not begin from the physical route of the packet or the name of the registry region.
The Regulation is not a global conflicts code. A court in Australia, Mauritius, the United States or a non-participating state applies its own rules. Its value here is analytical: it demonstrates how a legal system can respect a standard-form choice while preserving the laws that parties cannot contract away.
Corporate law does not follow the service agreement
Every registry needs confidence that its counterparty exists and that the signer has authority. That question is ordinarily answered by the law governing the holder’s formation and internal affairs, not by the registry’s chosen contract law alone. RIPE NCC’s demand for a national commercial-register extract makes this dependency explicit.
Suppose a holder is incorporated in State A, signs a registry agreement governed by State B law and is represented by a director whose appointment is later challenged. State B contract law may govern interpretation of the agreement. State A company law may determine whether the director had authority, whether the company was dissolved and who may act after a merger.
The distinction becomes important during restructuring. A name change, conversion, merger, division or transfer of undertaking may be valid under the holder’s company law but still require registry documentation. The registry is entitled to verify continuity. It should not assume that its database entry creates or defeats the corporate event.
Groups add complexity. The entity operating routers may not be the entity named in the registry. A parent may control the member, a subsidiary may hold licences, and another affiliate may contract with customers. The phrase “the holder” can conceal several companies with different legal connections.
A cross-border review should therefore map legal identity before debating rights. It should capture the exact registered name, number, incorporation law, status, authorised signers, parent relationships and any succession event. It should then compare those facts with the registry account and agreement.
This is not mere paperwork. If the wrong entity receives notice or purports to transfer resources, the choice-of-law debate may begin from a false party. Corporate law supplies the answer to who exists; the service agreement supplies many of the answers to what that party promised.
Insolvency splits status, contract and operational continuity
Insolvency is the strongest stress test because several legal systems may claim priority at once. The holder’s main insolvency proceeding may determine who controls the company, which contracts can be continued or rejected, what belongs to the estate and how creditors are treated. The registry agreement may contain termination, notice or cooperation clauses triggered by bankruptcy. The registry’s home court may be asked for relief. Networks and customers may be operating elsewhere.
No responsible analysis should say simply that the registry’s chosen law wins or that the insolvency forum automatically controls every registry act. The questions must be separated. Does the proceeding validly appoint an officeholder? Is the agreement an executory contract under the relevant insolvency law? Is a termination-on-insolvency clause enforceable? What record change is requested? Would it preserve or disrupt the running network? Which court can make an order effective against the registry?
Recognition across borders is another step. An insolvency order from one state may need recognition where the registry is incorporated. An arbitral award may need enforcement where the member has assets. A registry-side decision may be challenged where its operational effect is felt. The contract cannot guarantee that every foreign forum will treat each step identically.
Operational continuity should remain a distinct concern. A dispute over the estate or contract should not be allowed to create unnecessary routing or security disruption. Preserving the last verified record while authority is adjudicated may be safer than a rapid irreversible change. That is a governance choice informed by, but not identical to, choice of law.
The AFRINIC agreement’s express insolvency provisions and the RIPE and ARIN termination structures show that registries anticipate corporate distress. What is missing publicly is a comparative set of decided cases tracing how those clauses interacted with foreign proceedings. Without those cases, confident universal claims would outrun the evidence.
Mandatory regulation remains where activity occurs
Telecom, sanctions, data-protection, competition, consumer, cybersecurity and criminal laws are not displaced merely because a registry agreement chooses foreign law. A network operating licensed infrastructure must comply with the regulator that has authority over that operation. A company serving customers may face local duties even when its registry account is abroad.
Sanctions illustrate the distinction. A registry may be legally prohibited by its home jurisdiction from supplying certain services. A member may be subject to different sanctions or blocking rules where it is incorporated or operates. The contract’s governing-law clause helps interpret the parties’ rights but cannot authorise conduct prohibited by applicable mandatory law.
Data presents another layer. Registry services involve contact information, corporate documents and public directory data. AFRINIC’s 2017 agreement refers to Mauritian data-protection and privacy law for its handling of submitted information. A foreign member may also have obligations under the law governing its staff, customers or disclosure decisions. Which controller processes which data, and where, matters more than the region label.
Competition and access questions may likewise arise where a registry has substantial practical exclusivity. A contract cannot conclusively declare its own compliance with every competition regime. Nor does the existence of a regional monopoly automatically establish a violation. The relevant authority must apply its statute to market definition, conduct and effects.
The same discipline applies to law-enforcement demands. A request issued in one country may conflict with privacy, secrecy or blocking rules elsewhere. The registry must examine its own legal duties; the member must examine its duties; and neither should imply that a service-region map answers the conflict.
Mandatory law is not a loophole swallowing contractual predictability. It is a defined category. The party invoking it should identify the exact rule, why it cannot be derogated from, whose conduct it governs and which forum can apply it. Vague appeals to national interest are no better than vague appeals to regional authority.
Third parties did not sign the registry clause
Registry agreements are bilateral or membership instruments. Customers, lenders, lessors, cloud providers, transferees, fraud victims, competing claimants and states may be affected by a registry decision without being parties to the agreement. Their claims cannot automatically be sent to the chosen forum or law.
A customer alleging service interruption will usually rely on its contract with the network operator and local law, not the operator’s RIR agreement. A lender asserting security over business assets may face questions under the law governing the security interest and debtor. A claimant alleging fraud in a transfer may bring tort, property or restitution theories outside the narrow service contract.
This does not make the registry clause irrelevant. It may govern contribution, indemnity or duties between registry and member after a third-party claim. It may affect whether the registry acted consistently with its agreement. But it should not be used to erase the independent legal basis of the outsider’s case.
The distinction also matters for remedies. An internal arbitration panel may be able to reverse a service decision between member and registry. It may lack power to bind a liquidator, regulator or customer. A national court may issue an order with broader coercive force but still confront recognition limits abroad.
Governance reports should therefore identify who is bound by each dispute route. Calling a procedure “the appeal” without naming its standing and scope can mislead affected parties. The correct question is: appeal for whom, from which decision, under which agreement, with what power over third parties?
The global importance of number records makes third-party effects inevitable. That is a reason for precise dispute architecture, not a reason to pretend the registry contract has universal reach.
Choice-of-law clauses are useful—and should be narrower than rhetoric
There is a strong defence of home-law clauses. A registry serving dozens of countries cannot efficiently maintain a bespoke contract law for every member. Uniformity reduces cost, supports equal treatment and lets staff and members understand a common framework. It also makes institutional accountability possible in a known legal system.
The contracts show thoughtful variations. RIPE NCC uses a defined internal arbitration route. APNIC selects Queensland courts subject to dispute procedures. ARIN adjusts arbitration locations and recognises defined government constraints. AFRINIC’s agreement expressly refers to operating-jurisdiction law alongside Mauritian law. LACNIC’s establishment materials show conscious adaptation to Uruguay.
The critique is not that these choices are inherently illegitimate. It is that institutional rhetoric sometimes outruns them. If a registry claims authority because a network is “in its region,” it bypasses the contract that actually supplies many of its rights. If it claims that its home law resolves all consequences, it ignores the limited scope of party choice.
A strong registry should welcome the narrower account. It can say: this agreement governs our service relationship under the selected law; these procedures apply to defined disputes; mandatory law and third-party rights remain where applicable. That formulation is both more defensible and more predictable than a broad claim of regional jurisdiction.
Members should also avoid opportunism. A foreign holder should not accept a stable law and forum for years, then deny the clause merely because a dispute arises. The proper challenge is specific: invalid formation, lack of incorporation, mandatory rule, scope, unconscionability, public policy, non-party status or another recognised ground. Cross-border complexity is not a licence to ignore contracts.
The balance is ordinary private international law. Respect chosen rules where they validly apply. Refuse to turn them into powers over people, issues and jurisdictions they do not reach.
The missing case denominator
The public contracts tell us what may happen, but not how often cross-border conflicts actually occur. There is no consolidated dataset showing member domicile, operating countries, governing-law exceptions, arbitration locations, court proceedings, enforcement outcomes or insolvency cases across all five registries.
Without that denominator, several practical questions remain open. Do foreign members use internal arbitration at the same rate as members near the registry’s home? How often do government entities obtain special governing-law terms? How often are awards enforced abroad? Which disputes fail because the member cannot afford the chosen forum? How often do mandatory local rules alter the contractual result?
Publication need not expose confidential files. Registries could report anonymised annual counts by dispute type, member location, procedure, outcome, duration and enforcement status. They could identify whether a case involved contract interpretation, corporate succession, insolvency, sanctions, data, transfer or fraud.
Contract-version data are equally important. A clause quoted from a current agreement may not govern a holder that signed an older version, unless the agreement validly incorporates later text. Public case summaries should identify the applicable version and how it became binding.
LACNIC and AFRINIC need especially clean current captures of governing-law and dispute clauses, alongside historical versions. Establishment documents and a 2017 agreement are valuable, but they should not be mistaken for a complete 2026 contract map.
Evidence would likely show that most cross-border relationships work without litigation. That would support the value of stable clauses. It might also reveal concentrated barriers or recurring uncertainty. Either result is better than assuming the map itself supplies the answer.
A conflict map for a disputed registry act
Every cross-border case should begin with the act, not the address. Is the dispute about an invoice, membership status, refusal of a request, transfer, record change, suspension, termination, deregistration, security service, disclosure or succession after merger? Different acts invoke different instruments and remedies.
Next identify the parties. Record the exact registry legal person and the exact member entity. Add affiliates, transfer counterparties, creditors, customers, officeholders and regulators only where their rights are actually engaged. Do not use a corporate group’s brand as a substitute for legal identity.
Then capture the agreement and version, its governing-law clause, dispute process, amendment route, notice provisions and incorporated documents. Determine whether the disputed act falls within that agreement and whether the claimant is bound by it.
Map corporate connections separately: incorporation, principal place of business, authority of signers, mergers, dissolution and insolvency proceedings. Map operations separately again: routers, licensed services, employees, customers, data processing and performance locations.
Only then test mandatory rules and third-party claims. Identify the exact statute or doctrine and the forum asked to apply it. Determine whether the issue is contractual, corporate, insolvency, regulatory, procedural or non-contractual. Rome I is useful for covered contractual issues in its jurisdictions, not as a universal shortcut.
Finally, examine remedy and enforceability. Which body can order the registry to act? Which can bind the member? Where are assets and records? Will an award or judgment require recognition elsewhere? What interim step best preserves accurate records and running-network continuity?
This map turns “which law follows the IP holder?” into answerable sub-questions. It may produce more than one law, but not confusion. Complexity becomes manageable when each rule is tied to a relationship and act.
Contract drafting for extraterritorial membership
RIR agreements could reduce uncertainty by stating scope more explicitly. A governing-law clause should say that it covers the agreement and parties’ contractual obligations, without purporting to displace mandatory law or determine non-party rights. Several current texts imply this; direct wording would be clearer.
Dispute clauses should identify seat, hearing location, procedural rules, language, interim court jurisdiction, appeal or review, publication policy and enforcement route. “Arbitration” alone is not enough for a member deciding whether the remedy is usable from another continent.
Government and public-body exceptions should be transparent and principled. ARIN’s version 14.0 accommodation is a useful example, but aggregate reporting would show whether it is practical and consistently applied. Comparable treatment rules could prevent quiet bespoke arrangements available only to powerful members.
Insolvency and corporate succession clauses should distinguish verification from substantive control. The registry needs reliable evidence of who may act. It should specify acceptable foreign orders, recognition requirements, temporary record freezes and continuity protections while authority is disputed.
Notice provisions should account for cross-border failure. A single stale email can be a weak foundation for a high-consequence action. Multiple verified contacts, corporate-registry checks and escalation appropriate to the consequence can improve fairness without making ordinary administration impossible.
Contracts should also identify what remains stable during a dispute: public registration, routing-security entities, reverse DNS, pending transfers and access to account records. Preserving the last verified state may be appropriate until an authorised forum decides otherwise.
None of these clauses can eliminate conflicts. They can expose the route through them. Predictability comes not from claiming one law governs the world, but from specifying which law and remedy govern each institutional relationship.
The finding: law follows questions, not addresses
The five RIR legal anchors are real. RIPE NCC’s service agreement selects Dutch law and internal arbitration. APNIC selects Queensland law and courts. ARIN version 14.0 selects Virginia and applicable United States law while varying dispute locations and accommodating defined government requirements. LACNIC’s founding design adapted the predecessor agreement to Uruguayan contract law. AFRINIC’s 2017 agreement uses Mauritian law while acknowledging legal provisions where the parties operate.
Those choices provide order in a global system. They tell members that the bilateral relationship is not governed by an undefined “Internet law.” They connect each registry to an ordinary legal system and a route for accountability.
Their limit is equally clear. The holder’s legal existence comes from its incorporation law. Insolvency may be centred elsewhere. Networks remain subject to regulation where they operate. Customers and creditors may rely on their own contracts and laws. Mandatory rules can apply despite party choice. Awards and judgments may need recognition abroad.
No single law follows the address because an address is not the legal relationship. It is the subject around which several relationships form. The governing answer changes when the question changes.
For registry governance, that is a discipline of modesty. Use the service agreement for service obligations. Use company law for corporate identity and authority. Use insolvency law for the proceeding and estate questions within its scope. Use local public law for regulated operations. Use conflicts rules to decide overlaps. Identify non-parties rather than forcing them into a clause they never accepted.
The extraterritorial member is not an exception to the RIR system. It is the normal member of a global network. Contracts should be written, disputes should be reported and institutions should behave with that fact in view.
An address can be globally unique. The law around its holder will remain plural.