RIPE NCC is a test case for what happens when a registry built to administer unique network identifiers finds itself maintaining the reference ledger for assets that operators buy, lease, finance, defend, and treat as strategic inputs.
The accounting shock behind exhaustion
IPv4 scarcity is often described as a technical exhaustion story. That is true and too small. The more important story is an accounting shock. A number that once looked like an administrative entry became a scarce production input. A registry record that once looked like clerical coordination became part of balance-sheet confidence. A transfer request that once looked like database maintenance became a closing condition. A fee vote that once looked like association administration became a question about the cost of access to a recognised ledger.
RIPE NCC is the best mature case for examining that change. It is not a failed institution. It is not a peripheral 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 maintains number-resource registration data, supports the RIPE Database, processes resource transfers, operates RPKI services, supports reverse DNS and related infrastructure, and convenes a policy environment whose culture is open, technical and unusually well documented. Precisely because it is mature, it cannot explain post-exhaustion pressure as the side effect of institutional collapse.
The central question is whether RIPE NCC can remain a ledger when the entries in the ledger have become capital-like assets. A ledger records recognised holdership, prevents duplicate claims, supports accurate contact and routing-security data, and makes legitimate movement possible. A gatekeeper decides whether capital may move, whether secondary use is morally acceptable, whether a holder's business model deserves continuity, or whether a compulsory association can expand its own scope because the record it keeps is indispensable. The distinction is not ideological. It determines whether scarcity is priced mostly as a market fact or whether an additional registry-risk premium sits on top.
Official RIPE NCC materials are useful here as factual exhibits, not as an interpretive court of appeal. They record the IPv4 run-out sequence, waiting-list policy, transfer conditions, 24-month transfer restrictions, inter-RIR transfer requirements, sanctions checks, charging schemes, policy-development structure, audit activity, RPKI services and trust commitments. Those documents do not settle the economic interpretation. Institutions naturally describe their own conduct through the language of stewardship, community, service and stability. The stronger frame comes from institutional economics and from the public arguments made by market participants, leasing firms, critics and operators: once number resources become scarce operational capital, the institution that records them must be judged by how much uncertainty it removes and how much discretionary risk it adds.
That frame does not require pretending that IPv4 addresses are ordinary land, shares or spectrum licences. They are not. Their value depends on global uniqueness, registry recognition, operational use, routing acceptance, reputation, clean transferability, reverse DNS, RPKI, abuse history, and contract continuity. They have no physical form, but neither do many economically important rights. A company can sell, lease, reserve, collateralise in practice, or impair an IPv4 block because customers and networks treat the block as useful. The registry does not create that usefulness by decree. It records and secures the relationship that makes non-conflicting use possible.
The post-exhaustion task for RIPE NCC is therefore conservative in the best sense. It should make the official path cheaper than the shadow path. It should make transfers more predictable than workarounds, audits less frightening than stale data, RPKI more reliable than informal routing claims, and membership fees more defensible than resentment. If it does, scarcity is absorbed by a disciplined ledger. If it does not, scarcity is multiplied by a gatekeeper.
Why RIPE NCC is the cleaner scarcity test
Scarcity is easiest to misread when it is attached to scandal. AFRINIC's public crisis, receivership history, litigation and election disputes make it tempting to treat the scarcity problem as a question of one weak registry. ARIN's North American market makes it tempting to treat the problem as a question of needs-based transfer policy and legacy-rights doctrine. RIPE NCC is different. It is the registry whose ordinary competence makes the structural question harder to avoid.
The RIPE NCC service region contains wealthy European incumbents, smaller regional ISPs, public institutions, cloud and data-centre operators, Middle Eastern growth markets, post-Soviet administrative histories, conflict exposure, sanctions-sensitive members, legacy holders, brokers, multinational buyers and technically sophisticated policy regulars. A rule adopted in this region is not experienced uniformly. A flat membership fee can be trivial in one market and material in another. A sanctions check can be a routine compliance step for one transfer and a business-continuity risk for another. A mailing-list discussion can be easy for a regular participant and invisible to a small operator whose staff are focused on keeping customers connected.
This diversity makes RIPE NCC's neutrality valuable and expensive. The institution must use company documents, country codes, legal records, sanctions lists, policy terms, certification systems and transfer procedures without becoming a geopolitical or commercial allocator. It must operate under Dutch law while serving networks whose business, legal and political realities do not share one centre. It must preserve a record that courts, banks, buyers, sellers, routers, lessors and customers may all rely on for different reasons.
That is why the mature-registry case matters more than a dramatic failure case. In a failed registry, everyone can agree that records must be protected. In a mature registry, the question is more subtle: have the ordinary instruments used to protect records become instruments of market governance? The charging scheme, transfer review, 24-month restriction, audit request, sanctions screening, RPKI status and policy-list outcome may each be defensible in isolation. Together they define the risk environment around scarce address capital, and they do so without needing to announce themselves as regulation.
The right standard is not anti-registry suspicion. The Internet needs accurate number-resource records, and RIPE NCC performs useful functions. The right standard is whether RIPE NCC's authority remains narrow enough for affected parties to price, understand and challenge. A holder should know what the annual fee buys, what a transfer review verifies, what the waiting period prevents, how sanctions screening affects a file, what an audit can demand, how RPKI terms change, what data is public, what remedy is available, and when a dispute will be isolated rather than converted into customer harm.
RIPE NCC already publishes many of these materials. That is a strength. The post-exhaustion question is whether publication operates as restraint or merely as procedural density. A rulebook can limit discretion. It can also multiply hooks. A reliable ledger gives the market enough certainty to transact through the official record. A gatekeeper gives the market enough uncertainty to design around it, and the design-around is where leasing chains, contractual wrappers and shadow allocation begin to look rational.
From last /8 to last /24
The official run-out sequence is the starting point. RIPE NCC's IPv4 run-out materials describe a shift from needs-based allocation under relative abundance to final-pool rationing and then to exhaustion. For most of RIPE NCC's history, Local Internet Registries could receive IPv4 addresses if they supplied documentation such as network plans. In 2012, when RIPE NCC reached its final /8 block, community policy restricted allocations so that each LIR could request one single /22, or 1,024 addresses. In November 2019, the available IPv4 pool was exhausted. The current waiting-list policy allows LIRs that have not yet received an IPv4 allocation to request one /24 from addresses that may be recovered in the future.
The numbers matter. A /22 was already a ration, not a growth programme. A /24 is a minimal operational unit in many routing contexts and can be very useful to a small network, but it is not an industrial supply solution for a hosting company, a national access operator, a cloud platform, a large enterprise, a data-centre business or an operator with acquisition plans. The waiting list is a residual fairness device. It cannot recreate abundance.
That sequence changed the meaning of RIPE NCC's record. Before exhaustion, the registry could plausibly be understood mainly as an allocator: it judged eligibility, issued resources from a common pool and kept records. After exhaustion, the primary economic activity moved outside the free pool. Operators acquired surplus addresses through transfers, leasing, corporate acquisitions, address-sharing arrangements, renumbering projects, CGNAT, IPv6 deployment or some combination of those methods. The registry remained central, but its centrality changed. It no longer stood only at the entrance to a pool. It stood at the recognised record layer for resources already embedded in markets.
Scarcity also changed the value of old holdings. A block received in an earlier administrative era may now sit inside a company's strategy as an unrealised balance-sheet asset, even if formal accounting treatment varies and the registry avoids property language. A university, enterprise, telecom operator or hosting company with clean address space has optionality: use it, sell it, lease it, reserve it for growth, contribute it to an acquisition, or keep it as defensive continuity. A newer entrant without such holdings must buy, lease or redesign around scarcity at today's cost.
This is not a moral argument about whether early holders deserve windfalls. It is an institutional fact. Scarcity converts history into advantage. The registry cannot abolish that fact by using allocation-era vocabulary. It can only decide whether its procedures make the resulting market safer, more transparent and more liquid, or whether they add uncertainty to an already unequal distribution.
The waiting-list system should therefore be treated honestly. It is useful for late entrants who need a small block and qualify under published rules. It is useful as a signal that RIPE NCC still has an equity tool for those without previous allocations. But the post-exhaustion economy is not organised around the waiting list. It is organised around the record, transferability, leasing, operational reputation and confidence that the official path will not surprise the parties. Once that is understood, the ledger's job becomes clearer: it should not try to recreate abundance through administrative nostalgia. It should make scarcity legible.
Assetization without magic property language
IPv4 address blocks are awkward assets because they do not fit the mental categories that regulators, accountants and registry communities prefer. They are not land. They are not equipment. They are not corporate shares. They are not ordinary licences issued by a state. They are globally unique numbers whose operational value depends on recognition and routing. Yet the market treats them as capital because they can support revenue, reduce customer friction, enable services, carry reputation, move through transactions and protect continuity.
This is the point at which official registry language becomes least satisfying. Registries often avoid saying that number resources are owned property. That caution has legal and historical reasons. It also fails to describe what operators experience. A block that supports customers, geolocation records, email reputation, firewall allowlists, reverse DNS, RPKI objects, abuse processes, hosted services and service contracts is not a disposable annotation. It is an operating input. If a registry action, transfer delay, sanctions restriction, audit dispute or contractual closure impairs that input, the holder suffers a cost that looks very much like asset impairment, even if no one writes "property" in the policy manual.
Lu Heng's notes on IPv4 value, scarcity and registry power push this argument more aggressively than an official registry would. They frame IPv4 as underpriced service-enabling capital, argue that policy barriers and ownership ambiguity suppress market value, and criticise RIRs for turning uniqueness into discretionary authority. Readers should treat those notes as participant arguments rather than neutral adjudication. Their value is not that every conclusion must be accepted. Their value is that they ask the right economic question: if market participants commit capital around IPv4 resources, what liability and accountability should attach to the institution that can affect recognition, movement and security around those resources?
The same mechanism is visible without adopting maximal property language. A cleanly registered /20, /18 or /16 has value because it can be routed, transferred, leased or used. A block with disputed corporate authority, stale contacts, dirty abuse history, broken RPKI, unclear legacy status or uncertain transfer eligibility is worth less. A block stuck behind incompatible inter-RIR policy is worth less to some buyers. A block subject to a 24-month restriction is less liquid for a period. A block attached to a sanctioned party or exposed to sanctions screening risk may be harder to transact. These are asset-quality differences created or revealed by registry-related facts.
The registry does not need to become an asset manager to recognise this. It only needs to accept that its record now has asset-market consequences. That acceptance should make the institution narrower, not grander. The registry should be precise about what it records, what it verifies, what it does not decide, what conditions affect service, and how disputes are handled. It should avoid rhetorical ambiguity: denying asset reality while exercising authority that affects asset mobility. Institutional economics is unforgiving on this point. When a private ordering system becomes essential to an asset's usability, the governance cost of that system is priced into the asset.
Markets can live with unusual assets. They struggle with unusual assets whose reference ledger is discretionary. The safest position for RIPE NCC is not to declare itself owner, sovereign or moral allocator of address value. It is to make the recognised record accurate enough and bounded enough that private actors can bear the market risk themselves.
Transfers as capital-market plumbing
RIPE NCC's transfer pages are where post-exhaustion economics becomes visible. The Transfer of IP Addresses and AS Numbers page states that RIPE NCC authorises and facilitates transfers of Internet number resources, including IPv4, IPv6 and AS numbers, and that all resource transfers are free of charge. That is a useful policy. A registry should not behave like a tollbooth when it records legitimate movement.
But a transfer can be free of administrative charge and still costly in economic terms. If parties cannot predict documentation demands, timelines, sanctions handling, waiting-period effects, legacy treatment or inter-RIR compatibility, the transfer process becomes a risk layer. A seller may accept a lower price from a simpler buyer. A buyer may demand warranties or escrow conditions. A broker may avoid certain registry paths. A corporate acquirer may restructure the transaction around registry timing. A lessor may offer continuity as a substitute for direct purchase. Those costs do not appear as RIPE NCC transfer fees. They appear in price, delay, legal work and the discount applied to a block whose movement depends on a process the parties cannot fully price.
The Transfers in the RIPE NCC service region documentation shows the gate that sits inside the ledger. Transfer requests must be submitted through the proper LIR or sponsoring LIR path, and the resource types, holder status and documents matter. IPv4 addresses and 16-bit AS numbers are restricted by policy from being transferred for 24 months after they have been received from RIPE NCC, received via transfer, or updated after a change in business structure such as a merger or acquisition, subject to published conditions.
That 24-month rule is not a small clerical detail. It is a liquidity rule. It may deter immediate flipping, sham transactions and opportunistic churn around scarce resources. It may protect the integrity of the registry. It also affects capital. A buyer acquiring addresses must consider whether future movement is blocked. A company acquiring a network must consider whether later divestiture is restricted. A holder choosing between sale and lease must consider whether transfer timing changes value. A rule can be justified and still operate as market governance.
Mergers and acquisitions make the same point. RIPE NCC's mergers and acquisitions materials require evidence such as company registrations and legal documents supporting the structural change, and state that the request is evaluated under applicable policies and procedures. They also state that RIPE NCC checks the EU sanctions list and will not approve the transfer request if either party is under sanctions. The purpose is understandable. A registry cannot update high-value records on weak evidence or ignore binding legal obligations. The economic effect is equally clear. Registry approval becomes a condition in a transaction involving operational capital.
Inter-RIR transfers extend the issue across institutional borders. RIPE NCC's inter-RIR transfer materials state that IP addresses and AS numbers can be transferred between the RIPE NCC region and another RIR region, but the other RIR's policy framework also applies. Both registries must approve the transfer before processing. The page identifies transfer paths involving RIPE NCC, ARIN, APNIC and LACNIC, while noting that AFRINIC does not currently have an inter-RIR policy and therefore cannot transfer resources to or from its region through that path.
For a market participant, this is not governance trivia. Registry borders are economic borders. The same technical address block may carry different mobility depending on where it is registered, what the counterparty's region requires, whether policies are compatible, whether a waiting period applies, whether sanctions exposure exists and whether the record can be updated without dispute. Global routing does not eliminate regional registry friction. It makes that friction more visible.
The post-exhaustion transfer standard should be simple to state: verify legitimate authority, prevent duplicate claims, comply with narrow legal obligations, publish known restrictions, record the movement, preserve security data and make legitimate transactions predictable. The registry should not use transfer review to decide whether the market price is desirable, whether the buyer's strategic inventory is morally pure, or whether secondary use offends allocation-era instincts. The thinner the transfer gate, the more valuable the official ledger becomes, because market participants can then take responsibility for commercial risk rather than insuring themselves against administrative surprise.
Leasing is not a footnote
Leasing is often treated as a side issue in registry discussions because it sits uneasily beside allocation vocabulary. It should be central to scarcity analysis. Leasing is what markets do when purchase is expensive, transfer is slow, strategic need is temporary, balance-sheet treatment is inconvenient, or direct registry exposure is unattractive. It separates use from permanent registered holdership. It turns upfront capital expenditure into operating expenditure. It gives smaller operators access to capacity they may not be able to buy. It also creates risks around abuse, continuity, routing authority, contract chain, reputation and transparency.
RIPE NCC's official transfer framework is built around changes in registered holder, mergers, acquisitions, inter-RIR movement and related record updates. Leasing lives partly around that framework. A lessee may originate routes, serve customers and depend on address capacity without becoming the registered holder. A lessor may retain the registry relationship, RPKI authority or control over certain updates. Intermediaries may sit between them. Abuse desks, ROAs, route objects, geolocation records and reverse DNS may all need alignment. If they are not aligned, the market has created a shadow allocation layer: economically real, operationally consequential, and only partly visible in the registry record.
The easy answer is to condemn leasing as speculation or to ignore it as a private contract matter. Both answers fail. Condemnation fails because scarcity makes leasing rational. A growing ISP, hosting provider, VPN operator, SaaS platform or enterprise network may need IPv4 reachability without wanting to buy a block at market price or wait through a transfer. Ignoring leasing fails because operational harm can follow if the registry record, route authorisation, abuse handling and responsible-party data do not match reality. The institutional problem is not that leasing exists. The problem is whether leasing becomes a transparent secondary-use market or a substitute registry in which commercial intermediaries hold the facts that public infrastructure needs.
LARUS and NRS materials are important here because they do not treat leasing as an embarrassment. They frame it as a continuity and risk-management product: first-party address supply, fewer intermediary layers, accountable lessor relationships, and upstream absorption of registry uncertainty. Those are participant claims, and readers should understand the commercial interest behind them. But the claims reveal a real market demand. Operators do not only want numbers. They want reliable use of numbers under conditions where the registry layer, transfer market and address reputation do not surprise them.
For RIPE NCC, the institutional lesson is that leasing should be made safer rather than rhetorically wished away. The registry's legitimate interests are accurate records, responsible contacts, abuse handling, routing-security coherence, fraud prevention, and preservation of the recognised holder relationship. It does not need to become the commercial regulator of every lease. It does need enough clarity that leasing does not become a route around all accountability. A ledger that refuses to see secondary use invites precisely the opacity it then condemns.
The best scarcity-aware posture would distinguish transparent secondary use from disguised transfer, fraud or abandonment. If the registered holder remains responsible, that responsibility should be operationally meaningful. If the lessee originates routes, the routing-security objects should not mislead relying parties. If abuse reports go to the wrong desk, the record is not serving its public function. If a lessor can terminate suddenly without continuity safeguards, customers bear risk. If registry policy creates so much uncertainty that all leasing becomes opaque, the registry has worsened the problem it hoped to prevent.
Leasing is therefore a test of institutional realism. A registry that insists only on allocation-era categories will push markets into informal structures. A registry that accepts secondary use as part of the scarcity economy can set narrow requirements that improve transparency without pretending to allocate capital itself.
Small operators pay the scarcity tax twice
The distributional politics of IPv4 scarcity are often misdescribed. It is tempting to say that treating IPv4 as an asset harms smaller operators because it lets wealthy firms buy or hoard addresses. There is some truth in that concern. A large cloud platform, incumbent telecom group or well-funded hosting company can buy ahead, hire counsel, clean reputation problems, manage RPKI transitions and absorb broker costs in ways a small ISP cannot. Scarcity always favours those with capital and administrative capacity.
But denying asset reality does not automatically help smaller operators. It can hurt them twice. First, they pay the market price of scarcity because they lack historical holdings. Second, they pay the procedural price of a registry model that still speaks in allocation-era language while the real supply channel has moved to transfers, leasing and acquisitions. A large operator can carry that procedural cost. A small operator feels it as management time, legal uncertainty, delayed growth and dependence on intermediaries. The language of stewardship may sound egalitarian, but an opaque stewardship regime often favours the party with counsel, time and a back office.
The RIPE NCC waiting list softens this problem only at the margin. A /24 from recovered space can be useful. It can help a small network establish multihoming, isolate services, support limited hosting, or avoid worse workarounds. But it cannot supply growth at scale. A small access provider that needs address capacity for customer routers, CGNAT pools, business services, VPN endpoints or hosted applications still has to confront the market. The question is therefore not whether market scarcity exists. It is whether the official registry environment makes market access safer for smaller participants.
Policy friction can unintentionally favour incumbents. If transfers are uncertain, a firm with a compliance team navigates them better. If leasing is stigmatised, a smaller operator loses a flexible channel and may be forced into a worse contract. If audit expectations are unclear, a large operator can assign staff while a small operator loses executive attention. If policy debate happens in public mailing lists with high attention costs, larger and more connected participants have more influence. If fees fund a broad institutional bundle rather than the narrow ledger, the smallest members carry a compulsory burden without necessarily receiving proportional benefit.
This is why the poverty-penalty critique in Lu Heng's notes matters even for readers who do not accept every conclusion. The phrase points to a real mechanism: formal equality can become practical inequality when every member faces similar process, similar fees and similar procedural obligations despite very different capacity. A flat fee, an open list, a public transfer page and a standard audit process may look equal. In practice, the cost of using them can differ sharply by market, staff depth, language, legal exposure and cash flow.
A scarcity-aware RIPE NCC would therefore treat small-operator protection as a market-access problem, not as nostalgia for free-pool allocation. It would make transfer preconditions plain, publish common documentation failures, support clean leasing practices, explain RPKI transitions in operational language, keep compulsory fees close to essential registry functions, and design policy summaries for members who cannot monitor every thread. It would not pretend that a /24 waiting-list path solves the economics of a region where IPv4 reachability remains commercially required.
The practical test is whether a small operator can understand its choices without a specialist adviser. Can it tell whether buying, leasing, waiting, renumbering, using CGNAT or deploying IPv6 changes its registry exposure? Can it know what documents a future transfer will require? Can it see whether a block's reputation, ROAs, reverse DNS and registry status are clean? Can it understand whether a policy change affects future mobility? If the answer is no, scarcity has become a complexity tax. Complexity is rarely paid by the largest actors first; it is capitalised by them and suffered by everyone else.
Due diligence is now part engineering and part finance
IPv4 due diligence used to be a technical hygiene exercise. A buyer, lessor or operator wanted to know whether a block was routed, whether contacts were current, whether reverse DNS was manageable and whether the addresses had abuse or blocklist problems. Those questions remain. Scarcity has added financial and legal layers. A serious IPv4 review now asks who the legitimate holder is, whether corporate authority is documented, whether a transfer restriction applies, whether RPKI objects will need to be changed, whether IRR data and geolocation records are stale, whether sanctions screening could affect the parties, whether the resource is legacy, whether any sponsoring LIR relationship exists, whether a lease contract gives operational continuity, and whether registry timelines fit the commercial closing. The diligence room now contains engineers, lawyers and finance staff because the address block has become part of the production system and part of the transaction perimeter.
That mixed due-diligence stack is evidence of assetization. A number resource has become valuable enough that lawyers, engineers, finance teams, abuse desks and routing-security staff all have something to check. The risk is not only that a route will fail. It is that a transaction will fail, a warranty will be breached, a customer migration will be delayed, an email-reputation problem will impair service, a sanctions issue will block recognition, or a certificate change will create routing-security confusion.
RIPE NCC can lower these costs without replacing the market. It can publish better process statistics, clearer transfer examples, more practical RPKI transition guidance, audit category data and status information that helps parties distinguish remediable defects from serious authority problems. The goal is not to turn RIPE NCC into a broker, valuer or legal adviser. The goal is to make the official record more useful to those who must perform diligence anyway.
The economic importance of this point is easy to miss. Markets do not value only the underlying resource. They value the transaction cost of obtaining, keeping and using it. Two blocks of the same size can trade or lease differently because one has clean registry history, clear corporate authority, no pending restriction, reliable ROAs, coherent reverse DNS, clean abuse reputation and a responsive holder, while the other requires weeks of explanation. Registry reliability becomes capitalised into the price.
This is one reason the ledger-versus-gatekeeper distinction is not abstract. A ledger reduces due diligence by making facts legible. A gatekeeper increases due diligence by making outcomes depend on discretion. If RIPE NCC wants the official registry path to remain central, it should make diligence around that path as boring as possible. Boring is not a pejorative in infrastructure finance. It is the condition under which capital can move without excessive insurance against the recordkeeper.
Membership fees and the cost of a necessary ledger
Scarcity also changes how members read fees. In an abundant era, membership fees can be described as the cost of participating in a technical coordination system. In the post-exhaustion era, the fee is also part of maintaining a relationship with the recognised ledger for scarce operational capital. That does not make the fee illegitimate. It makes scope discipline more important. The more the registry relationship resembles a necessary input to asset confidence, the more members will ask whether mandatory charges are paying for the ledger itself or for the institution that has grown around it.
RIPE NCC's Charging Scheme 2026 keeps the annual contribution at EUR 1,800 per LIR account. It also maintains additional charges for independent and legacy Internet number resources and ASN assignments in specified categories, and a one-time sign-up fee for new members or additional LIR accounts. Members vote at the General Meeting each year on returning excess paid fees or shortages through redistribution. The model is transparent in a way many private infrastructure charges are not. It is still a compulsory relationship for members who need RIPE NCC services.
A flat LIR fee has advantages. It is simple. It avoids making each IPv4 holding a direct tax base. It supports the association without forcing constant price calculations around every resource. It may be easier to administer than more complex schemes. But it has distributional consequences. A EUR 1,800 charge is not the same economic event for a large Western European incumbent, a small rural ISP, a conflict-affected operator, a currency-stressed market participant, a research network or a new entrant that mainly needs the registry relationship because IPv4 scarcity already raises its other costs.
Lu Heng's September 2025 note on RIPE NCC costs argues that the core mandate is narrow: registration database, number-resource administration and RPKI. It criticises the bundling of meetings, travel, training, measurement platforms and community infrastructure into compulsory fees, citing a projected 2024 budget of EUR 38.2 million, roughly EUR 9.6 million allocated to core registry services and about another EUR 10 million to basic operational support. The note argues that optional or value-added activity should be funded voluntarily rather than through a blanket member levy. Again, this is a participant argument. Its analytical value is that it separates the essential ledger from the institution around the ledger.
RIPE NCC's own service portfolio is broader than the minimal ledger. It includes the RIPE Database, LIR Portal, RPKI, resource transfers, reverse DNS, K-root involvement, RIPE Atlas, RIPEstat, RIS, RIPE IPmap, training, meetings, country reports and community support. Many of these services are useful. Some are public goods. Some may lower coordination costs for networks beyond the membership. The economic question is not whether they are good. The question is whether a private membership association whose record is necessary for scarce resource confidence should fund all useful ecosystem activity through a compulsory fee bundle. Scarcity makes the distinction sharper because an operator cannot simply walk away from the reference ledger when it dislikes the institutional bundle.
The scarcity-era fee principle should be strict. Mandatory charges should be tied as closely as possible to uniqueness, registration accuracy, publication, transfer recording, reverse DNS, RPKI, security, dispute isolation and compliance that the ledger cannot avoid. Optional services should be justified separately, funded voluntarily where feasible, or measured in a way that shows broad member benefit. A registry that can explain its fee as the cost of a reliable record is more legitimate than a registry that explains it as the cost of a broad institutional identity.
Fee scope is not a side argument about budgets. It is a signal about power. A ledger should be cheap where possible because its compulsory character is justified by necessity. A gatekeeper can become expensive because the institution starts to treat its own expansion as part of the public good. Members may tolerate that in good times. Scarcity makes them ask what they are actually paying for, and whether the fee is the price of reliability or the price of institutional discretion.
Policy lists after price signals appear
RIPE's open policy culture is one of the institution's strongest assets. The RIPE policy development process is described as open, bottom-up and consensus-based. Policy discussions happen at RIPE Meetings and on Working Group mailing lists. Meetings and lists are open, archives and minutes are public, policies are documented, and participation does not require RIPE NCC membership. That is a serious legitimacy advantage over closed administrative decision-making.
But open process is not the same as equal economic representation. Attention is scarce. Operators run networks. Smaller members may lack staff, English-language confidence, procedural memory or time. Some participants may fear public disagreement in sensitive jurisdictions or commercial contexts. Some affected customers are not RIPE NCC members at all. Brokers, buyers, lessors, enterprise users and downstream customers may discover the effect of a policy only when a transfer, audit, certification issue or fee dispute touches them.
This matters because the content of policy changed after exhaustion. A policy on allocation size once decided access to a pool. A policy on transfer restriction now affects liquidity. A policy on RPKI delegated CA behaviour can affect security objects used by relying parties. A policy on ASN criteria can affect routing plans. A policy on legacy handling can affect historical asset confidence. A policy on audits can affect continuity. A policy on fees can affect the cost of holding the registry relationship. The public list remains open, but the consequences have become more capital-intensive.
The risk is policy-list absolutism. Because the process is open, outcomes may be treated as if all affected parties have consented. Because archives exist, silence may be read as acceptance. Because RIPE is technically respected, criticism may be treated as impatience with consensus. That is dangerous in a scarcity economy. Silence may mean agreement. It may also mean absence, fatigue, language barriers, fear, lack of awareness or rational inattention. An open door is not the same thing as a low cost of entry.
The remedy is not to abandon open lists. The remedy is to add reliance analysis. When a proposal affects transferability, waiting periods, RPKI obligations, legacy treatment, audit consequences, fees or service eligibility, the process should state who is likely to bear cost, who is likely to be absent, what market behaviour may change, what the fallback path is and how the effect will be reviewed after implementation. Consensus should be informed by economic consequences, not merely by the number of visible list participants.
The 2025-02 policy implementation on persistently non-functional delegated RPKI certificate authorities is a useful example. RIPE NCC's policy-implementation materials state that the proposal gives RIPE NCC a mandate to revoke resource certificates associated with long-time non-functional delegated CAs in order to reduce relying-party workloads, with updated certification-service terms published in May 2026 and effective in June 2026. That may be technically sensible. It also shows policy-list output entering the operational trust chain. Revocation of certificates is not just a sentence in a mailing-list archive. It is a change to the security layer around address recognition.
In a scarcity economy, the policy list should be treated as a constitutional instrument for a market-facing ledger. It does not need to become a legislature. It does need to stop assuming that procedural openness alone answers questions of economic effect.
Reliability is the scarcity product
After exhaustion, RIPE NCC's core product is not allocation. It is reliability. The market needs a record it can trust, a transfer process it can price, a certification system it can rely on, an audit culture it can understand, a fee structure it can defend, and a legal-compliance posture it can plan around. The registry may still describe many of these functions separately. The market experiences them as one dependency stack. A failure in one layer does not remain neatly in that layer when customers, contracts, routing security and transaction finance all depend on the same recognised record.
The RIPE Database and RDAP or Whois publication support recognised holdership and contact data. Reverse DNS supports operational hygiene. Transfer recording supports asset mobility. The LIR Portal supports member administration. RPKI supports route-origin assurance. Audit activity supports data quality. Sanctions checks support legal compliance. Trust Portal materials support confidence in confidentiality, integrity and availability. General Meetings and policy lists support accountability. Each function has a technical or procedural description. Together they determine whether a RIPE NCC-registered IPv4 block carries a confidence premium or a risk discount.
RPKI is the clearest example of reliability becoming economic. RIPE NCC's RPKI materials describe a system in which LIRs can request resource certificates listing the Internet number resources they hold, allowing verifiable statements about route origin through ROAs. Operators still decide how to use validation states. RIPE NCC does not command global routing. But as more networks incorporate route-origin validation into routing policy, the registry-recognised relationship becomes part of operational security. A resource certificate is not merely a database field. It is a cryptographic expression of recognised holdership.
That increases both the value and the danger of registry authority. A reliable RPKI service strengthens the ledger because it lets networks verify authorised origin claims. A discretionary or poorly explained certification change can raise the stakes of a registry dispute. A closure, audit, transfer or delegated-CA problem can become more than an administrative issue if it affects route-authorisation data. The right answer is not to weaken RPKI. It is to make RPKI authority narrow, technical, evidence-based and transparent, so that cryptographic assurance does not quietly become institutional leverage.
Audit activity belongs in the same category. RIPE NCC's audit and Assisted Registry Check materials describe a mandate to keep the RIPE Registry up to date and correct, including checks of legal name, address, contacts, contact persons, resource-registration correctness, routing and BGP announcement mismatches, and reverse-DNS delegation issues. A serious registry needs such checks. Fraudulent control, stale contacts and incorrect records harm the whole system. But audits become economically sensitive when failure to provide requested information can lead to serious contractual consequences.
The legitimacy line is proportionality. A cooperative data-quality review strengthens the ledger. An open-ended demand that members fear as existential strengthens the gatekeeper. Lu Heng's note on RIPE NCC phishing emails is relevant for this reason. The fake "Download Review" demand was not RIPE NCC process. But the scam exploited a belief that registry messages can threaten continuity. Fear itself becomes an operational cost. Members who fear the registry may over-lawyer updates, delay corrections, avoid engagement or rely on intermediaries. A narrow audit culture reduces that cost because it lets members separate routine hygiene from true continuity risk.
Reliability also includes service continuity under stress. A registry should not surprise operators through downtime, credential compromise, unclear law-enforcement responses, unexplained data changes, opaque sanctions handling or sudden RPKI shifts. The RIPE NCC Trust Portal is valuable because it makes confidentiality, integrity and availability visible. But trust is broader than cybersecurity. It includes governance trust: who can decide, what evidence is used, how delays are measured, how appeals work, how legal constraints are communicated, and how running-network continuity is protected when a dispute is unresolved.
In the scarcity era, reliability is not a support function. It is the thing being bought with trust.
Accountability disputes are market information
Institutions prefer to classify criticism as politics. Markets treat it as information. Fee disputes, transfer complaints, sanctions anxiety, audit fear, phishing susceptibility, policy-list frustration, national-regulator concerns, legacy-resource uncertainty and demands for transparency all indicate where the registry's authority is costly. Not every complaint is correct. But every recurring complaint deserves analysis because scarcity makes the cost of institutional uncertainty measurable. A capital market does not need a complaint to be morally pure before it treats the complaint as a signal of friction.
The fee dispute reveals distributional stress. A member who objects to the compulsory bundle may not be rejecting RIPE NCC's existence. It may be saying that the cost of the ledger should not subsidise all institutional ambitions. The transfer dispute reveals liquidity stress. A broker or holder who complains about documentation or waiting periods may be self-interested, but the market still needs predictable time-to-completion and clear denial categories. The audit dispute reveals fear of discretionary escalation. The sanctions dispute reveals the cost of operating under Dutch and EU legal obligations in a region that includes sanctioned and conflict-exposed actors.
BTW's RIPE NCC coverage has tracked several public signals around accountability, member visibility, Trust Portal transparency, Montenegro and Kosovo-related concerns, and registry-neutrality disputes. Those reports should not be treated as independent proof of every underlying claim. They are useful because they show where registry records become public governance. When a national regulator or public authority questions how registry data handles territorial or address-allocation issues, the registry is no longer invisible plumbing. It is a recordkeeper whose choices are read by political, legal and market actors.
The official response to accountability pressure should not be institutional defensiveness. It should be friction data. How long do intra-region transfers take by category? How many requests are delayed because documents are incomplete? How often are sanctions checks decisive? How many legacy updates are handled on a best-effort basis, delayed or abandoned? How many Assisted Registry Checks are voluntary, random or matter-specific? How often do audits end in ordinary correction rather than escalation? How many delegated RPKI CA notifications are sent, repaired or revoked under the new policy? How often do voluntary transfer locks appear, and for what broad reasons? These numbers would not turn RIPE NCC into a market supervisor. They would show whether the registry's own processes are reducing or adding transaction costs.
Some information must remain confidential. Aggregate process data is different from disclosing private transactions. It tells the market whether the gate is narrow or wide. It helps members distinguish real requirements from rumours. It lets buyers and sellers price timing. It lets smaller operators understand whether they need counsel or only better documents. It lets RIPE NCC show that its authority reduces risk rather than adding it.
Accountability disputes also reveal the private-public contradiction in the registry model. RIPE NCC is a private membership association. It performs a public-reference function. Its members vote, but affected parties extend beyond members. It is not a state, but its record can matter to courts, banks, public networks, customers and security systems. It is not a market regulator, but its policies affect liquidity. The contradiction cannot be eliminated. It can be managed only through narrow authority, measurable process and humility about what the association does not decide.
A mature registry should welcome this discipline. In a scarcity economy, the critic is not always right, but the existence of sustained criticism is evidence about where trust is expensive.
The region turns neutrality into a cost problem
RIPE NCC's region makes every scarcity decision more complex. Europe brings EU law, data-protection obligations, sanctions regimes, national regulators, sophisticated incumbents and heavy institutional scrutiny. The Middle East brings fast-growing infrastructure demand, sovereign telecom policy, cross-border investment and geopolitical sensitivity. Central Asia brings post-Soviet administrative histories, smaller markets and varying state capacity. The service region also includes operators affected by war, currency constraints, sanctions exposure and international banking friction.
Neutrality in this environment is not a slogan. It is a set of constrained practices. RIPE NCC can use country names and ISO codes for operational and informational purposes while stating that such use is not an endorsement of international status. It can comply with applicable sanctions law while trying to preserve running-network continuity within legal limits. It can evaluate corporate documents without becoming a commercial judge. It can maintain RPKI and database services without pretending that legal jurisdiction has no effect.
The sanctions check in mergers and transfers is a concrete example. It is legally understandable. It also creates market risk. A buyer, seller, lender or acquirer must ask whether either party's status will block registry approval. A member in a sensitive jurisdiction must ask which services remain available, which payments can be processed, whether support can continue, whether certification is affected, and how disputes will be communicated. The more clearly RIPE NCC publishes process and aggregate categories, the lower the uncertainty. The more it relies on case-by-case reassurance, the higher the discount.
Regional diversity also changes fee politics. A flat EUR 1,800 annual LIR contribution may be modest for a large operator and meaningful for a smaller one. The issue is not only income. It is also currency volatility, war exposure, sanctions-related payment friction, local market size and the cost of participating in policy governance. If compulsory fees fund only essential ledger functions, the distributional burden is easier to defend. If they fund a broad institutional ecosystem, the burden becomes politically and economically harder to justify across such a varied region.
The same diversity affects policy participation. A large operator or consultant can monitor lists, attend meetings, understand procedural history and speak publicly. A smaller operator in a sensitive market may lack staff, time or appetite for public challenge. A policy process can be formally open and still become attention-weighted toward confident regulars. Scarcity makes that asymmetry more serious because absent parties may later discover that a rule has changed their transfer options, audit exposure, fee burden or routing-security obligations.
The region therefore strengthens the case for institutional modesty. RIPE NCC should not try to solve geopolitical conflict, economic inequality or market pricing through registry discretion. It should maintain accurate records, comply with narrow legal obligations, publish constraints, process legitimate movement, support security and avoid recognition theatre. Neutrality is most credible when the registry can explain exactly what it did and exactly what it did not decide. In a region this varied, ambiguity is not diplomacy. It is a cost.
What a scarcity-aware ledger would do
A scarcity-aware RIPE NCC would make five costs lower: recognition, movement, secondary use, reliability and disagreement. That is a narrower ambition than governing the IPv4 economy and a harder one than preserving old vocabulary.
Recognition should be cheaper because the record is precise. The registry should make it clear who is the recognised holder, what status the resource has, what restrictions apply, whether legacy treatment matters, whether a contract or sponsorship relationship exists, and what security services are attached. It does not need to resolve every philosophical ownership debate. It does need to avoid ambiguity that lets the institution deny property language while exercising asset-like control.
Movement should be cheaper because transfer review is predictable. The official path should verify authority, documents, policy restrictions and legal constraints without becoming a discretionary judgement about the buyer's strategy or the seller's motives. Transfer statistics should not only list completed transfers but also help the market understand friction. The aim is not to maximise movement for its own sake. It is to make legitimate movement less uncertain than informal workarounds.
Secondary use should be cheaper because leasing and similar arrangements are brought closer to operational truth. If a holder remains responsible for resources used by customers or lessees, that responsibility should be connected to real abuse handling, route-authorisation hygiene, reverse DNS and contact accuracy. If the registry tries to pretend secondary use is peripheral, the market will create opacity. If it recognises the practice narrowly, it can reduce risk without regulating every commercial term.
Reliability should be cheaper because RPKI, reverse DNS, the RIPE Database, the LIR Portal, audits, sanctions processes and trust commitments are treated as a single dependency stack. A member should not have to guess whether an audit could affect RPKI, whether a transfer could change ROAs, whether a sanctions issue could affect support, or whether a policy proposal could change certification terms without clear notice. The more integrated the dependency, the more explicit the safeguards must be.
Disagreement should be cheaper because disputes are isolated. If holdership, corporate authority, sanctions status, legacy evidence or policy compliance is disputed, the default should be preservation of the last verified operational state where law and security permit. The registry can freeze conflicting updates, request documents, annotate status, apply narrow restrictions or seek legal clarity. It should be slow to produce customer harm, forced renumbering, broken route security or broad service termination unless the evidence and legal duty are clear.
These are not radical demands. They are the demands that follow from scarcity. A ledger for valuable resources must be more careful than a ledger for abundant ones. It must also resist the temptation to become grand. The more valuable the resource, the more tempting it is for the institution around the record to claim a larger public role. That is exactly when narrowness becomes the highest form of legitimacy: the registry matters most when it is least tempted to convert necessity into discretion.
Watchpoints for the next 12 to 24 months
The first watchpoint is transfer friction. RIPE NCC publishes transfer information, but the scarcity economy needs more process performance data. The key signals are time to completion, document cycles, abandoned requests, sanctions-related categories, legacy-update handling, 24-month restriction effects, voluntary lock usage and inter-RIR compatibility. If the official path becomes easier to price, RIPE NCC-registered space should carry a confidence premium. If it remains opaque at the moment of stress, parties will discount or route around it.
The second watchpoint is the fee and activity-plan cycle. The EUR 1,800 annual LIR contribution is stable in the 2026 scheme, but the deeper question is scope. Members should watch whether compulsory fees stay tied to essential ledger functions or continue to support a broader institutional ecosystem without sharper evidence of necessity. Fee discipline will matter more as scarcity keeps address strategy on balance sheets and smaller operators become more sensitive to compulsory costs.
The third watchpoint is policy-list representativeness. Open lists must remain central, but proposals touching transferability, RPKI, legacy resources, audits, fees or eligibility should include economic impact notes and post-implementation review. Scarcity has made policy a market instrument. The process should show that it understands absent parties as well as active speakers.
The fourth watchpoint is leasing normalisation. The more purchase prices and transfer frictions matter, the more secondary use will matter. Watch whether RIPE NCC and the community develop clearer expectations around responsible holders, abuse contacts, routing-security alignment and transparency without trying to turn every lease into a moral dispute. A safer leasing environment could help smaller operators. An opaque one could become shadow allocation.
The fifth watchpoint is RPKI governance. The delegated-CA revocation implementation shows that policy can enter the operational security layer. Watch how notices, timeframes, revocations, restorations and public metrics are handled. RPKI strengthens the ledger if it stays narrow and technical. It raises gatekeeper risk if certification becomes a broad lever.
The sixth watchpoint is audit culture. Assisted Registry Checks and selected audits are necessary for data quality. The market will watch whether they remain cooperative, proportionate and bounded. Public aggregate data on audit categories, remediation time and escalation would reduce fear. Vague audit anxiety would raise the registry-risk premium.
The seventh watchpoint is sanctions and neutrality under legal constraint. RIPE NCC cannot ignore applicable law. It can explain the limits more clearly. The market needs to know which services are affected by sanctions issues, how often categories arise, what parties can do before a transaction, and how continuity is preserved where possible. In a region with war, sanctions and contested status, surprise is expensive.
The final watchpoint is language. Institutions reveal adaptation through vocabulary. If RIPE NCC responds to scarcity questions mainly with stewardship, community and stability language, critics will hear gatekeeper ambition. If it responds with friction data, cost discipline, narrow legal explanations, service metrics, impact analysis and humility about what the registry does not control, it will sound like the ledger the market needs. Scarcity has already changed the asset; the remaining question is whether the institution's vocabulary will catch up without expanding its mandate.
The conclusion: scarcity rewards modest institutions
RIPE NCC's importance is not in doubt. The record it maintains is useful. Its policy culture is unusually open. Its services are documented. Its region needs an accurate registry. The question is whether the institution can adapt its self-understanding to the economics of IPv4 after exhaustion.
The old allocation model assumed that the registry distributed a scarce but administratively governed common resource to qualified networks. The post-exhaustion model is different. IPv4 addresses are already embedded in private networks, customer relationships, purchase agreements, leases, acquisition plans, security objects and strategic reserves. The registry record still matters, but the market now treats that record as part of an asset-quality stack. The registry's legitimacy therefore depends less on ceremonial stewardship and more on whether it lowers the cost of trust. Its success will be measured not by whether scarcity disappears, but by whether scarcity can be transacted, secured and governed without avoidable institutional risk.
That is why RIPE NCC should be strict about its own boundaries. It should keep the database accurate, support RPKI reliably, preserve reverse DNS and registry publication, process transfers predictably, audit proportionately, comply with law narrowly, explain fees clearly, and make policy effects intelligible. It should avoid acting as if open lists, member votes or not-for-profit status automatically authorise every market-shaping consequence. Accountability is not a slogan when a resource is valuable. It is the mechanism by which the registry prevents its own necessity from becoming private power.
The future of IPv4 in the RIPE NCC region will not be decided by one event. The free pool is gone. Waiting-list distributions will be small. Transfers, leasing, corporate transactions, address sharing, IPv6 coexistence and operational reputation will shape the market. RIPE NCC's role is not to deny that economy or to govern it morally. Its role is to keep the recognised record so accurate, secure, affordable and predictable that serious operators prefer the official ledger over workarounds.
Scarcity rewards institutions that know exactly what they are for. A modest registry can be indispensable because it lets others build, route, trade, finance and serve customers without fearing the bookkeeper. A grand registry becomes visible at the moment of dependency and forces every participant to ask whether the institution around the resource may change the rules, delay the movement, reinterpret the status or attach new conditions. RIPE NCC's strongest future is the first one: not a sovereign of number resources, not a moral arbiter of scarcity, but a disciplined ledger for a scarce operational asset.