Recognition in 2002: What ICANN Actually Approved About LACNIC

Summary

• ICANN's 2002 action recognized LACNIC as a Regional Internet Registry eligible to join the ASO arrangement after a staged review, provisional approval and transition plan.
• The operative record tested regional support, bottom-up policy, neutrality, expertise, funding, record keeping, confidentiality and operational readiness, rather than merely accepting a political claim.
• The final joinder and Board proclamation gave institutional coordination status; they did not enact a statute, transfer title to all address holdings, create territorial sovereignty, grant immunity or give LACNIC unlimited control over members' commercial assets.
• The detailed public IANA report is dated 7 November 2002, after the 31 October final action, so it can be used as a published assessment of the criteria but not silently recast as the text before the Board on 31 October.

Start with the operative verbs

The most useful way to read LACNIC's 2002 recognition is to start at the end of the decision chain and ask what the final act actually did. Resolution 02.126 did not describe a continental charter in broad political language. It recorded a Board proclamation that endorsed the President's evaluation and granted final recognition after earlier provisional approval and transition work. The joinder instrument signed around the same moment described LACNIC as approved as a Regional Internet Registry and eligible to become a signatory to the existing RIR-ICANN Memorandum of Understanding for the Address Supporting Organization.

Those are strong verbs, but they are not unlimited verbs.

Recognize, approve, proclaim and join are institutional-coordination verbs. They make LACNIC visible and operational inside a defined Internet-number administration arrangement. They allow the new registry to stand beside the existing regional registries for ASO purposes. They confirm that the applicant had passed enough of the shared recognition test to be treated as a Regional Internet Registry for Latin America and the Caribbean. They also leave many questions untouched. A recognition decision inside ICANN and IANA coordination is not the same as an act of national legislation.

An ASO joinder is not a deed conveying all property interests in number-resource holdings. A proclamation by an ICANN Board is not a grant of sovereign immunity. A registry's practical importance to member operations is not an unlimited power over the commercial assets of those members.

This distinction can sound narrow, but it is not a way to minimize the decision. Registry recognition is consequential because number-resource administration depends on unique, coordinated records and on the community's willingness to treat one body as the place where allocations, policies and registrant data are maintained for a region. Once LACNIC was recognized, network operators in the covered region could not treat the recognition as ceremonial. The recognised registry would become the normal institutional interface for address and autonomous-system administration in its service area. That dependence is substantial.

It still has to be described in the language of the instruments that created it.

The 2001-2002 record is therefore best read as an operative-verb audit. Each document should be asked the same questions: who wrote it, what did it do, what condition did it test, what immediate effect did it have, and what enlarged claim did it leave unsupported? That method prevents two opposite mistakes. One mistake is to treat recognition as a minor administrative note with no real force. The other is to treat practical registry dependence as if it automatically proves sovereignty, full property transfer, immunity or general commercial control. The record supports neither extreme.

The exact chronology matters. ICANN accepted ICP-2 on 4 June 2001. LACNIC's application is dated in the relevant recognition materials to 28 November 2001. ICANN's Board gave provisional approval on 14 March 2002 through resolutions 02.28 and 02.29. The joinder instrument was signed on 30 October 2002. The Board proclamation followed on 31 October 2002 under resolution 02.126. The public IANA report carrying the detailed criterion-by-criterion assessment is dated 7 November 2002. The transition plan identified 18 November 2002 as the target for independent operations. That sequence is not decorative.

It separates criteria from application, application from provisional decision, provisional decision from operational migration, final decision from public assessment, and final decision from planned cutover.

The docket of acts and silences

The docket below is a reading tool rather than a substitute for the underlying instruments. It keeps the documents distinct because the recognition record can be overstated when all texts are collapsed into a single founding moment.

Document or act	Author or institutional setting	Tested condition	Immediate effect	Unsupported enlarged claim
ICP-2, accepted 4 June 2001	ICANN-recognized criteria for new regional registries	Continental scale, substantial ISP support, bottom-up policy, neutrality, technical expertise, stable funding and record keeping	Supplied the checklist by which a new registry could be judged	Did not convey ownership of address resources or create a permanent public-law code
Application for Formal Recognition, 28 November 2001	LACNIC applicant submission	Coverage, community support, governance, funding, operations, records and confidentiality	Put LACNIC's case before ICANN and IANA	Did not independently prove every assertion or bind national legal systems
Resolutions 02.28-02.29, 14 March 2002	ICANN Board provisional action	Revised evidence and successful transition	Gave provisional approval subject to further conditions	Did not complete final recognition or prove operational cutover
Transition Planning Activities, 25 June 2002	LACNIC transition planning record with ARIN-linked migration work	Records, billing, agreements, second-opinion services and activation planning	Made the proposed registry operationally credible	Did not establish every completed transfer or define title to all historical records and resources
Joinder and Board proclamation, 30-31 October 2002	LACNIC, existing RIR-ICANN MoU structure and ICANN Board	Eligibility to join the ASO arrangement after evaluation	Approved LACNIC as an RIR and made joinder effective under the Board proclamation	Did not grant territorial sovereignty, immunity or unlimited commercial power
Public IANA report, 7 November 2002	IANA published assessment	Criterion-by-criterion recognition review	Recorded why the criteria were treated as satisfied	Did not prove that the posted text was before the Board on 31 October

This docket gives the strongest institutional case full weight. Recognition was not instantaneous. It passed through criteria, an applicant record, a provisional Board decision, transition planning, final proclamation and a published IANA assessment. ICANN did not simply accept a regional demand because it was politically attractive. The materials tested whether a proposed registry could operate at regional scale, maintain records, follow bottom-up policy, remain neutral, fund itself and connect to existing Internet-number coordination.

The same docket limits the result. None of the listed acts purports to be a statute enacted by a sovereign legislature. None says that all address holdings in the region became LACNIC's proprietary assets in a broad commercial sense. None creates territorial sovereignty. None says that LACNIC may disregard its members' ordinary contracts, national law or commercial interests because it has been recognized as an RIR. None resolves the background legal effect of number resources under Uruguayan, United States or member-country law.

The recognition record can be decisive for coordination status while remaining silent on those broader questions.

ICP-2 supplied a recognition test, not a title instrument

The first document in the chain is ICP-2: Criteria for Establishment of New Regional Internet Registries. Its importance is structural. It created a common test for evaluating a new Regional Internet Registry. The criteria included a continental scale, substantial support from Internet service providers in the proposed region, a bottom-up policy structure, neutrality, technical expertise, adequate funding and reliable record keeping. In the LACNIC matter, ICP-2 meant the question was not only whether Latin America and the Caribbean wanted a registry. The question was whether the proposed body met a registry model already defined by the existing coordination community.

That makes ICP-2 powerful evidence against the idea that recognition was merely symbolic. A body that fails neutrality, funding, policy or record-keeping tests cannot safely become a unique regional registry. The recognition system had to ask whether LACNIC could keep accurate records, maintain confidentiality, operate services, support members and participate in global coordination. Those were not decorative matters. In number-resource governance, inaccurate records or unstable operations can create real harms for networks that depend on routing, registration and policy continuity.

ICP-2 also has a boundary. It is a recognition standard, not a title document. It tells the evaluator what conditions a new RIR should meet. It does not say that a new registry receives proprietary ownership of every address-resource holding administered in the region. It does not enact a continuing accountability constitution that answers every later dispute. It does not itself create a territorial public authority. It is a checklist for establishment, drafted around the existing regional-registry model, not a conveyance of private assets or an exhaustive legal code.

This point matters because the criteria can be read too heavily. If ICP-2 requires record keeping, one might be tempted to say the registry owns the records in every sense. The text does not do that. If ICP-2 requires neutrality, one might be tempted to say neutrality supplies immunity from commercial challenge. The text does not do that either. If ICP-2 requires substantial regional support, one might be tempted to say support becomes perpetual consent to every later act. Again, the criteria do not carry that meaning. They support recognition if satisfied. They do not settle all future rights.

The recognition test still shaped the later evidence. LACNIC's application had to address coverage, community support, policy structure, operations, funding, records and confidentiality because those were the kinds of questions ICP-2 made relevant. The provisional decision had to remain conditional because a checklist is not satisfied by aspiration alone. The transition plan had to show how the proposed registry would become technically and administratively real. The final proclamation had to stand on an evaluation that the criteria had been met. In that sense, ICP-2 is the spine of the record, but it is not the whole body.

The application made LACNIC's case, not the final ruling

The 28 November 2001 application is the applicant's case for recognition. It described proposed regional coverage, support, governance, funding, operations, records and confidentiality. It was essential because the evaluator needed a concrete institution to examine. Recognition could not be granted to an abstract regional desire. LACNIC had to present a service area, a support base, a governance design, operational plans and administrative practices capable of satisfying the ICP-2 model.

The application is therefore evidence of what LACNIC claimed and offered. It shows that the applicant understood recognition as a test of institutional capability, not simply as a political assertion of regional identity. It also shows that the record was built around ordinary registry questions: who is covered, who supports the body, how policy is made, how services are funded, how data is maintained, how confidentiality is handled, and how the transition from existing arrangements can occur without breaking service.

At the same time, the application is not independent proof of everything it says. Applicant submissions always have that limit. They can be accurate, well-supported and useful, but they remain submissions made by the body seeking recognition. The current LACNIC page carrying the application has a heading that refers to 2002, while the recognition materials and joinder recitals date the application to 2001. That discrepancy does not defeat the substance, but it is a reminder to use the application carefully: it is part of the file, not the final legal act.

The application also cannot be turned into a property transfer. Statements about operations, records or confidentiality can support the conclusion that LACNIC planned to administer registry functions. They do not, by themselves, prove that every pre-existing record, contract, liability or resource claim moved to LACNIC in a particular legal form. For that, one would need executed schedules, transfer agreements, legal opinions or other transaction-specific evidence. The application helps explain why recognition could be considered. It does not answer every question about rights in the things to be administered.

Its strongest contribution is practical. The application gave ICANN and IANA a basis for asking whether LACNIC had enough regional support, governance capacity, funding and operational readiness. Without such a submission, provisional approval would have rested on slogans. With it, the Board could conditionally approve a transition and ask for revised evidence. The application thus marks the point where regional ambition became an administrable case.

Provisional approval kept recognition conditional

The March 2002 Board action matters because it prevents a false reading of recognition as a single leap. Resolutions 02.28 and 02.29 gave provisional approval subject to a revised application and successful transition. In ordinary institutional terms, provisional approval is a serious sign. It tells the applicant that the Board is prepared to proceed if stated conditions are satisfied. It also tells the applicant that the matter is not complete.

That conditional character is central. A provisional approval does not have the same force as final recognition. It does not automatically make the applicant the recognised RIR. It does not eliminate the need for operational migration. It does not erase the evaluator's need for updated evidence. It creates a path, not a completed status. If one reads March 2002 as final recognition, the later joinder, proclamation and assessment become redundant. The chronology shows they were not redundant.

Provisional approval also clarifies the kind of due care ICANN was applying. The Board did not merely say that LACNIC had a good idea. It required a revised application and successful transition. Those conditions tie the decision to evidence and operational performance. They also reflect the high cost of error in regional registry administration. If a new RIR is recognized before it can keep records, bill members, handle agreements and coordinate with existing registries, the result could unsettle the networks that depend on continuity.

The decision remains bounded. A conditional Board action inside ICANN does not decide national property law. It does not prove that all transition tasks later happened as described. It does not show the terms of every agreement between ARIN, LACNIC and affected resource holders. It does not supply the missing staff papers, objections or alternative models considered between March and October. It is evidence that ICANN had moved from initial review to conditional approval, not evidence that every legal and commercial question was solved.

This is where the narrow reading and the strong case meet. The strong case says recognition had real institutional discipline: LACNIC had to move through a transition before final status. The narrow reading says the condition itself does not grant powers beyond its words. A conditional path to registry recognition is important precisely because final recognition would be important. It still remains a path defined by the documents.

Transition planning made capability credible

The June 2002 transition planning record supplied the practical middle of the chain. It specified work around records, billing, agreements, second-opinion services and planned operational activation after final recognition. It also made ARIN part of the story because LACNIC's emergence required migration from existing arrangements into an independent registry serving Latin America and the Caribbean. Without that migration work, the recognition decision would have been institutionally thin.

Transition planning matters for three reasons. First, it shows that recognition was not only about governance design. It required databases, billing arrangements, member agreements and service procedures. Second, it shows that existing registry functions had to be preserved while a new regional institution came into being. Third, it shows why final recognition could reasonably be tied to operational readiness. A regional registry is not useful if it exists on paper but cannot administer the records and services its members need.

The planned 18 November 2002 activation date is especially easy to overstate. It was a target date for independent operations. A target date is not proof that every cutover step occurred on that date, that every record was transferred in a particular form, or that every legal obligation was allocated exactly as later entities might assume. It is evidence of planned operational timing, not a full closing binder. The distinction matters because title, liability and data-control questions may depend on documents not present in the fixed record.

Second-opinion work also illustrates the difference between function and legal status. A second-opinion function can show that the new registry was being integrated into existing allocation discipline. It helps demonstrate technical and administrative competence. It does not decide whether number resources are property, whether they are contract rights, whether they are revocable administrative entries, or how those concepts interact with local law. The transition plan can show operational architecture without resolving property theory.

The transition record supports the practical-authority case. Once LACNIC could maintain records, bill members, handle agreements and provide registry services, members in the region would depend on it. That dependence is not imaginary. It is the practical center of RIR status. But dependence created by unique coordination is still different from unlimited legal power. The registry becomes the effective place where certain functions happen. It does not become a legislature, a court or the owner of everything it touches merely because those functions are important.

Joinder changed LACNIC's coordination status

The decisive institutional step is the Joinder of LACNIC into RIR-ICANN Memorandum of Understanding, signed on 30 October 2002 and made effective through the Board proclamation on 31 October. The joinder language approved LACNIC as a Regional Internet Registry eligible to sign the ASO-MoU and made the joinder effective on Board proclamation under resolution 02.126. This is the point at which the recognition chain moved from conditional preparation into final institutional placement.

The immediate effect was not abstract legitimacy. LACNIC became a recognized RIR inside the global address-supporting structure. It could stand in the ASO arrangement with the other regional registries. Its region's number-resource administration could be treated as part of the recognized RIR system. That is a major institutional effect because the RIR system relies on shared acceptance. If the rest of the coordination structure treats a registry as the recognized regional body, that body becomes practically central to members, policy development and address-resource administration.

The joinder also defines the limit of the act. It is an institutional coordination instrument. It does not purport to grant sovereign regulatory power. It does not claim to be enacted by governments in Latin America and the Caribbean. It does not say that LACNIC owns every address-resource interest as a matter of property law. It does not create sovereign immunity. It does not give LACNIC unlimited authority over the commercial assets of its members. Its language is about RIR approval and ASO-MoU eligibility, not territorial rule.

That limitation should not be confused with weakness. Many institutions matter because other institutions accept them as the relevant point of coordination. The joinder made LACNIC's status legible to ICANN, IANA and the existing RIR community. It gave members and operators a reason to treat LACNIC as the regional interface. It connected LACNIC to the ASO mechanism. These are serious effects in Internet governance, where operational coordination can be more important than formal public-law categories.

Still, the joinder cannot bear claims its text does not make. If someone argues that recognition transferred title to all number-resource holdings, the joinder should be asked to identify the transferring parties, property, consideration, schedules and governing law. It does not. If someone argues that recognition created territorial sovereignty, the joinder should be asked to identify the sovereign source of that power. It does not. If someone argues that recognition gave LACNIC immunity from ordinary member claims, the joinder should be asked to identify the immunity grant. It does not.

The instrument is powerful within its institutional lane and silent outside it.

The 7 November report records assessment after the decision

The IANA Report on Recognition of LACNIC as a Regional Internet Registry is valuable because it published a criterion-by-criterion assessment and concluded that LACNIC met the requirements for approval and recognition. It gives the reader the most detailed public account in this record of how the recognition criteria were treated as satisfied. For that reason, it should be used seriously.

The date also has to be used seriously. The public report is dated 7 November 2002. The final Board action occurred on 31 October 2002, after the 30 October joinder signature. The Board record endorsed the President's evaluation, but absent an earlier version of the report, the posted 7 November text should not be described as the document before the Board or as a public precondition to the 31 October decision. It is a published IANA assessment inside the ICANN and IANA recognition system, not proof that its posted form preceded the decision.

This is more than a chronological footnote. Decision records often become cleaner after an act has occurred. A later public assessment can accurately explain criteria and reasoning while still not being the exact decision file available at the moment of action. If the distinction is ignored, the analyst may unintentionally reverse cause and publication. The safer reading is that the Board endorsed an evaluation, and IANA's 7 November report publicly records a detailed assessment consistent with recognition. The public report should not be made to do more than its date permits.

The report also remains institutionally bounded. It assesses criteria for recognition. It does not stand outside ICANN and IANA as an independent judicial ruling. It does not resolve background national-law questions. It does not supply the complete revised application package, quantify every support denominator, publish all staff papers or include every objection and alternative model considered before the final act. It is a strong assessment for recognition purposes and a limited record for broader legal claims.

Used correctly, the report strengthens the narrow conclusion. LACNIC was not simply waved into existence. The criteria were assessed, and the conclusion was that approval and recognition were warranted. That supports the claim that recognition had a disciplined basis. The same report's function confirms that the basis was an RIR-recognition basis. It evaluated whether LACNIC could be a regional registry under the accepted criteria, not whether LACNIC acquired sovereignty, title or immunity.

The strongest practical-authority case

Before testing enlarged claims, the strongest case for LACNIC's practical authority should be stated in full. A recognized RIR is not just a trade association with a useful mailing list. It administers unique records and procedures on which network operators depend. If an operator needs number-resource services in the covered region, the recognized registry becomes the central institutional counterparty. Policy development, allocation records, membership administration, confidentiality practices and coordination with global structures all converge there.

The 2001-2002 record supports that practical case. ICP-2 supplied criteria meant to protect the integrity of regional registry administration. The application addressed coverage, support and operating capacity. Provisional approval forced the matter through a transition. The transition plan dealt with records, billing, agreements and activation. The joinder placed LACNIC into the recognized RIR and ASO structure. The IANA assessment explained why the criteria were treated as met. Together, those texts produced more than a press release. They produced an operational institution with recognized coordination status.

That status can create substantial dependence even without public-law sovereignty. A member may experience registry policy as more immediate than a statute because registry records and procedures are the way it maintains resources. A policy change can affect allocation practice, documentation duties or routing-security preparation. A record-keeping failure can create risk. A confidentiality rule can affect business information. In that practical sense, recognition created a center of authority that operators could not casually ignore.

The practical case is also the best answer to a too-narrow critique. If someone says recognition did nothing because it was not legislation, the record says otherwise. ICANN and IANA coordination was the place where RIR status was recognized. The existing regional-registry model was the model ICP-2 used. Joinder into the ASO-MoU arrangement made LACNIC part of the common structure. The absence of a statute does not mean the absence of governance effect.

But practical authority is not the same as unlimited authority. Institutional dependence must still be traced to the functions the instruments confer. LACNIC could be the recognized RIR without being a sovereign government. It could administer regional registry services without owning every commercial interest of its members. It could maintain records without having a title deed to all related assets. It could join ASO coordination without receiving immunity from every possible claim. The strongest case for practical authority is therefore compatible with the narrow legal reading. It is not a contradiction.

Testing the ownership claim

The first enlarged claim to test is ownership. Did the 2002 recognition record transfer title to all address holdings or related commercial assets in the region? The answer from these texts is no. The record shows recognition, transition planning and joinder. It does not show a conveyance of property title. It does not identify every asset being transferred, every party transferring it, every member interest affected, every governing-law clause or every schedule of rights and liabilities.

That does not mean there were no agreements. The transition plan refers to agreements, records and billing. The existence of agreements is plausible and operationally necessary. The point is that the fixed public record does not supply the executed schedules that would be needed to decide broad ownership questions. A plan that says records and services will be migrated is not identical to a legal instrument proving title in every relevant asset.

Number resources themselves also require careful language. The recognition materials treat registry administration as a coordinated function. They do not define number resources as ordinary property owned by the registry in a broad commercial sense. They do not decide whether resource holders have contract rights, administrative expectations, policy-bound usage rights or other interests under applicable law. Those questions may matter, but they are not answered by the recognition instruments.

The ownership claim is therefore too large for the record. The record can support a narrower statement: LACNIC became the recognized registry institution responsible for regional administration within the ICANN, IANA and RIR coordination model. It cannot support the broader statement that recognition itself conveyed all resource-related title or all commercial assets to LACNIC. If that broader claim is made, the missing evidence is not a minor inconvenience. It is the evidence that would be needed to prove the claim.

This conclusion protects both sides. It prevents critics from ignoring LACNIC's recognized administrative role. It also prevents the recognized administrative role from being overstated into general ownership. Registry authority and title are related in practice but not identical in law. The 2002 instruments establish the former within the coordination system. They do not establish the latter in the broad form sometimes implied by recognition rhetoric.

Testing the territorial-sovereignty claim

The second enlarged claim is territorial sovereignty. Did ICANN's recognition create a sovereign regional authority for Latin America and the Caribbean? Again, the answer from the instruments is no. ICP-2 is a recognition standard. The application is an applicant submission. The provisional resolutions are Board actions. The transition plan is an operational plan. The joinder is an ASO coordination instrument. The IANA report is a recognition assessment. None is a treaty among states. None is a national statute. None identifies a sovereign power being delegated by governments to LACNIC.

This does not make the region irrelevant. The region is central because RIR status is regional. LACNIC had to show coverage and support for Latin America and the Caribbean. It had to become the recognized registry for that service area. The regional dimension is part of the function. But a service region is not territorial sovereignty. A registry can be regionally scoped without possessing public-law dominion over territory.

The distinction matters because Internet governance often borrows public-law vocabulary. Words like recognition, region, authority and policy can sound governmental. In this record, they operate inside a technical coordination system. That system has public consequences because networks and users depend on it. It still does not become a state. The instruments do not give LACNIC police powers, taxing powers, legislative powers or territorial jurisdiction in the way those terms are used for governments.

The strongest version of the regional claim is practical. LACNIC's recognized service area made it the relevant registry for covered members and resources. That creates a form of jurisdiction in the administrative sense: if a resource falls within the registry's service model, LACNIC is the institution that handles the relevant registry functions. But administrative scope inside the RIR system is not sovereignty. It is a bounded coordination role.

The unresolved legal questions remain outside the record. National laws may affect contracts, corporate status, data, member rights, liability and judicial remedies. The recognition texts do not decide how Uruguayan law, United States law or the laws of member countries would treat every dispute. They define institutional recognition within the ICANN and IANA arrangement. That is enough for registry coordination and not enough for territorial sovereignty.

Testing immunity and unlimited commercial control

The third enlarged claim is immunity. Nothing in the 2002 recognition record grants LACNIC sovereign immunity. A registry may have legal personality under the law of its host jurisdiction. It may have contracts, internal rules and dispute procedures. It may have policy authority inside the RIR system. Those features are not immunity. Immunity would need a legal basis, and the recognition documents here do not supply one.

This point is simple but important. A body can be recognized as essential to global Internet coordination and still be subject to ordinary legal constraints. A court or regulator may or may not accept a particular claim against it depending on jurisdiction, contract terms and applicable law. The recognition instruments do not answer those questions in advance. They do not say that LACNIC's acts are beyond challenge because ICANN recognized it as an RIR.

The fourth enlarged claim is unlimited commercial control over members' assets. The record does not support that either. Registry administration can affect members deeply because number-resource records are central to network operations. Policies can impose conditions. Agreements can create duties. Billing can matter. Confidentiality practices can affect business data. But the instruments do not say that recognition allows LACNIC to control all member assets or business decisions.

Here again, the practical effect is real but bounded. If a member depends on LACNIC for registry services, LACNIC's rules can have operational consequences. That is not the same as a general power over the member's commercial estate. The recognition record recognizes a registry and its coordination role. It does not make LACNIC the owner, regulator or manager of every asset a member uses to run its business.

The distinction is not semantic. It affects how disputes should be framed. A challenge to a registry policy is not automatically a challenge to sovereignty. A dispute over a contract or record is not automatically a dispute over ownership of the Internet. A member's dependence on registry records is not automatically consent to every possible act. The 2002 record supports institutional authority, but it does not erase ordinary questions about agreement, due process, applicable law and evidence.

What the documents leave unresolved

Several evidence gaps remain visible once the operative effects are kept in their lane. The first is the full revised application package and the evidence used to quantify substantial-majority ISP support. The record shows that support was a criterion and that LACNIC claimed support. It does not provide every denominator, objection, dissenting view or method used to measure that support. Without that, one can say support was assessed, but one cannot fully reconstruct the support count.

The second gap is the internal ICANN staff record between provisional and final approval. There may have been working papers, objections, alternatives, risk assessments or legal notes. The fixed materials do not provide them. The Board record endorses the President's evaluation, and the IANA report later publishes a detailed assessment. That is enough for a recognition reading. It is not enough to know every argument considered before the final act.

The third gap is the executed transition detail. The transition plan identifies records, billing, agreements, second-opinion services and activation planning. It does not provide every executed schedule distinguishing databases, service contracts, liabilities and number-resource claims. Those schedules would be necessary for a more precise account of which things moved, on what terms and under what law.

The fourth gap is contemporary legal advice. The recognition record does not include advice on the effect of recognition under Uruguayan law, United States law or the law of every affected member country. That absence matters because some enlarged claims depend on national-law consequences. The public ICANN and IANA materials can show what the coordination system recognized. They cannot substitute for legal analysis under every relevant jurisdiction.

These gaps do not defeat the recognition. Many institutional decisions are valid without publishing every supporting paper. The point is narrower: the gaps prevent readers from using the public recognition record to prove claims beyond the public recognition act. The record is strong enough to show recognized RIR status and ASO eligibility after transition. It is not strong enough to prove proprietary title, sovereignty, immunity or unlimited commercial control.

The operative-effect ruling

The best reading is therefore bounded and consequential. ICANN's 2002 action approved LACNIC as a Regional Internet Registry eligible to join the ASO arrangement after an ICP-2 transition. The record confirmed that LACNIC had been judged capable of regional registry service, policy participation, operational continuity, record keeping, funding and coordination. It brought LACNIC into the recognized RIR structure for Latin America and the Caribbean. That is the operative effect.

The same record did not do several things that are sometimes smuggled into recognition language. It did not enact a statute. It did not create territorial sovereignty. It did not grant sovereign immunity. It did not transfer title to all address holdings or all member commercial assets. It did not decide every national-law question. It did not publish the whole Board file or every transition schedule. It did not make the 7 November public IANA report a document known to have preceded the 31 October Board decision.

This ruling gives practical uniqueness its proper weight. A recognized RIR has substantial authority because the system needs one coordinated registry for the region. Members depend on that registry's records and services. That dependence is a fact of institutional design. But it is not a license to infer powers that the instruments do not contain. The recognition record creates coordination status and registry authority inside the ICANN, IANA and ASO system. It does not create a sovereign public authority or universal property owner.

The unresolved evidentiary question is also narrow: what did the complete revised application, internal evaluation file and executed transition schedules say about support, records, liabilities, contracts and number-resource claims? Until those materials are available, the public record can support the coordination conclusion with confidence, but it cannot support broader claims about title or national-law effects. That is not a weakness in the core recognition finding. It is the line between what ICANN actually approved and what later rhetoric may want the approval to mean.