Conservation is one of the most durable words in Internet number governance because it sounds modest. It implies prudence, technical care and a refusal to waste a finite common resource. In the early IPv4 allocation era, that language had an obvious administrative role. A registry with a shrinking pool had to prevent duplicate claims, avoid casual over-allocation and ask networks to justify requests. The problem was finite supply before a mature market existed. Conservation, in that setting, meant rationing a resource that the registry still controlled.
The problem after exhaustion is different. RIPE NCC exhausted its remaining IPv4 pool in November 2019. Its current waiting-list path can give eligible Local Internet Registries only a single /24 from future recovered space. Most meaningful IPv4 capacity now moves through transfers, leasing, corporate acquisitions, legacy-resource updates, address-sharing strategies and operational workarounds. Conservation language did not disappear when the free pool disappeared. It migrated. It now appears in debates about transfer restrictions, waiting-list rules, audits, registry fees, policy development, legacy status, routing security and the proper scope of a membership association. The word still sounds technical. Its consequences are economic.
RIPE NCC is the clean case because it is mature, well documented and not a crisis registry. It is a not-for-profit membership association based in the Netherlands and the Regional Internet Registry for Europe, the Middle East and parts of Central Asia. It runs a public registry, supports the RIPE Database, processes transfers, operates RPKI services, supports reverse DNS, convenes policy discussion and collects fees from a large membership. Its IPv4 run-out page records the exhaustion facts. Its transfer policy allows legitimate holders to transfer resources but imposes restrictions on scarce resources. Its charging scheme sets a EUR 1,800 annual contribution per LIR account for 2026, plus charges for independent assignments and ASNs. Its policy pages describe an open, bottom-up process. These are useful exhibits, not the analytical frame.
The stronger question is this: once IPv4 scarcity has already become an economic fact, what does conservation language conserve? Does it conserve uniqueness, record integrity and operational reliability? Or does it conserve institutional discretion, incumbent advantage, low-visibility distributional choices and the old moral authority of allocation-era administration? RIPE NCC's region provides the evidence because its membership model, policy-list culture, transfer rules, legacy handling, accountability disputes and reliability expectations all sit on that boundary.
Before conservation became a slogan
The original conservation case was not absurd. IPv4 had a finite address space. Allocation decisions could not ignore depletion. If networks received much more than they could plausibly use, others would face shortage sooner. If the registry record became inaccurate, routing and coordination would suffer. If contacts were stale, abuse response and operational troubleshooting would weaken. Conservation, in this early sense, was a technical-administrative discipline.
The policy vocabulary reflected that world: need, justification, fair access, aggregation, stewardship, responsibility. A Local Internet Registry asked for resources, supplied plans and documented use. The registry, operating under community-developed rules, evaluated whether the request fit the allocation framework. The free pool was the centre of gravity. Scarcity was anticipated, but the main economic problem was how to allocate from remaining central stock without obviously wasting it.
That world is gone. It did not disappear because critics declared it obsolete. It disappeared because the free pool ran out. RIPE NCC's public history describes the transition. For much of its history, LIRs could receive as many IPv4 addresses as they needed if they supplied documentation such as network plans. When the registry reached its final /8 in 2012, each LIR could request one /22, or 1,024 addresses. In November 2019, available IPv4 space was exhausted, triggering the present waiting-list regime for recovered addresses. This is not an ideological claim. It is the operating fact around which the region's address economy now turns.
The conservation question changed at that moment. Before exhaustion, conservation asked how the registry should distribute what remained. After exhaustion, conservation asks how the registry should treat resources already distributed, already embedded in networks and already priced by market demand. The difference is not semantic. A new allocation from a free pool and a transfer of existing address space are economically different events. The first is administrative rationing. The second is recognition of a capital movement between parties.
When conservation language is carried from the first event into the second without adjustment, it becomes a mask. It makes a rule about liquidity sound like a rule about waste. It makes a rule about who can benefit from scarcity sound like a rule about public responsibility. It makes a rule about institutional review sound like a rule about fairness. The old language remains comforting because it avoids the harder question: who now bears the cost of scarcity, and who is allowed to capture its value?
That question is uncomfortable because it exposes distribution. IPv4 scarcity benefits holders of clean, usable address space. It hurts late entrants, fast-growing operators and networks without historical stock. It creates opportunities for leasing, purchase, brokerage and corporate transactions. It increases the value of registry-recognised records. It makes the policy history of a region part of its capital structure. Conservation rhetoric can acknowledge this and ask how to preserve reliable records. Or it can deny the economic shift and keep treating every market signal as a moral threat.
The pool is no longer the economy
The waiting list is the clearest evidence that conservation now has limited allocative power. A /24 is useful. It can support a small service, multihoming, a minimum public footprint or a late entrant's first step into routable IPv4. But a /24 cannot satisfy the address requirements of a hosting platform, national broadband deployment, cloud region, data-centre expansion, large enterprise migration, security-service network or acquisition-driven growth plan. The waiting list is a residual fairness mechanism, not a solution to industrial demand.
That does not make the waiting list useless. It gives some operators a small opportunity that would otherwise not exist. It also preserves a visible link between RIPE NCC and allocation fairness after exhaustion. But the list should not be mistaken for the main economy. Most address capacity now moves through other channels. Operators buy blocks. Holders lease underused space. Companies acquire firms partly because of their address holdings. Legacy resources are updated. Some networks deploy CGNAT. Others use IPv6 where feasible while still needing IPv4 for customers, compatibility and reputation. The official allocation path is no longer the central supply mechanism.
This is where conservation language can mislead. If the remaining policy imagination is built around fair distribution of recovered fragments, it may obscure the larger distributional question: how does the registry's recognition layer affect the existing stock? A small recovered allocation may be fair in narrow terms while the transfer market remains expensive, opaque or slow. A waiting-list rule may deter abuse while doing little for operators that need more than a /24. A conservation narrative may celebrate the prevention of speculative requests while ignoring the fact that incumbent holders now possess most usable supply.
The post-exhaustion registry should therefore be judged less by how it rationed the last fragments and more by how it administers the recognised record for existing resources. Is transfer predictable? Are legacy updates clear? Are sanctions checks narrow and measurable? Does RPKI attach reliably to recognised holdership? Are audits data-quality tools or fear triggers? Are fees tied to the cost of a necessary ledger or to a broader institutional ecosystem? Does the policy process analyse economic effects rather than merely repeat allocation-era language?
RIPE NCC's own materials show that the registry understands part of this shift. Its run-out page acknowledges the transfer market and CGNAT as responses to scarcity. Its transfer policy allows permanent and non-permanent transfers and requires database updates. Its transfer statistics provide visibility into approved movements. Its inter-RIR pages describe compatibility with other regions. These are market-facing features. They sit uneasily beside any claim that conservation alone can govern the scarcity economy.
The better term after exhaustion is reliability. RIPE NCC cannot conserve a free pool that no longer exists in meaningful quantity. It can conserve the integrity of the record, the predictability of transfers, the continuity of RPKI and reverse DNS, the evidentiary quality of legacy changes, the narrowness of sanctions compliance and the accountability of fees. That form of conservation is real. It is also different from conserving institutional discretion over who may benefit from scarcity.
The moral appeal hides distributional choices
Conservation rhetoric is powerful because it sounds anti-waste rather than anti-market. Few operators want to be accused of hoarding. Few policymakers want to appear indifferent to late entrants. Few registry officials want to say openly that scarcity has created winners and losers. The word conservation lets institutions avoid blunt distributional language. A restriction can be described as protecting the community. A liquidity constraint can be described as preventing speculation. A fee can be described as sustaining shared services. A due-diligence delay can be described as preserving integrity.
Some of these descriptions are true in particular cases. Fraud prevention protects the community. Transfer restrictions can reduce policy gaming. Fees do sustain shared services. Due diligence preserves integrity. The analytical problem is that true statements can still conceal trade-offs. A policy that prevents a narrow abuse may also reduce legitimate liquidity. A fee that funds useful services may also burden small operators who need only core registry functions. A waiting-period rule may deter flipping while lowering the price a seller can obtain. A community argument may represent active list participants better than absent members or downstream users.
This is the distributional core. Conservation after exhaustion is not only about preventing waste. It decides who can turn scarce IPv4 into capital. It decides whether early holders can sell or lease freely, whether late entrants can buy without hidden friction, whether small operators must use brokers, whether large incumbents can absorb delays, whether legacy holders are pulled into direct agreements, and whether registry institutions preserve relevance by keeping market movement permissioned.
Public market-side arguments have pushed this point sharply. They argue that scarcity should be treated as capital, that administrative control can suppress liquidity, and that language about stewardship or community can preserve gatekeeping while hiding the economic value at stake. These arguments are interested, not neutral judgments. Their value is that they ask the question official vocabulary tends to soften: when a resource has already become scarce, who benefits from keeping price, transferability and ownership-like confidence morally suspect?
The answer is not as simple as saying markets good, registries bad. A registry that abandoned due diligence would damage the market. A transfer system with no identity checks would invite theft. A region with no sanctions compliance would create legal risk. A database that accepted every claim would become less useful. Conservation of the ledger remains essential. The point is narrower and more demanding: conservation language should be tied to measurable ledger harms, not used as a general warrant for controlling scarce capital.
For RIPE NCC, the distinction is practical. If a 24-month transfer restriction is justified as preventing immediate flipping, the registry and community should measure how often it does so and what legitimate transactions it delays. If waiting-list eligibility is justified as fair access, the community should acknowledge that a /24 is symbolic for many growth needs. If audits are justified as data-quality work, the institution should distinguish cooperative correction from enforcement escalation. If fees are justified as shared infrastructure, members should see which costs are indispensable to the ledger and which are broader institutional choices.
Conservation should become an audited claim, not an emotional vocabulary.
Transfers show the economics underneath
RIPE NCC's transfer framework is where conservation rhetoric meets market reality. The transfer policy allows legitimate holders to transfer complete or partial blocks of address space or number resources, subject to rules and restrictions. Allocated resources may be transferred only to another RIPE NCC member. Provider Independent resources may be transferred to a member or to an entity with the required contractual relationship through a member. Transfers must be reflected in the RIPE Database. The original holder remains responsible until completion. In temporary transfers, the original holder re-assumes responsibility when the resource is returned.
This framework is more market-facing than a pure rationing model. It recognises that resources move. It also embeds conservation-era constraints. Scarce resources such as IPv4 and 16-bit ASNs cannot be transferred for 24 months from receipt, including receipt through a change in business structure such as a merger or acquisition, while certain further merger or acquisition transfers remain possible. The policy logic is familiar: prevent rapid churn, stop opportunistic conversion of administratively received resources into quick profit, and protect the integrity of scarcity rules.
Yet the economic effect is liquidity control. A holder who receives space cannot treat it as fully mobile for two years. A buyer must price the restriction. A corporate acquirer must consider future divestiture. A seller may prefer a lease. A restructuring may be shaped by registry timing. A block subject to restriction is different from a cleanly transferable block. Conservation vocabulary may make the rule sound like moral hygiene. In market terms it changes the option value of the resource.
The same applies to merger and acquisition review. RIPE NCC's M&A guidance requires recent company registration documents, legal documents supporting the change in business structure and other available support. It says RIPE NCC evaluates requests under applicable policies and procedures and checks against the EU sanctions list; if either party is under sanctions, the transfer request will not be approved. That is reasonable for a Dutch association operating in a legally complex region. It is also a transaction condition. A buyer, seller or lender must price the possibility that registry recognition will not move, or will move more slowly than the business deal requires.
If conservation means preventing fraudulent or unlawful transfers, the gate is legitimate. If conservation means preserving the registry's ability to morally evaluate market movement, the gate becomes suspect. The difference can be seen in what the process measures. A narrow ledger process asks whether the parties are real, authorised and legally eligible; whether the resource is transferable; whether records are accurate; whether services are updated; and whether there is a dispute. A broader conservation process asks, implicitly or explicitly, whether this transfer is aligned with a preferred view of how IPv4 should be used. The first protects the market. The second governs it.
Inter-RIR transfer policy demonstrates the same tension across borders. RIPE NCC can participate in transfers with other RIRs where policy frameworks are compatible, while AFRINIC's lack of an inter-RIR transfer policy means resources cannot be moved to or from that region through that path. The address space itself is globally routable, but registry mobility depends on regional institutional rules. Conservation in one region can become capital immobility for a global market. A resource's value may depend not only on size and reputation but on which registry's conservation logic applies.
The problem is not that RIPE NCC should process every transfer blindly. The problem is that every conservation rule should be read as a market rule. It affects liquidity, price discovery, corporate structure, leasing demand and small-operator access. If the registry wants conservation claims to remain legitimate, it should publish more friction data: processing times, categories of delay, restrictions applied, aggregate sanctions outcomes, failed or abandoned transfer requests, legacy-update uncertainty and inter-RIR waiting patterns. Without such evidence, conservation remains a pious phrase covering unknown costs.
A queue that is both useful and symbolic
The RIPE NCC waiting list performs two functions at once. It is a real tool for distributing recovered IPv4 in small units to eligible late entrants. It is also a theatre of fairness, preserving the idea that the registry still allocates scarce resources according to a public rule rather than leaving everything to price. Both functions matter.
The real tool is limited but not trivial. A /24 can let a new LIR establish a routable IPv4 presence. It can support multihoming, small access networks, enterprise use, experimental services or basic customer needs. For a small operator, it may be meaningful. A registry that simply abandoned recovered space to private deals would lose a visible fairness mechanism. The waiting list also discourages the idea that all scarcity should be resolved immediately by the highest bidder.
The theatre of fairness becomes problematic when it is used to distract from the larger market. The waiting list does not supply serious growth capacity. It does not equalise historical allocations. It does not remove the need to buy or lease. It does not solve the imbalance between large incumbents holding old stock and new entrants facing market prices. It does not answer the question of whether transfer restrictions or fees burden smaller operators. It cannot, by itself, justify broad conservation rhetoric around the entire IPv4 economy.
This dual nature should be acknowledged openly. The waiting list is a small equity device inside a market-dominated scarcity environment. Treating it as such would improve policy clarity. It would allow RIPE NCC to defend it honestly without overstating its role. It would also force the community to evaluate other rules on their own merits: transfer restrictions as liquidity rules, fees as infrastructure charges, audits as data-quality controls, sanctions screening as legal compliance, and policy-list governance as an attention market.
The current danger is symbolic substitution. A visible queue can make scarcity governance look fair even when the real distributional action occurs elsewhere. If the queue is the public face of fairness while the transfer market is the hidden engine of supply, conservation rhetoric may become a form of institutional self-comfort. It lets the registry say there is still a public path while the practical path for growth is purchase, lease or acquisition.
The waiting list should be defended in modest terms. It is a way to allocate recovered fragments under an objective rule. It is not a substitute for transfer-market transparency. It is not evidence that scarcity has been socially solved. It is not a reason to apply allocation-era moral language to every later movement of IPv4 capital.
The small-operator problem
Conservation language often presents itself as protection for small and late-arriving networks. Sometimes it is. A recovered /24 can matter. A rule against gaming may prevent insiders from capturing fragments. A clean public registry helps small operators who cannot hire large legal teams. But conservation can also make small operators worse off when it suppresses liquidity or raises fixed costs.
The small operator's position after exhaustion is different from the position imagined by early conservation policy. In the older model, an operator could request from a shared pool and accept needs-based scrutiny because the pool was the main source of supply. In the post-exhaustion system, the same operator often has no meaningful pool to request from. It must buy, lease, wait for a small recovered block, use CGNAT, rely on IPv6 where customers and services permit, or delay growth. A conservation rule that makes transfers slower or leasing less clear does not give the small operator more addresses. It may simply raise the price of the only available supply.
Liquidity is therefore a small-operator issue. It is often associated with traders, brokers and large address holders. But liquidity is precisely what lets smaller networks obtain usable increments without purchasing a whole business or accepting unfavourable dependency. A thin, uncertain transfer market benefits parties with legal capacity and inventory. A clearer market benefits operators that need to buy or lease modest amounts with confidence. If conservation rhetoric suppresses liquidity in the name of anti-speculation, it can accidentally protect incumbents.
Policy participation compounds the problem. A small operator may not know that a mailing-list debate will affect its future ability to acquire addresses. It may not have staff to read long threads, attend meetings, track revisions or vote at General Meetings. When the rule later becomes a constraint, the formal answer may be that the process was open. That answer is true but incomplete. A public process can still distribute costs toward those least able to participate in it.
Fees carry the same asymmetry. A EUR 1,800 annual LIR contribution may look modest from a registry-wide budget perspective. It may also be one of several fixed costs that small operators face while paying for transit, equipment, power, staff, local licences, security, customer support and address supply. If the fee funds a narrow ledger, the small operator can understand it as the price of reliable recognition. If the fee funds a broad institutional programme, the operator may experience it as a compulsory levy attached to a resource relationship it cannot avoid. Conservation language then becomes a way of asking small networks to fund a system whose benefits they may not fully use.
Small operators also bear a larger continuity risk from registry uncertainty. A large network can lose time on a delayed transfer and still serve most customers. A smaller network may have a customer project, deployment window or financing plan dependent on a specific prefix. A delay in recognition, RPKI setup, reverse-DNS delegation or transfer completion can mean lost revenue. If the operator must pay a broker, lawyer or specialist to navigate what conservation rhetoric describes as community policy, the real cost of the rule is no longer visible in the rule itself.
Small-operator effects should therefore be part of every scarcity policy discussion. When a rule claims to conserve fairness, ask whether it lowers or raises the small operator's actual cost of obtaining usable IPv4. When a transfer restriction claims to conserve resources, ask whether it prevents abuse or simply reduces supply velocity. When a fee claims to conserve institutional services, ask whether the compulsory payer uses those services or mainly needs database reliability, transfer processing, RPKI and reverse DNS. When a policy list claims consensus, ask how many small operators were present.
The answer is not to exempt small operators from all rules. That would create its own distortions and fraud risks. The answer is to make conservation tests concrete. A rule should be able to show why the burden it imposes on smaller networks is necessary to protect the ledger, not merely convenient for institutional order. A registry that can do that earns trust. A registry that cannot will see small operators look for workarounds, intermediaries and private continuity arrangements.
Legacy resources and leasing expose the limits
Legacy resources and IPv4 leasing reveal the limits of conservation rhetoric because both operate outside the neat allocation story. Legacy resources carry history. Leasing separates registered holdership from temporary operational use. Neither fits comfortably into a simple narrative of conserving a pool through demonstrated need.
RIPE NCC's legacy-transfer page says legacy resources can be transferred within the service region, that RIPE NCC can help update the RIPE Database if it is clear who the legitimate holder is, that transferred legacy resources retain LEGACY status, and that updates are handled on a best-effort basis because legacy-resource transfers are not covered by RIPE policies. This is a careful posture in some respects. It preserves historical status and recognises transferability while requiring due diligence. It also reveals uncertainty. Best effort is not the language of a fully standardised settlement process.
Legacy resources show that historical allocation has become market title. A holder may not own the block as land, but historical records, database status, corporate continuity and recognised holdership all affect transaction confidence. Conservation rhetoric cannot resolve this. Saying that the resource belongs to a community does not tell a buyer whether the seller can deliver. Saying that the registry conserves the public interest does not tell a legacy holder which services require a direct agreement. The market needs evidence, status continuity and predictable updates.
Leasing exposes a different gap. When an operator needs IPv4 capacity but does not want or cannot afford purchase, leasing can allocate use without permanent transfer. This can be efficient. It can also obscure responsibility if RPKI, reverse DNS, abuse handling, geolocation, reputation and route authorisation are poorly managed. Conservation rhetoric often treats leasing with suspicion because it looks like commodification of a resource once allocated under need-based ideals. But leasing exists because demand persists and official allocation cannot supply it.
The correct question is not whether leasing violates the emotional memory of conservation. It is whether leasing arrangements make operational responsibility clear. Who controls ROAs? Who maintains reverse DNS? Who responds to abuse? What happens when the lease ends? Can the lessee route reliably? Does the lessor's registry status remain stable? Does the registry record remain accurate enough for third parties? These are ledger questions, not moral questions.
Leasing is also an indicator of registry trust. If it grows because rental is economically efficient, that is one thing. If it grows because direct holding, transfer review or registry exposure are perceived as unpredictable, that is another. The same market form can be healthy adaptation or defensive avoidance. Conservation rhetoric cannot distinguish the two. Process data, service reliability and transaction behaviour can.
Legacy and leasing therefore point to the same conclusion. After exhaustion, the important conservation object is not the old free pool. It is reliable use. Reliable use may be achieved through clean transfer, legacy update, leasing, RPKI, reverse DNS, accurate contacts and documented responsibility. A registry that wants to conserve the Internet should make these paths safer and clearer. A registry that wants to conserve allocation-era authority will treat them as suspect deviations.
Reliability is the new conservation
If RIPE NCC's conservation rhetoric is to remain useful, it should be redirected toward reliability. The registry should conserve uniqueness, the integrity of the record, the continuity of services, the clarity of transfer status, the narrowness of legal compliance and the trust that a registered holder can rely on ordinary processes. This is conservation in a post-exhaustion economy.
RPKI shows why. RIPE NCC's RPKI service lets eligible parties request digital certificates listing Internet number resources they hold and create Route Origin Authorisations for BGP origin validation. The more networks use RPKI data, the more registry recognition becomes machine-readable operational trust. This is a powerful reliability tool. It also means that registry decisions around certification, delegated CAs, closure, transfer and service eligibility can affect routing confidence. Conservation of routing security requires a reliable certification system, not broad moral authority over address use.
Reverse DNS shows the same logic in a quieter way. RIPE NCC's reverse-delegation materials explain that the RIPE Database is used as the management database for producing reverse-DNS zones and that domain objects define delegated nameservers. Reverse DNS affects mail, logs, diagnostics, abuse response and customer operations. A record change, lock or service disruption can have practical effects. Conservation of operational continuity means maintaining clear, reliable reverse-DNS procedures, not merely invoking stewardship.
The RIPE Database itself is the core reliability asset. It should show recognised holder, relevant contacts, route-related objects where appropriate, domain objects, transfer history and status information with enough accuracy that operators and counterparties can act. A stale database is wasteful in the strongest sense. It wastes market time, legal effort and operational confidence. A reliable database conserves capital by reducing the cost of trust.
Audits and Assisted Registry Checks should be understood in this frame. They are valuable when they improve data accuracy, routing consistency, sponsored-resource clarity and reverse-DNS quality. They become problematic when members experience them as open-ended enforcement under conservation rhetoric. The better the registry distinguishes cooperative correction from punitive escalation, the stronger its reliability claim.
The Trust Portal is also part of this shift. Confidentiality, integrity and availability are not only cybersecurity virtues. They are market virtues. A holder of scarce resources needs confidence that credentials are secure, records are stable, legal requests are handled properly, and service availability does not depend on informal institutional habits. The more RIPE NCC can show reliability through evidence, the less it needs broad rhetoric.
Reliability also has a liability dimension. RIPE NCC's Standard Service Agreement limits liability and excludes broad categories of damage, subject to important exceptions. This may be necessary for a not-for-profit registry. But limited liability makes reliability more important, not less. If members cannot expect full compensation for business losses caused by registry disruption, they need preventive discipline: clear procedures, narrow powers, stable services and transparent performance. Conservation rhetoric cannot substitute for that discipline.
In the post-exhaustion era, a registry conserves value by being boring, predictable and narrow. It should be difficult to steal a block, easy to understand why a transfer is delayed, clear when a resource is restricted, predictable when RPKI changes, transparent about fees, and humble about market choices. Boring is not the opposite of stewardship. It is the only credible stewardship left.
Accountability disputes are pricing signals
RIPE NCC's region has produced visible accountability signals: member fee debates, transparency initiatives, governance-document consultations, government and regulator concerns, board-election participation questions, phishing campaigns exploiting registry authority and recurring public criticism of RIR scope. These events are often discussed as governance or public-relations issues. They are also pricing signals.
A fee dispute signals that members are not simply asking how much the association costs. They are asking what part of the association is necessary because the ledger is necessary. A transparency portal signals that members and external stakeholders want evidence, not only assurance. A regulator's interest in address handling signals that public authorities understand registry records as more than technical notes. A phishing message that impersonates RIPE NCC authority signals that members believe registry contact can threaten continuity. A policy-list dispute signals that attention and legitimacy are scarce.
Markets price these signals. A buyer considering a block in the RIPE NCC region prices transfer predictability. A lessee prices registry risk. A holder prices annual fees, audit exposure and service continuity. A small operator prices the cost of participating in policy only when a problem arises. A broker prices documentary uncertainty. A lender prices whether recognised holdership can survive dispute. Each price incorporates a view of whether RIPE NCC is a ledger or a gatekeeper.
The institution can reduce this risk premium through data. It can publish aggregate transfer processing times, categories of delay, sanctions-screening outcomes, audit remediation rates, closure statistics, legacy-update timelines, RPKI revocation categories and reverse-DNS service metrics. It can distinguish between legal requirements and policy preferences. It can explain fee allocation by ledger-critical versus broader activities. It can show how many members actually vote and participate. These disclosures would not eliminate criticism. They would convert rhetoric into evidence.
The lack of such evidence leaves conservation language too much room. If a rule is defended as conserving fairness, show who benefits and who pays. If a fee is defended as conserving infrastructure, show which infrastructure. If a restriction is defended as conserving resources, show what abuse it prevents. If an audit is defended as conserving accuracy, show remediation outcomes. If a sanctions process is defended as legal necessity, show aggregate processing categories. Conservation rhetoric should earn its place through measurement.
This is not a demand for hostile oversight. It is the normal discipline of an institution whose record has become economically important. RIPE NCC is not a state, but its record has public consequences. It is not a market regulator, but its rules affect liquidity. It is not a title office, but its database carries title-like confidence. It is not a routing authority, but its RPKI services influence routing decisions. Accountability disputes arise because these roles overlap.
The mature response is to stop treating conservation as a moral shield. Treat it as a hypothesis. A conservation policy should be able to say what it preserves, what it costs, how the cost is distributed and when the policy should be changed.
Ledger neutrality or gatekeeper discretion
The ledger-versus-gatekeeper distinction is the cleanest way to discipline conservation rhetoric. A ledger preserves accurate records, authenticates changes, maintains service continuity, marks disputes, applies law narrowly and lets market participants decide how to value the resource. A gatekeeper uses registry dependency to approve or disapprove of business models, slow legitimate capital movement, preserve institutional relevance or turn old allocation norms into present market control.
Every registry must gatekeep in limited ways. It must prevent duplicate recognition, reject forged documents, comply with sanctions, stop fraudulent transfers and protect its systems. The problem is not the existence of gates. The problem is whether each gate is tied to a specific ledger harm and whether its scope is narrow enough to be priced.
Conservation language can blur this distinction. Preventing a forged transfer is conservation of the ledger. Discouraging a disliked lease model is gatekeeping. Checking that a merger document is real is conservation of the ledger. Treating all address monetisation as suspicious is gatekeeping. Preserving a waiting-list rule against shell games is conservation of fairness in a narrow residual pool. Using that rule's moral logic to justify broad transfer friction is gatekeeping. Charging members for database reliability, RPKI, reverse DNS and security is conservation of infrastructure. Bundling every useful community activity into an unavoidable invoice without cost separation is institutional expansion.
The test should be concrete. What exact harm would occur without this conservation rule? Would the same harm be prevented by a narrower rule? Who pays the cost? Does the rule affect liquidity? Does it affect small operators differently from large ones? Does it preserve the last verified state during disputes? Does it increase or decrease the need for private workarounds? Can the institution measure the outcome?
This approach does not require RIPE NCC to become a market cheerleader. It requires institutional precision. A registry can be conservative in the best sense: cautious about records, strict about authority, careful about sanctions, serious about routing security and modest about its own role. That kind of conservatism is compatible with a liquid market. What it cannot do is use conservation as a general right to prefer allocation-era moral order over post-exhaustion economic reality.
The ledger is strongest when it is boring. The gate is most dangerous when it is morally confident.
Toward thinner, more honest conservation
A better conservation rhetoric for RIPE NCC would begin by admitting scarcity's economic reality. IPv4 address space is scarce. The remaining pool is not a meaningful supply mechanism for most operators. Historical holders have advantages. Transfer markets and leasing exist because demand remains. Registry recognition affects value. Policy rules change liquidity. Fees distribute costs. Audits and sanctions reviews can create risk. RPKI and reverse DNS make the record operationally important. None of this is solved by repeating that the community stewards resources.
The second step is narrowing the conservation object. RIPE NCC should conserve uniqueness, not allocation-era moral authority. It should conserve record accuracy, not institutional discretion. It should conserve reliable transfer settlement, not suspicion of market movement. It should conserve routing-security trust, not control over business models. It should conserve affordable access to the necessary ledger, not automatic funding for every useful institutional activity. It should conserve open policy discussion, not the fiction that visible list participants represent all economic exposure.
The third step is measurement. Conservation claims should be tied to evidence. If rapid post-allocation transfer is a problem, show its incidence. If transfer restrictions prevent abuse, show the pattern. If waiting-list allocations support small operators, measure operational outcomes. If fees fund indispensable services, classify costs accordingly. If audits improve data, publish remediation categories. If sanctions law blocks transfers, publish aggregate counts and timelines. If legacy updates are best effort, show how often and why they succeed or fail.
The fourth step is humility about official language. The registry's own documents are necessary for understanding rules, but they are not the final authority on economic meaning. Institutions always describe their powers in their preferred vocabulary. The market describes the same powers through price, delay, discount, legal conditions, escrow, leasing and avoidance. A serious analysis must read both.
The final step is distributional honesty. Conservation after exhaustion does not make scarcity disappear. It allocates the burden of scarcity. It may burden sellers through waiting periods, buyers through price, small operators through fees, absent participants through policy-list outcomes, sanctioned regions through compliance friction, legacy holders through service uncertainty, and downstream customers through routing or reverse-DNS consequences. Some burdens may be justified. They should not be hidden.
There is also a governance dividend from being explicit. If RIPE NCC states which burdens are intentional and why, disagreement becomes easier to locate. Members can argue about the actual trade-off rather than about the virtue of conservation in the abstract. A small operator can see whether a policy is meant to protect it or whether it is being asked to pay for a wider system benefit. A buyer can decide whether a restriction is part of ordinary title risk or a temporary liquidity cost. A policy participant can ask for review after observed outcomes rather than reopening a moral debate each time the market complains. Precision lowers the temperature because it converts values into design choices.
Thinner conservation would make RIPE NCC stronger, not weaker. It would preserve the part of the institution that the Internet actually needs: a trusted, narrow, reliable ledger for unique resources and associated operational services. It would reduce the incentive for market actors to treat the registry as a risk layer. It would also make the region's policy culture more honest by forcing conservation claims to confront economics. The institution would still have authority, but that authority would be easier for members, buyers, lessees and affected networks to understand before scarcity turns an administrative rule into an expensive surprise.
Analysis and watchpoints
The practical watchpoints are the places where conservation language turns into market effect.
Transfer restrictions should be judged by evidence, not moral tone. The relevant question is whether the 24-month restriction prevents a real pattern of harmful gaming at a cost proportionate to the legitimate liquidity it removes. If the rule mainly delays ordinary transactions, restructurings or exits, conservation has become a liquidity tax. If the rule is still justified, the justification should appear in data: restriction counts, abuse patterns, exception categories and market effects.
The waiting list should be described with realism. A /24 from recovered space can be valuable to a small actor. It is not an industrial supply mechanism. If RIPE NCC presents the waiting list as a limited inclusion device, the rhetoric remains honest. If the queue becomes a symbol that distracts from transfer-market pressure, conservation language will obscure the real scarcity economy.
Fee classification is another signal. Members should be able to see which charges fund ledger-critical functions such as the RIPE Database, transfer processing, RPKI, reverse DNS, security, data accuracy and continuity, and which fund broader institutional activity. A compulsory fee attached to recognition is easier to defend when the bundle is explicit. It is harder to defend when every activity is wrapped in the same conservation vocabulary.
Policy-list practice matters because conservation rules are often made by those with the time to appear. Proposals affecting transfers, legacy resources, RPKI, audits, fees or sanctions should include economic impact analysis and outreach to likely absent holders. Silence from small operators, lessees, legacy holders or downstream users should not be read as consent merely because the list was open.
Sanctions and legal friction should remain narrow and visible in aggregate. Compliance with Dutch and EU obligations is not optional. But the boundary between legal compulsion and institutional caution should be as clear as possible. If sensitive-region transactions are delayed or refused, the market needs categories and timelines, not a haze of compliance language.
Leasing and temporary use should be treated as operational realities. The question is not whether rental markets offend an older allocation ethic. The question is whether responsibility signals are accurate: ROAs, reverse DNS, abuse contacts, route authorisation, end-of-term cleanup and holder accountability. Treating leasing as a moral failure will push it into opacity. Treating it as harmless will ignore real abuse risk. The useful middle is ledger clarity.
Legacy-resource treatment should make historical resources more legible and transferable without using ambiguity to impose unnecessary institutional control. Conservation of history means preserving title-like confidence while verifying changes carefully. It does not mean erasing old reliance through modern normalisation, nor accepting every stale claim without evidence.
RPKI and reverse-DNS continuity should be governed as high-reliability infrastructure, not as secondary administrative privileges. If conservation now means reliability, these services sit near the centre. A database lock, certificate revocation or reverse-delegation disruption can affect market value and customers. The institution should treat such actions as operationally significant.
Audits and registry checks should remain cooperative, measurable and bounded. Data accuracy is a valid conservation goal. Fear is not. The difference lies in cure periods, evidence templates, escalation paths, remediation statistics and separation between correction and punishment.
The issue to watch is not whether RIPE NCC uses the word conservation. It is whether conservation is used precisely. When it means preservation of the ledger, the word still has value. When it means protection of institutional discretion after scarcity has moved into markets, it obscures the real distributional choice. The post-exhaustion economy does not need less care. It needs more honest care: conserve the record, conserve operational reliability, conserve narrow authority, and stop pretending that scarcity can be governed by old allocation language once the resource has become capital.