Summary

  • A court order may be legally decisive while still leaving identity, scope and technical sequencing to be verified.
  • LACNIC's agreement and policies make legal documents evidence within registry processes, not self-executing database commands.
  • Continuity is protected by separating reversible safeguards from irreversible changes and keeping a reviewable record.

Authority is not an API call

A court order can settle who may act for a company, restrain a transfer, approve a reorganisation or require a party to deliver control. Those effects can be urgent and binding. But the legal instrument does not usually enumerate the safe sequence for changing registry contacts, authentication credentials, routing certificates and the recognised holder of Internet number resources.

That gap matters because LACNIC administers a unique regional record. Its Registration Services Agreement defines registration and administration services, incorporates policy and allows revocation for specified defaults. The policy manual says number resources are delegated rather than owned as freehold property. A judge may determine rights between parties; LACNIC still needs to identify the resource, authenticate the actor and map the requested outcome to a contract and policy action.

The transfer rules show the bridge. For mergers, acquisitions and reorganisations, legal documents support the request, while LACNIC verifies the transaction and the registry conditions. Ordinary IPv4 transfers also require holder and recipient checks. The document is indispensable evidence. It is not a script that can safely be pasted into an operations console.

Four records must agree

A bounded response keeps four records separate. The legal record identifies the court, case, parties, operative wording and any deadline or stay. The registry record identifies the recognised holder, resources, contacts and current obligations. The technical record shows routing, RPKI, reverse DNS and credential state. The decision record states exactly what LACNIC accepted, deferred or rejected and why.

This separation prevents two symmetric errors. The first is defiance disguised as technical caution: treating every operational complication as a reason to ignore lawful authority. The second is over-compliance disguised as urgency: changing more than the order requires, disabling ordinary service or transferring control before identity and scope are reconciled.

LACNIC's recovery process offers a useful operational analogy. Evidence that an organisation has disappeared can trigger investigation, but the process seeks contact and rectification and uses notice before recovery. Continued routing is not proof of legal entitlement; an unanswered email is not permission for an instant, irreversible change.

Continuity is a control, not a veto

Preserving continuity means holding the stable service state while the requested high-consequence change is authenticated. It may justify protecting logs, freezing non-essential credential changes and preserving ordinary routing. It does not create a power to overrule a binding order. The correct response depends on jurisdiction, parties, wording, urgency, appeal or stay status, holder history, NIR involvement and the documents LACNIC requests.

LACNIC's public, consensus-based policy process supplies the legitimate rules for the registry side of the bridge. Courts supply lawful authority within their jurisdiction. Neither institution should impersonate the other.

Number Resource Society doctrine proposes a narrow operational pattern: authenticate the order, separate reversible safeguards from irreversible action, preserve ordinary service, reconcile the four records and publish only the minimum accountable result. This is a governance proposal, not evidence of LACNIC policy, legal title or the validity of any order.

The test is practical. After execution, can an independent reviewer tell what the court required, what LACNIC verified, what changed technically and what remains disputed? If not, the order may have been obeyed, but the registry has not been governed.

Sources