Summary

  • There is no official evidence that LACNIC is leaving the RIR system, facing derecognition or entering emergency operation.
  • A credible transition must move authority without breaking the chain of unique allocation, holder registration, directory accuracy, policy execution and service continuity.

Start with the ledger, not the institution

The phrase “beyond RIRs” invites the wrong first question. It asks what organization might replace a regional Internet registry. The harder question is what must never be lost during replacement.

IANA describes a hierarchical number system: it coordinates global pools, allocates to Regional Internet Registries under global policy, and ordinarily does not allocate directly to network operators. Its documentary index points to RFC 7020 and the system goals of uniqueness, aggregation and registration. Those are not branding attributes of an RIR. They are properties that prevent two parties from receiving incompatible claims to the same resource and allow the rest of the Internet to know which record is authoritative.

For LACNIC, the present record is clear about institutional position but silent about an exit. IANA recognizes LACNIC for Latin America and parts of the Caribbean. The 2002 recognition report tested regional support, neutrality, technical capacity, governance and sustainable operation. Nothing in the closed source set says that recognition is under challenge.

The most useful transition material is therefore also the easiest to misuse. The Number Resource Organization published a second version of a governance document in August 2025. The page labels it a draft. ICANN’s earlier consultation announcement likewise said that the proposed framework would replace ICP-2 only if adopted by ICANN and the RIRs. It is evidence of design work, not evidence of a current LACNIC proceeding.

Five functions that cannot fall between operators

The draft defines RIR services broadly enough to expose the real transition balance sheet: allocation, registration, directory services and related technical services that let holders use resources and let the community obtain accurate holder information. A successor could inherit servers and still fail if it did not inherit lawful authority to update those records. It could inherit authority and still fail if routing-adjacent services or operational knowledge were unavailable.

A transition architecture must therefore close five ledgers:

  1. Uniqueness: one accepted claim for each number resource.
  2. Registration: a defensible chain from allocation or transfer to the current holder.
  3. Policy: a legitimate method for changing the rules and applying them consistently.
  4. Operations: systems, people, credentials, data and procedures capable of continuous service.
  5. Regional authority: support for the entity responsible for a large, non-overlapping service region.

LACNIC’s transfer framework demonstrates the difference between moving an asset claim and moving registry authority. IPv4 blocks may move within or across regions under policy. Eligibility and holder status are checked, and registry information is updated. LACNIC does not become a party to the commercial bargain. The market can discover a price; it cannot make its own registry record authoritative.

What the draft contributes

The draft offers a continuity ladder rather than a revolutionary switch. It would require redundancy and controlled sharing of records, data, implementation procedures and systems sufficient for an Emergency Operator. Emergency operation would require unanimous agreement by the other RIRs and ICANN, publication, community engagement and a limited initial period. Derecognition would follow a presumption in favor of rehabilitation and operate only as a last resort, with a successor or interim handoff if it occurred.

That sequence matters. Repair preserves local knowledge and legitimacy when possible. Temporary operation protects service while facts are established. A successor handoff addresses failure that cannot be cured. Each step changes who controls what, but none permits the registry function to disappear.

Evidence boundary

This is a conditional institutional test. The sources do not establish a LACNIC failure, abuse of discretion, inaccurate registry, continuity defect, proposed successor or live emergency. They also provide no cost estimate or recovery timetable. The draft does not prove that existing arrangements are inadequate, and a policy manual does not prove that every operational control has been tested.

Primary sources: IANA Number Resources, IANA number-system documents, ICANN’s consultation notice, NRO draft Version 2, LACNIC policy manual and LACNIC’s transfer procedure.