Summary

  • LACNIC’s transfer rules create an option over timing: a completed transfer changes the registered holder, makes the event public and starts separate one-year constraints for the source and the transferred space.
  • The policy manual also imposes a three-year seasoning period on new LACNIC allocations, while a proposal to recognise temporary transfers remained under discussion. The governance problem is not to presume hoarding, but to make the exercise and non-exercise of these options observable.

The decision before the transaction

The scarce asset in a mature IPv4 portfolio is not only a count of addresses. It is the ability to postpone a decision while preserving customer continuity, routing history, reverse-DNS arrangements, abuse contacts, ROAs and internal migration plans. None of those facts proves that every retained prefix is efficiently used. They do show why a block can carry contingency value even before anyone names a transfer price.

For an incumbent, the critical moment arrives when waiting ends. Under section 2.3.2.18 of LACNIC’s Policy Manual, a transfer may occur within the region or between RIR regions. The minimum unit is a /24. A recipient in the LACNIC region must justify the IPv4 resources, the responsible registry verifies the holder and checks for a dispute, and intra-regional parties submit signed legal support. Once completed, LACNIC changes the holder information and records the event in a public transfer log.

That is a real change of institutional state. Before the transaction, the holder retains the choice. After it, the ledger, the parties and several deadlines have moved.

Three clocks, not one price

The first clock applies to the source. For one year after the registered transaction, the source becomes ineligible to receive IPv4 allocations or assignments from LACNIC. In the exhaustion era that sanction may have limited practical reach for an established holder, because ordinary free-pool space is not generally available to incumbents. It still expresses a rule: an organisation should not transfer space and immediately seek replacement resources from the registry.

The second clock follows the addresses. Space that has been transferred cannot be transferred again, in whole or in part, for one year. A buyer therefore receives recognised control, but not an immediately re-tradable instrument under the policy. The lock reduces rapid cycling and also makes timing part of the deal’s value.

The third clock begins earlier. Addresses newly allocated or assigned by LACNIC cannot be transferred for three years. That seasoning period separates a recent allocation from an older portfolio whose transfer option is already exercisable.

These rules do not disclose the commercial price of the option. They define part of its exercise cost. A holder that transfers today gives up the ability to reverse that registered-holder change through the ordinary permanent-transfer mechanism. Waiting preserves the choice to transfer later, to use the block for an operational contingency, or to keep reassessing an IPv6 migration. The policy does not say those choices are equally legitimate. It does make them institutionally different.

The non-return rule changes the baseline

Section 2.3.6 of the same manual is unusually direct. It says that the implementation of transfers removes the requirement to maintain the original need justification and that returning resources is no longer required in failed transfers or mergers and acquisitions. The provision should be read narrowly: it does not declare address space to be freehold property, guarantee routability or erase contractual duties. It does alter the governance baseline. The recognised holder is not operating under a standing rule that every change in use automatically sends surplus space back to LACNIC.

That makes optionality more than a metaphor. If a portfolio can remain registered while the holder considers a permanent disposition, the right to delay has institutional support. The appropriate response is not a presumption of bad faith. It is better evidence about which pathways holders actually use.

A proposed reversible state

LACNIC’s policy system exposes the unresolved issue. LAC-2023-7, last shown as under discussion after an August 2025 revision, starts from the premise that current policy recognises permanent transfers only. Its author proposes temporary intra-regional transfers with recorded start and end dates and restoration of the prior holder information at the end.

The proposal’s claims must remain attributed. Its author argues that a controlled temporary transfer could operate like leasing, help smaller or financially weaker recipients and support an IPv6 transition. Those are policy arguments, not measured outcomes and not an adopted LACNIC position. The proposal nevertheless reveals a precise gap: the current registry has a completed permanent-transfer state, but no adopted, time-bounded transfer state that returns the record to the original holder.

That gap can reward waiting. A holder that wants reversibility may prefer not to execute a permanent transfer. Outsiders then cannot tell, from the transfer log alone, whether the block is an operational reserve, part of a private use arrangement, awaiting a corporate event or simply being held for a later decision. BGP visibility does not solve the problem. An unannounced prefix may be idle, staged, filtered, reserved for failover or used in a way a distant collector cannot see.

Fees are evidence of carrying structure, not motive

LACNIC’s 2026 ISP fee schedule adds another bounded fact. Annual membership fees are based on the highest category determined by the total IPv4 or IPv6 resources assigned. The schedule also says paid fees are not refunded because of service cancellation, resource return or category change.

This does not prove that the fee system causes retention. IPv6 holdings may determine the category; returning enough space may affect a future invoice; security, customer commitments and renumbering costs may dominate the calculation. The narrower inference is sound: observed use inside an already assigned portfolio does not itself determine the annual category, and a mid-cycle return does not create a refund. The immediate registry-fee reward for surrendering slack may therefore be weak or absent in a particular case.

A regional record with national seams

LACNIC is a regional authority operating through more than one administrative path. Organisations in Brazil and Mexico request resources through their national registries. LACNIC has also described the implementation of inter-RIR transfers as coordinated work across WHOIS, RPKI, IRR, reverse DNS and other systems. A legally simple instruction to change the holder is operationally a multi-surface update.

That context matters for legitimacy. A transfer rule cannot be judged only by the text at the regional centre. Holders and recipients need consistent evidence, timing and remedies across LACNIC and the NIR paths. If a reversible state is ever adopted, it would need clear authority over the end date, restoration of records, abuse responsibility, ROAs, routing registries and disputes. Otherwise “temporary” would describe a contract without producing a dependable registry state.

What the public record cannot establish

The bounded public sources do not disclose negotiated transfer prices, the scale of private leasing, portfolio-level utilisation or the number of attempted transactions that were rejected, withdrawn or abandoned. They do not establish that fee tiers cause retention. They do not support accusing any named holder of hoarding, speculation or evasion.

Those limits are not a reason to abandon scrutiny. They define the data LACNIC could publish without adjudicating motives: quarterly counts of applications, approvals, withdrawals and rejections; median processing time; block-size cohorts; the use of transfer, return and corporate-event pathways; and reasons expressed in controlled categories. A separate policy ledger could show the status, safeguards and implementation cost of any proposed temporary-transfer mechanism.

The institutional test is simple. Scarcity gives an older portfolio choices that a new network does not possess. LACNIC cannot erase that history. It can make the moments at which those choices are exercised visible, explain the rules that attach to them and provide a reviewable path when the registry record and operating reality diverge. Optionality should be measured before it is moralised.

Sources