Summary

  • According to prior BTW reporting, LACNIC opened a process in June asking legacy IPv4 holders or users to establish contact, identify the organization and justify their right to use the resources. The same reporting says failure to contact the registry or satisfy review may lead to loss of registration services.
  • An independent proposal tracker still lists LAC-2023-4, “Legacy Resources Management,” as under discussion after a 30 June version change. The live administrative process and the unfinished community proposal overlap, but they are not the same authority.
  • LACNIC should publish a case record that names the rule in force, the fact that failed, acceptable substitute evidence, cure and review steps, the last verified registry state and a reversible map of any service consequence.

Two processes now touch the same record

In June, LACNIC called on organizations holding or using legacy IPv4 space to formalize their relationship with the registry, update associated information and substantiate the right to use the resources. BTW's earlier long-form analysis recorded the practical consequence: no contact within the process, or a failed justification after review, can result in registration services being withdrawn.

That is already an operational process. A holder must decide who can answer, which organization is the successor to the name in an old record, and what evidence connects today's network to an allocation made before the modern RIR contract system.

The policy track is not at the same stage. The independent NOG Alliance overview lists LAC-2023-4 as under discussion, with version 4 last changed on 30 June. Its public repository makes the tracker method inspectable rather than asking readers to trust a static status label.

The draft and the call look at many of the same things: contact with LACNIC, justified use, announcement or other evidence of operation, reverse DNS, registration data and an abuse contact. That overlap can be useful. It can also create a constitutional shortcut if a case officer treats the live call as though the community has already settled the draft's conditions.

The safe rule is simple: every action should name its authority. A request made under the June process should say so. A future condition adopted through the policy process should identify its version and effective date. Staff guidance should not quietly bridge the gap by turning an unfinished proposal into a current test.

Operational signals are evidence, not title

Legacy space is difficult because technical activity and legal continuity do not line up neatly. A prefix can be announced by a network that is not the historical holder. A route can disappear because an organization is renumbering, dormant or using the block internally. Reverse DNS can remain correct after a corporate name changes, or become stale while the legal successor remains valid. A working abuse mailbox proves contactability, not ownership.

These signals still matter. They help distinguish a maintained resource from an abandoned record. They show whether the public directory can reach someone responsible. They can expose a hijack, an obsolete delegation or a claim that has no operational trace.

The mistake is letting one signal carry a conclusion it cannot support. Route visibility should not become a title registry. Reverse DNS should not become a corporate succession test. Whois or RDAP fields should not be treated as self-authenticating deeds. Registration hygiene and legal authority are related questions with different evidence.

IPv4 Global's comparative explainer describes why the distinction exists. Legacy addresses were issued before the present policy and contractual framework. RIRs now attach different service arrangements to them, and LACNIC is described as offering services to legacy registrants. The source is a broker and has a market interest, but its narrow historical point is independently useful: modern service status and original allocation history are not the same thing.

That history produces ordinary, not exotic, hard cases. A university may have changed legal form. A public network may have moved between ministries. A telecom asset may have been privatized, divided or merged. A family company may rely on succession papers that do not resemble a modern acquisition file. A dissolved name can have a lawful successor and a live network.

Fraud and abandonment are real. So are weak archives. A sound process has to tell them apart.

A case ledger should show its working

LACNIC does not need to publish private documents to make the process reviewable. It can publish a compact case taxonomy and aggregate outcome ledger.

Each affected holder should receive a record containing the claimed resource, the organization under review, the authority used, evidence categories received, the specific missing or conflicting fact, acceptable substitutes, cure date, reviewer, escalation path and current service state. Public reporting can aggregate those fields without naming sensitive parties.

Reason codes matter. “Insufficient evidence” leaves a holder guessing and leaves outsiders unable to measure consistency. “No proof connecting dissolved entity A to successor B,” “conflicting authorized representatives,” “resource not observed and no alternate use evidence,” or “contact notice undeliverable” identifies a curable fact.

The same discipline should apply to service consequences. Registration services are not one switch. Public holder and contact records, reverse DNS, account access, transfer eligibility, support and other registry functions can fail differently and affect different downstream users. A disputed representative might justify an account lock while the last verified public record remains visible. A stale abuse contact might justify a contact correction without disturbing reverse DNS. Suspected hijack may require a stronger containment step.

The default during a curable review should be the last verified state, not an empty record. That protects third parties who rely on the directory while preserving LACNIC's ability to freeze risky changes. It also makes rollback possible: if review or appeal changes the result, the registry can return to a recorded state instead of reconstructing it after deletion.

Participation cannot certify a case it has not seen

Lu Heng's Bill of Rights of Uniqueness Coordination treats operational continuity, portability and transparency as boundaries on the uniqueness coordinator. The point is not to prevent record cleanup. It is to keep the remedy no broader than the failed fact and to stop registry service from becoming leverage for an unrelated institutional conclusion.

The Multi-Stakeholder Mirage supplies the complementary warning. An open discussion can improve a rule, but attendance is not evidence about every absent holder, old public body or locally documented succession. Policy participation can authorize general criteria after consensus. It cannot certify the facts of a case that participants have never examined.

At the research cutoff, LAC-2023-4 remained under discussion. No public case counts, substitute-evidence map, reason-code set, service-by-service consequence table, appeal outcomes or recovery report were located. The June process may produce clean records and deter false claims. The evidence available does not yet show how consistently it separates abandonment from difficult continuity.

The immediate governance task is therefore not to stop the call. It is to stop the two clocks from becoming one unnamed authority. Outreach can continue. Policy can continue. Every consequence must reveal which one permits it.

Sources