Summary

  • An airport slot is permission to plan an operation within declared capacity, not ownership of a runway, a route franchise or a command about where to fly.
  • Historic precedence gives continuity when a series meets its required use rate. The 80:20 rule attaches priority to performance, while justified non-use protects holders facing exceptional conditions.
  • Secondary exchange reveals that historic positions can carry substantial value even when coordinator confirmation remains necessary. Value is not the same as unrestricted title.
  • Competition safeguards operate beside historic rights. Pools for newly available slots, new-entrant preferences, misuse sanctions and targeted slot-release commitments address access problems without erasing every incumbent holding.
  • IPv4 governance should adopt the institutional structure, not the aviation metric: recognise old holdings, record transfers and verify authority while operators control deployment.
  • Intervention should identify the exact harm, power, evidence, affected range, remedy and review path. Scarcity alone does not authorise confiscation.

A slot is permission within capacity, not ownership of the airport

At a fully coordinated airport, demand at particular times exceeds the runway, terminal, stand or airspace capacity available. The slot system converts that physical constraint into a schedule that airlines can plan before passengers arrive and aircraft move. The European slot regulation defines a slot through permission given by a coordinator to use the full range of airport infrastructure necessary for an operation on a specific date and time. The permission is important because an unscheduled arrival at a saturated airport can impose delay on every other user.

That definition contains two boundaries. First, the capacity belongs to an airport system with declared operating limits; a slot does not convey a piece of concrete or airspace. Second, the airline remains responsible for the flight. It chooses a commercially and legally permitted route, aircraft, fare, service pattern and network connection. The coordinator matches requested operations to available capacity. It does not sell tickets, employ pilots or determine whether a route should serve tourists, freight, families or corporate travellers.

The United Kingdom's airport slot reform consultation states the point directly: coordination cannot increase airport capacity. It is an administrative method for using existing capacity within operational and environmental limits. The airport declares parameters. Airlines propose schedules. The independent coordinator allocates and monitors slots under applicable rules.

This division is the first useful comparison with IPv4. A number registrar can record one current holder for a unique range, authenticate changes and coordinate transfer. It does not thereby become the network operator. Whether an address is announced, from which facilities, through which upstreams and for which lawful customers remains an operational matter. RFC 7020 expressly places route announcement and the manner of advertisement outside the Internet Numbers Registry System.

The analogy is therefore institutional rather than physical. A slot manages simultaneous claims on finite airport capacity; an IPv4 record preserves uniqueness in finite numerical space. In each case, the administrator's legitimacy is strongest when it performs the narrow coordination task well and weakest when scarcity is used to claim authority over the user's business.

Historic precedence converts repeated performance into planning certainty

Airport schedules are seasonal. Airlines commit aircraft, crews, maintenance, gates, sales and connecting banks long before a season begins. If every slot were reassigned from zero at every seasonal conference, even a successful route would face repeated administrative risk. An airline could invest in developing traffic only to lose the time after proving the market for a rival.

Historic precedence addresses that risk. Under the normal 80:20 rule, an airline that operates a series of slots at least 80 percent of the relevant season receives priority for the same series in the next equivalent season. The Worldwide Airport Slot Guidelines, jointly published by IATA, Airports Council International and the Worldwide Airport Coordinators Group, organise the practical coordination method used across many Level 3 airports. Their stated objectives combine continuity, consumer choice, connectivity, competition, transparent allocation and efficient capacity use.

The word historic can be misleading. Priority does not arise merely because an airline's name appeared decades ago. It is refreshed by qualifying use in the most recent comparable season. A winter series supports a claim to the next winter, not automatically to a summer time for which the operating pattern is different. The relevant unit is a series, not an airline's entire presence. Time changes and schedule details can be treated under published rules without dissolving the underlying continuity.

This arrangement recognises reliance without declaring an unconditional estate. The airline can plan because compliant performance normally leads to renewal. The public receives a stable timetable. Airports can plan facilities around known demand. Connecting networks can form around repeated times. At the same time, the right remains attached to a defined series and a use condition.

Historic IPv4 holdings also embody reliance. Networks were built, customers addressed, contracts written, security controls established and corporate transactions completed on the assumption that a recognised range would remain available. Some holdings predate current regional institutions. A just registration order does not erase that reliance because today's administrator would have allocated differently. It identifies the holder, preserves the history and applies prospective, published rules to later changes.

Use-it-or-lose-it is a renewal condition, not a seizure slogan

The phrase use-it-or-lose-it sounds punitive when detached from its design. In airport coordination, it is not a free-standing declaration that an administrator can take any valuable thing it considers underused. It is a measurable condition for priority in the next equivalent season. The unit, observation period, threshold and consequence are defined in advance. Failure normally returns the affected series to a pool for reallocation; it does not transfer the airline's aircraft, route contracts or other slots to the coordinator.

The threshold also contains deliberate tolerance. Airlines do not need perfect operation. Weather, maintenance, air-traffic restrictions and ordinary disruption make 100 percent unrealistic. The 20 percent margin allows resilience while discouraging an airline from reserving scarce times that it has no serious plan to operate. Coordinators give usage feedback so airlines can see which series may fail the threshold before the season closes.

The design has two lessons for number governance. The first is that any utilisation consequence must be attached to an administrable proposition. "Not valuable enough" is not a test. "Not announced globally" is not a reliable substitute for non-use because addresses may support private networks, reserve capacity, migration, security services, intermittent infrastructure or authorised downstream use. Route collectors also see only selected observation points. An unannounced prefix is not equivalent to an empty runway time.

The second lesson is that the consequence should match the right conditioned. Airport non-use affects priority for a future seasonal allocation. It does not retroactively declare that every past operation was unauthorized. If an address institution conditions a newly issued block on a documented deployment plan, failure might affect eligibility for another subsidised allocation. It does not follow that an old, legitimately held block may be confiscated merely because an administrator dislikes its present traffic pattern.

Scarcity can justify rules. It cannot replace them. A lawful use discipline must state who is subject, what evidence counts, what exceptions apply, when measurement occurs, how much tolerance exists, what prospective consequence follows and who reviews error. Without those features, use-it-or-lose-it becomes a slogan for discretionary redistribution.

Justified non-use prevents a mechanical rule from becoming irrational

Airport rules recognise that operation can fail for reasons outside an airline's control. Airport or airspace closure, severe weather, grounding of an aircraft type, industrial action and other exceptional conditions may support justified non-utilisation. The IATA explanation of justified non-use describes why qualifying cancellations can still count when historic eligibility is calculated. Temporary relief during the pandemic made the principle unusually visible: forcing empty flights solely to preserve future rights would have wasted resources and contradicted public-health restrictions.

Exceptions do more than show compassion. They protect the accuracy of the incentive. A use rule should distinguish strategic withholding from inability to operate. If it does not, holders will perform wasteful acts to manufacture evidence. Airlines may fly low-demand services to protect a slot. Address holders might generate artificial announcements, token traffic or nominal assignments that satisfy a crude metric without serving a real network need.

Evidence should therefore be directed at the proposition in dispute. An airline can document a closure, restriction or grounding. A number holder can document a migration, reserve function, disaster-recovery design, customer assignment, merger integration, security transition or lawful private deployment. The registration institution need not approve the commercial wisdom of those choices. It may verify that the asserted status is real when a published rule makes that fact relevant.

Exceptions also need boundaries. A holder should not convert an ordinary commercial decision into permanent immunity. Airport guidance expects unused slots to be returned promptly when an airline knows it will not operate them. Similarly, a holder seeking a benefit reserved for active deployment should not rely indefinitely on an untested statement of future intent.

The defensible balance is evidence, time and proportionality. A stated exception protects continuity for a defined period. A reasoned decision identifies what was accepted. Review is available. The rule does not invite staff to redesign the operator's network. This is how a measurable condition remains legitimate without becoming an instrument of administrative preference.

The coordinator has authority over the schedule, not the airline's purpose

The independent coordinator receives capacity parameters and airline requests, resolves conflicts, allocates times, monitors conformity and records historical status. Neutrality matters because the same scarce time may be wanted by an incumbent hub carrier, a new entrant, a cargo operator and a regional service. If the airport operator or dominant airline controlled allocation, it could use schedule power to protect its adjacent commercial interests.

Independence does not mean unlimited discretion. The coordinator applies legislation, the worldwide guidelines and compatible local rules. If a requested slot cannot be accommodated under the European framework, the coordinator provides reasons and indicates the nearest alternative. Repeated and intentional slot misuse can trigger withdrawal or national sanctions. Coordination committees allow airlines, airports, air-traffic authorities and other users to advise on capacity and local matters without taking over individual allocation decisions.

The narrow office makes review possible. A challenger can ask whether the declared capacity was applied consistently, whether historic status was calculated correctly, whether an exchange matched and whether a misuse finding relied on actual operations. Those are bounded questions. It would be much harder to review a decision that one airline's route was insufficiently important to society.

Number registration requires the same separation. The registrar may verify that the requesting organisation exists, that the representative has authority, that the range is exact, that no conflicting current record survives and that transfer conditions were met. It may preserve public contacts and security-related service status. It should not decide whether hosting, enterprise infrastructure, leasing, migration, cloud service, access provision or reserve capacity is the commercially superior use.

The boundary is not a defence of illegality. Airlines remain subject to safety, competition, consumer, sanctions and environmental law administered by competent bodies. Networks remain subject to applicable law, contracts and technical-security duties. The point is attribution. A slot coordinator should not become an aviation ministry by inference. A number registrar should not become a global licensing authority because it controls a valuable record.

Exact temporal units make scarce rights legible

Airport capacity is not one undifferentiated asset. A departure at an attractive morning time is not interchangeable with a late-night arrival. Runway direction, terminal flow, stands, curfews, passenger connections and paired capacity at the destination all matter. The slot system therefore uses exact dates, times and series. Historic precedence attaches to the defined sequence that was operated, not to a vague quantity of airport access.

IPv4 holdings require equivalent exactness in numerical rather than temporal space. A prefix and its length identify a range. A larger range may be divided into more-specific prefixes. A transfer can concern one component while the holder retains the rest. Registration history should connect parent, extracted and residual ranges so that no address is duplicated or lost between records.

This exactness is essential when intervention is proposed. A competition concern at one airport and one route does not justify removing an airline's slots everywhere. A dispute over one IPv4 sub-range does not justify freezing every holding of a corporate group. The institution should identify the smallest unit affected by the evidence and leave unrelated units undisturbed.

Exact units also make partial solutions possible. Airlines can exchange particular times or release a defined pair. Address holders can transfer one clean prefix while a separate range remains disputed. A record can show that one component is pending and another final. Precision reduces the temptation to resolve hard cases through broad institutional power.

The deeper lesson is that scarcity governance improves when rights are granular enough to audit. Broad categories such as "airport access" and "Internet resources" hide the entity of decision. A holder cannot know what it may rely on, a competitor cannot identify the alleged foreclosure and a reviewer cannot measure proportionality. Time-series identity in aviation and prefix identity in number registration are the foundations on which legitimate continuity and change can coexist.

Secondary trading recognises value without making value absolute

Where desirable slots are scarce, parties will search for ways to move them. The European regulation expressly permits one-for-one exchanges and specified transfers, including some changes within a group or following takeover, subject to coordinator confirmation. The United Kingdom has also developed a secondary market in which unequal exchanges, leases and compensation can move practical control of slots. Its official reform consultation describes both substantial transaction values and the limits of transparency and access in that market.

The existence of payment matters. It shows that historic continuity can support economic value even though the original allocation was administrative and the airport infrastructure is not owned by the airline. Airlines invest around a predictable position, and counterparties will pay to obtain it. Accounting, financing and insolvency practice may treat the expected access as economically significant.

Payment does not remove every condition. The coordinator still confirms the scheduling change. Capacity parameters still apply. Use obligations continue. Competition law can constrain a transaction. The market transfers a qualified position within a coordinated system; it does not buy the power to create another runway movement or ignore curfew.

IPv4 transfers reveal the same distinction. An address range can have a market price because it is scarce, globally useful and costly to replace. A recipient can pay for the seller's ability to complete a recognised transfer. The registration service then verifies source authority, recipient identity, exact range and compatibility with applicable policy. Recognition of the transaction should not be confused with the registry selling the addresses itself.

This middle category is often resisted because institutions prefer simple labels: either public allocation that cannot be sold or private property that the coordinator cannot condition. Airport practice shows why both are incomplete. A valuable, transferable reliance interest can exist within an administrative coordination regime. Governance should make the conditions clear rather than deny the value or convert every condition into ownership by the administrator.

A market cannot correct every inherited concentration

Secondary trading can move slots to an airline willing to pay more, but it does not guarantee open entry. Incumbents may value a slot partly because it protects a hub network or blocks a rival. A new carrier may need several coordinated daily pairs before a route is viable. Sellers may prefer leases that preserve long-term control. Prices and counterparties may remain private. A thin market can entrench rather than dissolve historic concentration.

The United Kingdom's 2023 consultation reported that approximately 92 percent of slots across its coordinated airports were allocated on historic rights, rising above 99 percent at Heathrow and around 98 percent at Gatwick for the period examined. It also noted the stability and investment benefits of historic rights. The policy problem is therefore not proved by the word concentration alone. It is whether the combination of inherited position, market structure and behaviour creates a measurable barrier to useful competition.

IPv4 markets face parallel frictions. Holdings are fragmented across legal histories. Buyers need diligence on authority and chain. Some ranges carry route reputation or security complications. Registry rules differ. Transaction costs favour experienced intermediaries and larger buyers. A holder may lease addresses rather than transfer them because future scarcity is valuable. None of this proves that confiscation would allocate better.

A market should be improved where its defects are observable. Publish completed transfer facts that do not expose protected terms. Standardise authority evidence. Make fees predictable. Permit portability between qualified registration services. Prevent administrators from favouring related brokers or buyers. Allow clean sub-ranges to move without immobilising an entire portfolio. Provide rapid review when a transfer is refused.

Competition policy can then address actual foreclosure, collusion, discriminatory access or exclusionary conduct through the body authorised to do so. The alternative - administrative redistribution whenever concentration appears high - destroys reliance while offering no reliable method for identifying the next best user. Scarcity makes market design necessary. It does not make institutional intuition an efficient allocator.

New-entrant pools protect access at the margin

The European slot framework places newly created, returned and otherwise available slots into a pool. A portion receives priority for qualifying new entrants, subject to the detailed rules. The device reserves some opening for carriers that do not already possess a large schedule at the airport. It does not cancel all historic series each season.

The marginal character is both strength and weakness. It preserves network continuity for incumbents while directing genuinely available capacity toward access. Yet at a fully saturated airport, very few attractive times may enter the pool. The UK consultation's Heathrow example showed how a high percentage for new entrants within the pool could coexist with only a tiny number of pool slots compared with the total seasonal schedule.

This is an important caution for IPv4 policy. A reserved pool can help new networks if recovered, returned or specially set-aside addresses are genuinely available. It cannot manufacture clean IPv4 space. A wait list can distribute occasional returns, but it should not be used to imply that confiscating established holdings is the only way to support entry.

Other tools can reduce entry barriers without breaking existing recognition: allow small transfers, lower administrative fees for modest recipients, publish compatible transfer paths, support financing and escrow clarity, preserve global portability, and avoid needs tests that only large compliance teams can satisfy. IPv6 deployment can reduce some dependence on additional IPv4 while not pretending that current compatibility needs have vanished.

The airport comparison favours an incremental rule. Put new capacity and voluntarily returned capacity into a transparent pool. Define eligibility in advance. Audit allocation. Do not call a pool pro-competitive if it is inaccessible in practice. Most importantly, do not convert a policy for available capacity into a presumption that every historic holding is available. Entry safeguards and incumbent continuity are design variables, not mutually exclusive moral positions.

Targeted slot releases show how competition remedies should be scoped

General allocation rules are not the only source of access. Competition authorities may require airlines to make slots available when a transaction or continuing commercial arrangement threatens rivalry on particular routes. The United Kingdom Competition and Markets Authority's Atlantic Joint Business Agreement case provides a current example. Binding commitments accepted in 2025 require slots to be made available for competitors on specified London routes, with a monitoring trustee and defined application process.

The remedy is informative because it is not a declaration that historic rights are illegitimate. It connects a competition concern to routes, frequencies, eligible applicants, duration, monitoring and associated access terms. Competing airlines receive a usable opportunity. The authority does not seize every slot held by the parties or allow the coordinator to redesign their worldwide networks.

An IPv4 competition remedy should meet the same discipline. If a holder used address control to foreclose a downstream market, the competent authority would need evidence of market power, conduct, effect and jurisdiction. A remedy could require nondiscriminatory dealing, divestiture of a defined range, release of contractual restrictions or access on stated terms. The registrar would record the resulting change; it would not invent the competition case.

Targeting protects legitimacy in both directions. Incumbents cannot hide proven exclusion behind historic allocation. Administrators cannot cite general scarcity as proof of abuse. The remedy reaches the identified harm and leaves unrelated holdings intact.

This also explains why registration data matters to competition without turning the registrar into the competition authority. Accurate holder identity, transfer dates, parent-child ranges and service relationships help investigators understand control. The record supplies evidence. The authorised body decides whether conduct breaches law. The registrar implements a final, applicable act. Separation produces stronger enforcement because each institution can be judged against its competence.

Misuse sanctions require conduct, notice and proportionality

Airport rules distinguish low utilisation from repeated intentional misuse. An airline that repeatedly operates at a significantly different time or in a significantly different way can disrupt capacity assumptions and disadvantage compliant users. The coordinator can act under the regulation, while Member States provide effective and proportionate sanctions. Airport Coordination Limited publishes a slot-sanctions framework for the United Kingdom that explains the statutory and code-based basis for enforcement.

The terms repeated, intentional and significant matter. A single weather diversion is not strategic misuse. A small timing variance is not automatically equivalent to operating without coordination. Evidence from actual movements can be compared with the allocated series. The carrier receives a defined allegation rather than an unbounded claim that its service lacks merit.

Number systems need an equally precise hierarchy. A stale contact invites notice and correction. An unauthorised transfer instruction requires a security hold. Deliberate false identity evidence may justify rejection, account restriction and referral. A route hijack is operational evidence requiring urgent coordination, but route observation alone does not prove that the registered holder authorised it. A contractual payment dispute does not automatically invalidate the registration.

Sanctions should be attached to the actor and conduct proved. Suspending every resource of an organisation because one contact record is wrong may be disproportionate. Removing a prefix because an unrelated customer violated a service term may punish the wrong party. Secret criteria make correction impossible and invite selective enforcement.

The air-traffic lesson is not leniency. It is administrability. High-reliance systems need graduated responses, contemporaneous evidence, notice, reasoned decisions and review. A coordinator can protect scarce capacity more credibly when users know the line between disruption, ordinary variance and fraud. A number registrar protects uniqueness more credibly when it identifies the registration harm rather than treating all unwanted activity as authority to redistribute.

The airport analogy has a limit: address use is not a runway movement

An aircraft movement is visible and consumes time-specific airport capacity. If the movement does not occur, another flight could in principle have used that slot. IPv4 use is not so simple. A registered prefix can serve many customers, remain reserved for failover, support private addressing arrangements, be announced only to selected networks, sit behind security mitigation or prepare a staged migration. One holder's registration does not prevent another network from using other available addresses at the same moment in the way one scheduled movement excludes another at the same runway time.

IPv4 scarcity exists because the number space is finite and uniqueness requires one coherent allocation state. But registration, routing and traffic are different facts. A route may be originated by a contractor. A hijacker may produce visible traffic. A legitimate holder may not announce globally. More-specific routes may divide operational control. RPKI can authorise an origin without proving corporate power to sell.

For that reason, copying the 80 percent threshold would be irrational. What is the denominator: addresses responding to probes, addresses seen in flow data, announced prefixes, assigned customers or contractual reservations? Each measure sees a different use and creates privacy, security and gaming risks. A registrar would need intrusive access to judge commercial deployment and would still miss legitimate functions.

The transferable principle is narrower. When a benefit is explicitly conditioned on a stated fact, use relevant evidence and a defined period. A recipient seeking a needs-based transfer may document a deployment plan if the applicable published rule requires it. A holder claiming a security exception may document the protected function. But basic recognition of an established, lawful holding should not depend on continuous public traffic.

Good analogies transfer institutional logic while respecting the subject matter. Airport use can be counted as movements. Address use is distributed across technical and contractual layers. A system that ignores that difference will reward artificial signals and punish operational prudence.

Historic IPv4 holdings need chain recognition, not retrospective conformity

Legacy address space may have been distributed before today's regional structures, contracts and criteria existed. Organisations have since merged, renamed, dissolved, reorganised or transferred network businesses. Records can be incomplete. The question for a current registrar is whether it can identify the legitimate holder and maintain a unique, accurate state, not whether the original recipient could satisfy a policy written decades later.

The RIPE NCC framework for legacy holders illustrates a recognition approach. It maintains and publishes registry data, offers formal service relationships, performs due diligence on the claimant and can examine company registration, name-change and transfer documents. The policy states that rights to hold, use or transfer legacy resources are not created or restricted by that service framework. Registration service and underlying claims are deliberately distinguished.

Airport historics follow a comparable temporal discipline. The coordinator starts from the series actually recognised and operated under the rules then applicable. It does not demand that an airline prove it would win a modern new-entrant allocation every year. Prospective use and misuse rules protect capacity. History protects reliance.

For IPv4, the chain should record original distribution where known, corporate succession, transfer, split, correction and current service relationship. A missing old document should be described as a gap rather than cured by a stronger assertion than the evidence supports. Later verified continuity may still establish who can instruct the present record. Disputes beyond the registrar's competence can be noted and referred to agreement, arbitration or court.

Retrospective conformity is especially dangerous because the administrator chooses the modern test. It can convert institutional evolution into a power to cancel older rights. A fair order updates the record to reflect reality, applies clear requirements to future services and preserves challenge where evidence conflicts. Historic recognition is not immunity; it is refusal to rewrite time.

Transfer rules should test authority and uniqueness, not business taste

Every transfer creates a risk of duplicate recognition, fraud or broken chain. Registration services therefore have legitimate work. They should confirm the source entity, the receiving entity, the exact prefix, authorised representatives, consent, applicable restraints and effective state change. Inter-regional transfers also require the two services to reconcile release and receipt.

APNIC's current transfer policy requires the source to be the registered holder and free of a dispute over the resource's status. It records inter-regional transfers only where the counterpart service has a compatible transfer policy. ARIN's Number Resource Policy Manual similarly addresses source recognition, recipient agreements, operational use and transfer conditions. These are not identical regimes, which is itself a reason for transparent interoperability.

The transfer review should not expand without limit. A registrar may need a recipient plan where an applicable needs rule makes it relevant. It does not need to choose the recipient's product, customer class, data-centre location, financing structure or route policy. Those matters can be governed by law, contract, lenders, customers and network operators.

Secondary slot exchange offers a useful model. The coordinator confirms that the proposed change can be recorded consistently with capacity and rules. It does not renegotiate the airlines' compensation or determine whether one carrier has a better brand. Competition review remains available where a transaction creates a separate concern.

A strong number transfer service therefore says exactly what approval means. It confirms the change in recognised registration under stated conditions. It does not certify universal legal title, clean reputation, worldwide route acceptance or commercial success. Bounded confirmation is more valuable than a grand declaration because parties can identify residual risks and assign them through contract, insurance or specialist review.

Portability prevents historic administration from becoming permanent captivity

Airport slots are tied to a particular airport because the underlying capacity is physical. An airline cannot move a Heathrow time to another airport and call it the same slot. IPv4 ranges have no comparable physical attachment to the office that first registered them. They can be used globally, and the holder may have operations across several regions.

That difference strengthens the case for registration portability. A historic holder should be able to move service to a qualified recorder if uniqueness, chain history, dispute state and adjacent technical services remain coherent. The old service marks the move final; the new service becomes current; both preserve a shared event reference. No duplicate range is created.

Portability changes incentives. A registrar that delays routine changes, charges unpredictably or asserts authority over commercial use can lose the service relationship without destroying the holder's recognised position. A receiving service must meet common evidence, continuity, audit and security standards. Competition occurs in administration rather than through competing claims to the same numbers.

The airport analogy still contributes one caution. Secondary arrangements can become opaque if the formal record and practical user diverge. A portable number system must show which service is current and who can instruct it. Leasing or delegated operation should not be confused with a completed transfer. Protected commercial terms can remain private while the public status stays intelligible.

Portability is not permission to evade a court order or erase an open dispute. Applicable restraints travel with the evidence needed to interpret them. Nor should a former registrar retain a veto after every published condition is satisfied. A narrow integrity hold can pause a move; it needs a reason, evidence, expiry and review.

Historic allocation should create continuity, not captivity. Airport systems cannot supply portability of place, but their coordinated exchanges show that continuity can survive a change in user. Number systems can go further because the resource is numerical rather than fixed to concrete.

Competition safeguards should govern institutions as well as holders

Scarcity invites scrutiny of concentrated users, but administrative concentration can be just as consequential. A single registrar may control updates, transfers, security certificates, reverse-DNS delegation, public contacts and dispute status. If no exit is possible, procedural delay can destroy transaction value even without a formal refusal.

Airport design responds by requiring an independent coordinator and by separating airport management, airline operations, air-traffic control and competition oversight. The separation is imperfect, but it identifies conflicts. The airport cannot simply allocate its best times to an affiliated airline. The coordinator's decisions remain bounded by capacity and published criteria. Competition authorities can impose targeted remedies.

Number governance should apply equivalent safeguards to the recorder. It should disclose decision times, refusal categories, conflicts of interest, related commercial services and transfer fees. Staff deciding disputes should not benefit from brokerage or acquisition outcomes. Independent review should be available. Data exports and continuity arrangements should allow a successor to preserve the last valid state if the institution fails.

Policy participation is not a substitute for these controls. A holder may speak in a community meeting and still face an unreviewable individual decision. Voting weight or membership fees may favour established actors. The question is not whether discussion occurred but whether the institution's power over a specific record is accountable.

Competition safeguards also require interoperability. If transfers between registrars are blocked by incompatible policy despite no uniqueness risk, the administrative boundary itself can foreclose exchange. Common event identifiers, authenticated release and receipt, exact prefix matching and reconciliation can reduce that barrier without centralising every service.

A scarcity institution earns trust by constraining itself. Demanding utilisation evidence from users while publishing no evidence about administrative performance is an asymmetry, not accountability.

Confiscation fails both reliance and information tests

Forced redistribution is sometimes presented as efficient because an administrator can identify dormant holdings and give them to active users. The claim assumes facts the administrator rarely possesses. It must know current and planned use, contractual commitments, security functions, migration costs, the value of reserve capacity and the comparative productivity of possible recipients. Public routing data cannot supply that knowledge.

Confiscation also changes behaviour before it occurs. Holders will create visible activity, fragment arrangements, conceal reserve capacity or avoid updating records if accuracy exposes them to loss. Investors will discount network commitments that depend on discretionary recognition. Sellers will rush transactions before rules change. Administrators will face lobbying over recipient selection. The apparent gain from recovered addresses must be measured against these distortions.

Airport use-it-or-lose-it avoids some of these failures because the protected expectation was always seasonal and expressly conditioned on countable operations. Even there, policy supplies exceptions and advance returns to avoid waste. Historic IPv4 holdings often lack an equivalent original condition, and address use cannot be counted with comparable confidence.

None of this makes recovery impossible. A holder can voluntarily return space. A dissolved organisation with no legal successor may leave a genuine orphan after careful notice and chain research. Fraudulently obtained registration can be corrected. A court or authorised authority may direct disposition. Contractual termination can have stated effects. The institution must prove the category rather than treating silence or low visibility as abandonment.

The difference is between correction and taking. Correction restores the record to an evidenced state or implements a competent decision. Taking selects a preferred new user because the incumbent's purpose is disfavoured. Scarcity may heighten the value of correction; it does not erase the need for authority, evidence and remedy.

A fair historic-allocation model needs eight elements

First, exact identity. The record names each prefix and links parent, child and residual ranges after a split. No decision operates on a vague portfolio.

Second, recognised continuity. Original allocation, succession, transfer and correction form a durable chain. Historic status states what is known and what remains uncertain without requiring old recipients to satisfy new allocation criteria retroactively.

Third, authenticated authority. Corporate identity, representative authority, account access and operational contact are separate facts. A valid credential can submit a request but does not by itself prove power to dispose of the range.

Fourth, bounded conditions. Any use, service or transfer condition defines the affected benefit, evidence, period, tolerance, exception and consequence. Basic registration is not made dependent on a secret judgment about commercial merit.

Fifth, exchange. Clean transfers can complete through matched instructions, predictable fees and interoperable release and receipt. Commercial consideration remains with the parties. The record states only what the registrar verified.

Sixth, competition safeguards. New or returned capacity can support entry. Proven exclusion can receive a targeted remedy from a competent body. Registrar conflicts, delay and lock-in receive equal scrutiny.

Seventh, correction and review. Affected parties receive notice, reasons, access to the decisive evidence to the extent law permits, a time limit and independent review. Final correction adds history instead of silently replacing it.

Eighth, continuity of service. Registration can move to a qualified provider, and institutional failure does not erase the last valid state. Routing and other adjacent operations remain separate while handover is coordinated.

These elements do not settle whether every jurisdiction characterises an address interest as property, licence, contract or another category. They answer the practical governance question: how can a valuable historic position remain reliable and transferable without converting the recorder into owner or the holder into sovereign?

Hard cases reveal whether the safeguards are real

Consider an airline that narrowly misses the utilisation threshold after an airspace closure. A legitimate system can identify the affected series, verify the closure, apply the stated exception and preserve historic priority. A number equivalent might involve a holder that temporarily withdraws routes during a security incident. The registrar should not infer abandonment from the withdrawal.

Consider a secondary slot trade in which payment is agreed but the coordinator finds that the proposed times cannot be recorded as represented. The parties retain contractual remedies, while the coordinator gives a reason confined to the scheduling rule. In an IPv4 transfer, a mismatch in the prefix or source authority should pause that range, not invite the registrar to renegotiate price or select another buyer.

Consider a dominant airline arrangement that harms competition on three routes. A targeted release with a monitoring trustee can open those routes while other historics continue. If an address holder commits proven exclusion in a defined market, the remedy should be equally tied to the conduct and range necessary to restore competition.

Consider a registrar that becomes insolvent during a transfer. Historic evidence, matched instructions and a portable current-state record should let a successor determine whether the event completed. The resource cannot remain hostage to the corporate survival of the recorder.

Finally, consider a genuinely abandoned range. Notice should reach registered contacts, corporate successors and other evidenced claimants. Routing activity is relevant but not conclusive. After a published period and review, the record may identify the range as unclaimed and follow an authorised recovery rule. The reasons and evidence remain visible. This is not discretionary confiscation; it is a bounded response to proved absence of a holder.

Hard cases prevent easy rhetoric. A system committed only to incumbency will fail on fraud and exclusion. A system committed only to redistribution will fail on reliance and error. The test is whether it can preserve the last valid state while a specific exception is proved.

Conclusion: continuity needs conditions, and conditions need limits

Airport slots demonstrate that inherited scarcity positions need not be absolute property or revocable administrative favour. Historic precedence protects investment and reliable schedules. Use-it-or-lose-it connects renewal to operations, while justified non-use prevents waste. Secondary exchange moves access; entry pools and targeted releases create openings without cancelling every incumbent series. Independent coordination keeps the recordkeeper out of the cockpit.

The comparison does not make IPv4 a runway timetable. Address use can be private or delegated and is not consumed through one countable operation. An 80 percent traffic rule would be arbitrary. The useful lesson is qualified continuity: exact units, prospective rules, relevant evidence, defined exceptions, coordinated transfer, targeted remedies and review.

Historic IPv4 holdings should be recognised when the chain and authority are supportable. Their value does not disappear because the first distribution was administrative. Transfers can be recorded without treating the registry as seller. Routing and lawful commercial purpose remain with operators. Proven fraud, abandonment or exclusion can justify precise intervention.

Confiscation is not stewardship. It encourages artificial use and gives administrators a task for which they lack market knowledge and universal authority. Permanent immunity is no answer either: holdings remain subject to fraud correction, court orders, contracts and competition law.

The position lies between those poles. Continuity earns confidence through known, limited conditions. Exchange earns trust when the coordinator verifies identity and uniqueness rather than choosing the winner. Competition safeguards should address demonstrated harm, not scarcity in the abstract. A scarce resource can move without seizure, remain stable without becoming untouchable and be coordinated without being operated by the coordinator.

Sources