RIPE NCC is the mature registry case for understanding what IPv4 transfer rules reveal about title certainty, liquidity, information asymmetry and institutional self-interest.
Article
The market hidden inside a registry rule
IPv4 transfer policy looks like administrative plumbing until scarcity makes the pipe valuable. A regional Internet registry may describe a transfer as a change in the holder recorded in its database. A buyer, seller, lender, broker, operator or cloud customer experiences the same event as something closer to settlement. The resource may route before the registry update, but the market usually treats the update as the moment when the claim becomes clean, serviceable and bankable. That is why RIPE NCC is one of the best places to study the economics of transfer market architecture.
RIPE NCC is not a collapsed or obscure institution. It is an independent, not-for-profit membership association based in the Netherlands and the Regional Internet Registry for Europe, the Middle East and parts of Central Asia. Its own What We Do page describes member services such as registry entries, resource transfers, the LIR Portal and RPKI, and wider services such as the RIPE Database, K-root, RIPE Atlas, RIPEstat, RIS, country reports, outreach and learning. That makes RIPE NCC an excellent mature case. The question is not whether a registry can fail in dramatic circumstances, but whether a functioning registry quietly becomes the architect of a market once its ledger entries become scarce operational capital.
The framing used here is institutional economics rather than registry self-description. RIPE NCC, NRO and ICANN materials are useful factual exhibits: they show how the registry says transfers, sanctions checks, legacy-resource updates, RPKI, fees and policy development work. They do not settle the economic meaning of those rules. Number-resource coordination began as neutral bookkeeping, but IPv4 scarcity converted recognised control into a capital-like position. A registry that controls recognition, transfer conditions and security-state continuity therefore needs to be judged by the uncertainty it removes and the uncertainty it creates.
This distinction is not an attack on the registry function. The Internet needs globally unique numbers, accurate registration data, coherent reverse DNS, reliable route-origin certification and a trustworthy way to reflect legitimate changes of control. A registry that does those jobs well increases resource value because counterparties can rely on a stable public reference point. The danger begins when the same institution moves from ledger discipline to gatekeeper discretion. A ledger verifies identity, records a valid transfer and prevents duplicate claims. A gatekeeper decides whether capital may move, whether institutional policy should override market signals, and whether essential registration services can finance a widening bundle of institutional ambitions.
RIPE NCC sits exactly on that boundary. It does not charge a fee for resource transfers. But a zero transfer fee does not make a transfer costless. The real costs are time, uncertainty, documentation, restrictions, sanctions screening, inter-RIR compatibility, legacy status, RPKI continuity, reverse DNS updates, broker reliance and the risk that a rule designed for registry hygiene will operate like a liquidity control. The architecture is not the private purchase agreement alone. It is the combination of private bargain, registry due diligence, policy restriction, public record, security-state transition and institutional confidence.
RIPE NCC is especially useful because its transfer framework is more market-facing than a pure rationing model but still more restrictive than a simple asset registry. Its current transfer policy allows legitimate resource holders to transfer complete or partial blocks of address space or other resources, including IPv4, IPv6 and ASNs, within the service region. It also addresses inter-RIR transfers, including legacy resources; requires transfers to be reflected in the RIPE Database; keeps the original holder responsible until completion; imposes a 24-month transfer restriction on scarce resources such as IPv4 and 16-bit ASNs after receipt, including receipt through a merger or acquisition; and requires RIPE NCC to publish transfer statistics. These are not clerical details. They are the rules by which liquidity, title certainty and information are produced.
The core argument is therefore simple. RIPE NCC's transfer market is not a free market with a database attached. It is a registry-settlement market whose design reveals how much power remains with the bookkeeper after exhaustion. Fraud checks, legal-authority checks, sanctions checks, published transfer history and RPKI continuity are not optional luxuries. Yet every necessary check can become a discretionary choke point if the institution does not measure friction, publish enough process data, isolate disputes narrowly and recognise that the market pays a risk premium for registry uncertainty. Transfer policy is where the post-exhaustion RIR model shows its political economy.
Scarcity turned the RIPE Registry into market infrastructure
RIPE NCC's own IPv4 run-out materials provide the factual spine. Since RIPE NCC began operations in 1992, it distributed IP addresses and ASNs in its service region. In November 2019 it exhausted its remaining IPv4 pool. Its public run-out page says networks in Europe, the Middle East and parts of Central Asia can no longer receive "new" IPv4 addresses from RIPE NCC that have not previously been used by another network, and acknowledges that many networks now mitigate scarcity through the IPv4 transfer market or address-sharing technologies such as CGNAT.
The allocation sequence matters because it explains why transfer rules are now central rather than peripheral. For most of RIPE NCC's history, Local Internet Registries could receive IPv4 addresses against documented need. In September 2012, when RIPE NCC reached its final /8, community policy limited each LIR to one /22, or 1,024 addresses. In October 2019, as the pool narrowed, allocations could be smaller. On 25 November 2019, once available IPv4 space was exhausted, the current waiting-list model applied: eligible LIRs can enter a list to receive one /24 from future recovered space.
A /24 can be operationally meaningful. It can support multihoming, a small service, a test deployment or a late entrant's minimum reachability. It cannot solve the address needs of a hosting platform, a carrier, a national broadband provider, a cloud region, a large enterprise migration, a security platform or a data-centre expansion. The waiting list is a residual fairness device. The main IPv4 economy now lives in transfers, leasing, corporate acquisitions, renumbering, CGNAT and IPv6 transition strategies. Once that happens, the registry record is no longer only an allocation ledger. It becomes part of the market infrastructure for assets already embedded in networks.
The word "asset" should be used carefully. RIPE NCC does not need to describe number resources as ordinary property for the economic point to hold. IPv4 addresses are globally unique operational identifiers whose value depends on routing, reputation, customer continuity, registration, reverse DNS, RPKI, transfer history, contract terms and scarcity. They are not land, shares or spectrum licences. Yet a recognised block can be bought, leased, reserved, financed in practice, priced in an acquisition, or impaired by uncertainty. Market participants behave as if recognised control has value, even where legal vocabulary remains cautious.
That is the crucial post-exhaustion shift. The registry does not create the scarcity; the protocol limit and persistent IPv4 demand do that. The registry does not create every dollar of market value; operators, customers, replacement cost and routing reliance do that. But the registry can change the risk profile of that value. A cleanly recognised block whose holder can transfer it predictably is worth more than a block entangled in uncertain authority, stale data, sanctions exposure, unclear legacy status, a broken RPKI chain or a misunderstood transfer restriction. Registry architecture enters price through risk, not rhetoric.
This is why official transfer language has to be read economically. When a RIPE NCC page says it authorises and facilitates transfers of Internet number resources and that a transfer changes holdership from offering party A to receiving party B, it is describing an administrative event. In the market, the same event is a closing condition. A seller may receive payment only after the registry process reaches a defined point; a buyer may wait to integrate customer networks; a broker may structure escrow around the approval path; and a lender or acquirer may discount a block if the route from contract to registry recognition is unclear. Transfer market architecture begins where administrative description ends.
RIPE NCC's maturity raises the standard: the official path should price better than the shadow path, or the market will treat the registry as another risk layer.
Title certainty starts with recognised holdership
In ordinary commerce, title certainty is the foundation of liquidity. In IPv4 markets, the equivalent is not a land registry deed. It is recognised holdership supported by accurate records, a plausible chain of authority, usable services and a security state that others can validate. A transfer market can tolerate price volatility. It struggles with uncertainty over who can sell, who can receive, which documents prove authority and whether the registry will recognise the change.
The RIPE Resource Transfer Policies, currently RIPE-807, begin from this reality. Any legitimate resource holder may transfer complete or partial blocks of address space or number resources that were previously allocated or assigned by RIPE NCC or otherwise through the RIR model, except where policies require return or restrictions apply. 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 RIPE NCC member. Transfers must be reflected in the RIPE Database. The original holder remains responsible until completion. The current holder must ensure that relevant policies are applied.
These clauses are title-certainty devices. They define the source, the recipient class, the record update and the responsibility bridge before completion. They also show why RIPE NCC is not merely a passive clerk. A purely passive clerk would record whatever two parties present. A registry maintaining global uniqueness cannot do that. It must verify that the offering party is legitimate, the receiving party fits the recognised category, the relevant documents are adequate, and the database update will not create conflicting claims. That verification protects everyone who relies on the record.
The intra-region transfer documentation makes the due diligence concrete. Transfer requests can be submitted only by the offering LIR or by the sponsoring LIR of the offering End User. Resource holders can be LIRs or End Users, and the scenarios include transfers among LIRs and End Users in either direction. Required documents include recent registration documents for legal persons, verified identity documents for natural persons, a transfer agreement signed by authorised representatives, and proof that the signatories have authority. If the receiving party is an End User, RIPE NCC also requires an End User Assignment Agreement with the sponsoring LIR.
This is the sensible face of gatekeeping. A registry that updates high-value records on weak evidence invites fraud. A forged transfer of a valuable block is not an ordinary paperwork error; it can create routing, financial and legal consequences. Documentation requirements preserve title certainty by ensuring that the party claiming authority can act. But due diligence also creates information asymmetry. RIPE NCC sees documents and status details that counterparties may not see, and each side may depend on registry evaluation whose timing and detail are only partly visible.
The policy says the transfer is completed when RIPE NCC updates registration records. That is the moment the market cares about. Before that point, parties may have contract rights against each other, but the public registry state has not moved. After that point, the official reference layer has changed. RIPE NCC's role is valuable because the market trusts the update. It becomes dangerous only if the update is delayed, denied or conditioned for reasons that go beyond protecting the accuracy and security of the record.
Title certainty also requires the registry to distinguish defects. A forged authority document, a missing power of attorney, an unverified natural-person identity, a sanctioned party, a restricted resource and an ordinary incomplete form are not the same problem. Some defects should stop a transfer; some should pause it pending evidence; some should be resolved through correction rather than denial. The more RIPE NCC can make these categories predictable without revealing confidential information, the lower the risk premium attached to RIPE-region space.
This is where the ledger-versus-gatekeeper line becomes practical. A ledger protects title by verifying source and recipient authority. A gatekeeper weakens title when it makes counterparties guess whether hidden institutional judgment will override valid documentation. RIPE NCC's documents show a serious due-diligence framework. The market question is whether that framework is observable enough in performance, not merely in prose.
The 24-month restriction is a liquidity rule
The 24-month restriction is one of the clearest examples of transfer policy as market architecture. RIPE NCC's intra-region transfer page states that IPv4 addresses and 16-bit ASNs are restricted by policy from being transferred for 24 months after they have been received from RIPE NCC, via transfer from another organisation, or following a change in business structure such as a merger or acquisition. RIPE-807 similarly defines scarce resources, including IPv4 and 16-bit ASNs, and bars their transfer for 24 months from receipt, while clarifying that the restriction does not prevent transfers due to further mergers or acquisitions during that period.
The policy logic is understandable. In a scarcity environment, a registry and its community may want to deter rapid flipping, opportunistic speculation, sham reorganisations or conversion of administrative allocations into immediate market inventory. If a participant receives scarce resources and sells them instantly, the policy community may see a failure of stewardship. A waiting period can make arbitrage harder and can preserve the idea that scarce resources should serve operational need rather than only trading profit.
The economic effect is equally clear. A 24-month restriction reduces liquidity. It affects price because a buyer cannot treat the acquired block as fully mobile for two years. It affects corporate planning because a company acquiring a network may be unable to divest associated scarce resources in an ordinary sale unless another merger or acquisition path applies. It affects financing because optionality has value, and leasing because a holder who cannot sell or transfer freely may prefer temporary commercial arrangements over a permanent move. It affects due diligence because the first question is not only "who holds the block?" but "when and how did the holder receive it?"
That does not mean the rule is wrong. It means the rule should be evaluated as a liquidity tax, not as a neutral footnote. Every anti-abuse restriction trades market mobility against policy confidence. A two-year period may be a defensible price for reducing churn, but the registry and community should know what it costs: how many requests are blocked or delayed, how often speculation is actually deterred, how often legitimate restructuring is complicated, and how much more heavily small operators are affected than larger ones that can absorb waiting periods.
The published IPv4 transfer statistics show approved changes, including transfer type and whether a transfer resulted from a business-structure change such as a merger or acquisition. That publication is valuable. It gives the market a public record of movement. But it does not by itself reveal the invisible side of liquidity: attempted transfers that did not proceed, abandoned files, requests delayed by documentation cycles, sanctions-related non-approvals, legacy uncertainty, or cases where the 24-month rule changed transaction structure before a formal request was filed. Approved transfers are the visible part of the market. Liquidity risk often lives in the missing part.
A scarcity-aware registry would therefore treat the 24-month rule as something to measure. Aggregate counts of restriction-related outcomes would not disclose private deals. Common scenarios--direct transfer after a transfer, consolidation among multiple LIR accounts, merger inside the restricted period, partial-block treatment, inter-RIR interaction and legacy-resource differences--could be explained in advance. The goal would not be to weaken anti-abuse control. It would be to reduce uncertainty around a control that has market consequences.
The danger is that anti-speculation language can become a permanent excuse for capital control. Speculation is not always harmful in a scarce asset market. It can supply inventory, smooth price discovery and move resources toward future use. It becomes harmful when it relies on fraud, policy gaming, hoarding obtained from residual pools, or misleading registry records. A good transfer architecture should target the bad mechanism, not moralise every resale. The 24-month rule is defensible only if it remains a narrow, predictable anti-churn device. If it becomes a symbol of registry suspicion toward secondary markets, it raises the risk premium that a good ledger should reduce.
Inter-RIR transfers reveal policy borders
IPv4 addresses route globally, but registry recognition is regional. Inter-RIR transfer policy is where that contradiction becomes visible. RIPE NCC's inter-RIR transfer page says IP addresses and ASNs can be transferred between the RIPE NCC region and another RIR region when the relevant policy frameworks allow it. Both registries must approve the transfer before the registries update their records on a specified date. The page lists transfer paths with ARIN, APNIC and LACNIC, including legacy resources for those relationships in the published categories. It also notes that AFRINIC does not currently have an inter-RIR transfer policy and therefore cannot transfer resources to or from other regions.
This is policy friction, not packet friction. BGP does not need a block to remain in the original RIR's administrative region. A network in one region can route space historically registered in another, subject to practical and contractual arrangements. The friction comes from recognition. A resource can move cleanly across registry borders only where both institutions' policies align enough for a joint update. The registry border acts like a customs border for number-resource capital.
RIPE-807 shows the architecture. Any type of Internet number resource can be transferred to or from the RIPE NCC service region, including legacy resources, unless a policy requires return or a restriction applies. RIPE policies apply while the resource remains registered in the RIPE NCC region and while the transfer is in process. RIPE NCC says it shall accept transfers into its service region when they comply with RIPE transfer policy. For transfers from RIR regions that require the receiving region to have needs-based policies, recipients must provide a plan to RIPE NCC for using at least 50% of the transferred resources within five years. For transfers out, RIPE NCC follows its own regional policy and also complies with commitments imposed by the receiving RIR to facilitate the transfer.
This design is more flexible than a closed regional model. It allows capital movement across regions, recognises legacy resources and does not impose an ordinary needs assessment on every inbound transfer unless the source region's framework requires one. Yet it still creates cross-registry dependency. A buyer and seller must care not only about the private agreement and RIPE NCC's process, but about the other RIR's expectations, documentation and timing. The technical addresses are global; settlement is institutional.
AFRINIC's absence from the inter-RIR transfer map is particularly revealing. For RIPE NCC, it means there is no clean policy path to move resources between the RIPE NCC region and the African registry through the standard inter-RIR framework. That does not stop every operational arrangement involving African networks and RIPE-region resources, but it does mean recognised holdership cannot cross that border through the ordinary channel. The market will price that absence: resources inside a region with no compatible path can carry a mobility discount, and holders may use leases, corporate structures or other arrangements because the official transfer bridge is missing.
Inter-RIR compatibility therefore has a geopolitical and institutional dimension even when no one calls it politics. A restrictive registry can export friction by conditioning transfers on compatibility, and a more permissive registry may still need to satisfy the stricter partner's requirements if its members want access to that market. Transfer rules become a soft form of capital control over scarce digital infrastructure.
RIPE NCC's role is not the same as ARIN's needs-assessment-heavy posture, and it should not be collapsed into it. RIPE NCC's policy is relatively market-facing, especially for intra-region transfers. But the five-year 50% plan requirement for inbound transfers from needs-based regions shows how another region's ideology can enter the RIPE process. A recipient may need to disclose future plans not because RIPE NCC ordinarily demands that for every transfer, but because inter-RIR compatibility requires it.
A better inter-RIR architecture would make three things visible: performance data by RIR pair; status categories that distinguish source-region review, receiving-region review, sanctions screening, business-structure evidence and database cleanup; and policy incompatibility itself as a market risk rather than an obscure registry fact. Inter-RIR transfers are not an administrative side channel. They are the global settlement layer for a scarce resource whose demand no longer respects regional borders.
Mergers and acquisitions are the corporate path around scarcity
Corporate transfers expose another part of the architecture. In an IPv4-scarce world, addresses often move not only through specified resource transfers but through acquisition, merger, restructuring and changes in business form. A company may acquire a hosting business for customers and infrastructure, but also for its address holdings. A telecom operator may reorganise subsidiaries; a data-centre group may consolidate regional entities; a bankrupt estate may sell operating assets. Address inventory can be a material part of the transaction.
RIPE NCC's mergers and acquisitions materials require evidence supporting the change in business structure. Once supporting documentation is received, RIPE NCC evaluates the request under applicable policies and procedures. The page also says RIPE NCC checks the EU sanctions list and will not approve the transfer request if either party is under sanctions. It further states that IPv4 addresses and 16-bit ASNs cannot be transferred for 24 months from the date registry information was updated.
These requirements are not mere formalities. A corporate restructuring path can solve real continuity problems. If the old legal entity no longer exists, or a business line with customer networks changes hands, the registry must be able to update records so that real operational control and public registry state do not diverge. Without such a path, records become stale precisely when business records change, damaging title certainty and operational continuity.
At the same time, the M&A path is a market instrument. If a direct resource transfer is restricted, delayed or uncertain, acquisition of an entity or network may become more attractive. If the M&A path carries its own 24-month post-update transfer restriction, sanctions screening or unclear documentation standards, those features affect valuation, closing conditions and exit planning. If registry approval occurs after commercial signing, the parties must decide who bears the risk of a failed update.
This is where the official distinction between a transfer and a business-structure change becomes economically porous. The registry may need separate procedures for good reasons: a sale of a block and acquisition of a network are different facts. Yet in a scarce market both can move the same resource, and the market will choose the path with the best mix of certainty, timing, tax treatment, legal structure and registry acceptance. Policy architecture therefore shapes corporate structure even when the registry does not intend that effect.
The sanctions element makes the issue sharper. RIPE NCC is based in the Netherlands and must comply with applicable legal obligations. It cannot simply ignore EU sanctions in transfer processing. But sanctions checks are not economically neutral. They affect counterparties, banking, closing conditions, representations, warranties and the willingness of buyers to engage with holders from sensitive jurisdictions. In the RIPE NCC service region, sanctions exposure is not remote. War, geopolitical conflict and financial restrictions can turn an ordinary registry update into a legal-risk event.
A mature architecture should not pretend this risk is avoidable. It should make it more priceable. Parties need to know what is checked, when it is checked, what happens if a party is identified as sanctioned, what documentation helps, what services remain available where law permits, and how running-network continuity is protected during unresolved legal questions. RIPE NCC's pages give the core rule. The market needs the performance detail around the rule.
The M&A path also demonstrates why title certainty cannot be separated from information quality. Corporate registries differ across jurisdictions. Directors change. Powers of attorney vary. Parent structures can be complex, document access uneven, and address histories older than the current business form. The registry must evaluate enough evidence to avoid false updates, but not so much that legitimate continuity becomes hostage to bureaucratic perfection. The economic target is not zero friction. It is proportionate friction whose purpose is clear.
If RIPE NCC can keep the M&A path narrow, documented and predictable, it strengthens the market. It allows resources to follow real operating assets and reduces the incentive to hide changes. If the path becomes slow, opaque or too discretionary, corporate buyers will price registry approval as a special risk of acquiring Internet infrastructure. That is the sort of risk premium a good ledger should not create.
Legacy resources are not historical trivia
Legacy resources are often described as a historical category: Internet number resources obtained before or outside the current hierarchical registry model. In a transfer market, they are not historical trivia. They are supply with a distinct title profile. Legacy status can affect contractual relationships, service eligibility, transfer evidence, RPKI use, buyer comfort and price.
RIPE NCC's legacy-resource page says Internet number resources obtained before or otherwise outside the current hierarchical registry model are considered legacy resources. It also says the RIPE community accepted a policy establishing principles for offering and implementing registry services to legacy holders. The legacy transfer page says legacy resources can be transferred within the RIPE NCC service region. RIPE NCC can help update RIPE Database registration information to reflect the new holder so long as it is clear who the legitimate holder is. Legacy resources transferred in this way retain their LEGACY status. The same page notes that legacy-resource transfer updates are handled on a best-effort basis because legacy resource transfers are not covered by RIPE policies.
That best-effort sentence carries market weight. It tells a buyer that legacy-resource movement can depend on evidence of legitimate holdership and due diligence, but not on the same fully specified policy machinery as ordinary resources. It is sensible for RIPE NCC to avoid pretending that legacy resources have identical origins. It is also a source of uncertainty. If the resource is valuable, "best effort" is not only an operational phrase. It is a risk category.
The inter-RIR page adds another dimension. When resources come from another RIR to RIPE NCC, RIPE NCC determines their status together with the receiving party. Resources with LEGACY status can keep that status. A contractual relationship with RIPE NCC is not required to receive a transfer of resources with LEGACY status, but it is required to use RPKI. That distinction is crucial. A holder may receive the resource record without a direct contract, but use of a key security service depends on a contractual relationship. As RPKI becomes more important for routing assurance, service eligibility can affect economic value.
Legacy resources therefore sit between memory and market. They may have originated before present policy, under weak or unusual documentation histories, and their current users may have changed through decades of mergers, renamed entities or informal operational arrangements. Yet they can be large, clean, valuable and operationally critical. A registry that handles legacy updates well can bring supply into a clearer market. A registry that handles them unpredictably can trap supply or force buyers to demand steep warranties.
The policy challenge is to improve clarity without retroactively rewriting history. If RIPE NCC tries to force every legacy resource into the contemporary member model as the price of practical service, holders may view the registry as converting history into leverage. If it refuses to modernise legacy records, buyers inherit uncertainty and the market discounts the resource. If it offers clear pathways for evidence, voluntary contract relationships, RPKI eligibility and transfer updates, it can reduce risk while respecting distinct origins.
Legacy certainty matters especially for small and mid-sized buyers. Large cloud, carrier or infrastructure buyers can pay counsel to reconstruct corporate history, demand indemnities and absorb delays. A small operator cannot. If legitimate legacy supply stays off the market because records are uncertain, small buyers pay higher scarcity prices. If legacy supply enters the market with poor clarity, small buyers inherit risk they cannot price. The same registry choice therefore affects distribution, not just administrative neatness.
RIPE NCC's strongest position is to make legacy-resource treatment more transparent in categories. What evidence usually proves legitimate holdership? How often do updates fail because authority is unclear? What is the typical timeline? How does a holder decide between no contract, a sponsoring relationship and a direct contract? How does RPKI eligibility change after a transfer? Which parts are policy-bound and which are best-effort? These answers can be published in general terms without exposing private files. In a scarce market, legacy clarity is supply policy.
Information asymmetry is the market's hidden tax
Every transfer market has asymmetric information. Sellers know more about historical use, abuse reputation, customer dependencies, route objects, reverse DNS, geolocation problems and corporate authority. Buyers know more about future deployment and willingness to pay. Brokers know more about competing demand. Registries know more about pending requests, documentation concerns and policy interpretation. Public databases reveal some facts and hide others. The result is a market in which the registry's unpublished process can become as important as the block itself.
RIPE NCC's transfer publications reduce asymmetry in one important way. RIPE-807 requires publication of all transfers, monthly or more often if RIPE NCC chooses. The list includes offering party, the original resource, receiving party or parties, transferred prefixes or resources, transfer date, and whether the transfer was under the transfer policy or due to a business-structure change such as a merger or acquisition. RIPE NCC's IPv4 transfer statistics page says only valid transfers are made public, and that staff regularly check and update the list. Data are available for allocated PA and assigned PI transfers.
This public record matters. It creates an observable transfer history, helps market participants see whether a block moved through a policy transfer or a corporate change, and gives counterparties a way to identify mobility patterns. It reduces the fog that would otherwise surround a high-value secondary market.
But transfer statistics are not the same as transfer transparency. They tell the market about successful approved changes. They do not tell the market about failed or abandoned requests, processing times, document cycles, sanctions hits, voluntary transfer locks that affected negotiations before a formal request, legacy best-effort cases, requests changed from direct transfer to M&A path, or deals that never entered RIPE NCC because counterparties feared friction. A market can look liquid if one counts only completed trades. It may still be illiquid if many legitimate trades die quietly.
The registry does not need to publish private prices or confidential documents. It should not. The useful transparency is aggregate process data: time from complete submission to approval; additional-document cycles; natural-person identity verification; unclear signatory authority; 24-month restriction delays; decisive sanctions screening; inter-RIR waits; and legacy requests that cannot proceed because legitimate holdership is unclear.
Such data would reduce the hidden tax of uncertainty. Buyers and sellers could price timing. Smaller operators could know whether they need counsel or only a better document set. Brokers would compete more on real execution quality and less on mystique. RIPE NCC could show that its process protects the ledger without adding avoidable drag. The same data would also expose problems. That is why it would be valuable.
Information asymmetry is not only a transfer-office issue. RPKI, reverse DNS, routing registry objects, abuse contacts and geolocation data all affect the value of a block. RIPE NCC's Assisted Registry Check materials describe support for registry consistency, resource usage documentation, sponsored resources, routing consistency, RPKI, reverse DNS consistency and network reachability. That is useful because a marketable block is not only a prefix. It is a bundle of records and operational dependencies. A buyer who receives a prefix with stale route objects, broken reverse DNS or poorly managed RPKI inherits hidden costs.
The architecture should therefore make operational quality easier to see. A registry should not become a rating agency for every block. It can, however, make objective registry-state information clearer: current holder, resource type, transfer history, lock status, legacy status where applicable, RPKI availability, reverse DNS status, sponsoring relationship and contact accuracy. The closer the official record gets to operational truth, the less the market relies on insiders who know how to interpret silence.
Information asymmetry is where self-interest often hides. A registry may say it is protecting privacy or confidentiality, and often it is. But confidentiality can also protect institutional opacity. The right balance is not total disclosure. It is disclosure designed around economic reliance. In a scarce market, the public needs to know enough about process performance to trust the ledger without turning private business plans into public records.
Sanctions checks turn legal compliance into transaction risk
Sanctions compliance is unavoidable for RIPE NCC. It is based in the Netherlands, operates in a region affected by war and geopolitics, and must comply with applicable law. Its transfer and M&A pages make the basic rule plain: after supporting documentation is received, RIPE NCC evaluates the request under applicable policies and procedures and checks against the EU sanctions list; if either party is under sanctions, the request will not be approved.
The legal logic is straightforward. A Dutch membership association cannot process transactions as if sanctions law did not exist. The market logic is more complicated. A sanctions check can turn a registry update into a transaction condition. It affects who can buy, who can sell, whether financing can close, whether escrow can release, whether counsel will approve a deal and whether a block associated with a sensitive jurisdiction carries a discount even when the current holder is not sanctioned.
The RIPE NCC service region makes this unusually important. The region includes European Union member states, the United Kingdom, the Middle East, Central Asia, Russia-related exposure, Ukraine-related exposure, sanctioned entities, non-sanctioned entities in risky jurisdictions, smaller operators facing banking friction, and public-sector networks whose continuity may matter to many downstream users. A compliance rule that is routine in one country can be decisive in another. Neutrality cannot mean ignoring law. It must mean applying law in a narrow, predictable and well-explained way.
Sanctions screening also interacts with information asymmetry. A buyer may not know whether a seller has ownership, control or affiliation facts that matter to a sanctions analysis. A seller may not know whether the buyer's ultimate ownership will concern the registry. Corporate documents may be public in one country and opaque in another. Banks may apply stricter screening than RIPE NCC. Counsel may advise caution even where the registry would approve. The transfer market then prices not only actual sanctions status but uncertainty about sanctions status.
The registry cannot remove that risk, but it can reduce surprise. Clearer procedural categories would help: when screening occurs, what parties can prepare before submission, how indirect ownership is considered, what happens if a potential match appears, whether parties can correct mistaken identity, what legal sources are checked, how continuity is handled where transfers cannot proceed, and what aggregate number of requests are affected. Some detail may be legally sensitive. Aggregate transparency is still possible.
This matters because sanctions checks can easily be misunderstood as political discretion. If the registry explains only the rejection result, affected parties may see arbitrary gatekeeping. If it explains the legal constraint, timing, evidence path and review options, the market can distinguish compliance from institutional preference. A registry that wants to remain a ledger in a politically exposed region must make legal compulsion visible without turning itself into a geopolitical authority.
The sanctions rule also affects inter-RIR and M&A transfers differently. In an inter-RIR case, the other registry has its own legal and policy environment. In an M&A case, corporate control may be more complex than in a simple specified transfer. In a legacy-resource case, historical ownership may be harder to prove. The same sanctions check can therefore have different friction depending on path. The market needs path-specific clarity, not only a general warning.
The broader lesson is that a registry can be neutral and still be a source of legal risk. Neutrality is not the absence of constraints. It is the disciplined application of constraints in ways that are narrow, documented and as predictable as law permits.
The policy list is open, but attention is uneven
RIPE's policy culture is one of RIPE NCC's strongest assets. RIPE NCC's policy-development page describes a long-established, open, bottom-up process of discussion and consensus-based decision-making. Policy development happens at RIPE Meetings and on RIPE Working Group mailing lists. Meetings and lists are open to everyone; list archives, working-group minutes and formal policies are public. A person does not need to be a RIPE NCC member or a regular meeting participant to propose policy.
This openness matters. It is better than closed institutional drafting. It lets technically competent outsiders, customers, operators, critics, brokers, academics and affected holders participate, and it distinguishes RIPE, the open community, from RIPE NCC, the membership association and secretariat. In a market shaped by registry policy, visible process is a public good.
But formal openness is not equal participation. Attention is scarce. Operators have networks to run. Smaller firms may lack staff, English-language confidence, procedural memory or appetite for public debate. Some members in politically sensitive environments may avoid visible disagreement. Large incumbents, consultants, policy specialists and long-time community participants can monitor lists and meetings more easily. A policy process can be open and still be attention-weighted toward those with the time and confidence to show up.
That matters more after IPv4 exhaustion. Before scarcity, a transfer rule or resource policy may have looked like technical allocation administration. After scarcity, the same rule can affect liquidity, price, corporate transactions, RPKI eligibility, sanctions exposure, legacy supply and small-operator access. A mailing-list consensus can become a market rule. Silence may mean agreement, but it may also mean ignorance, fatigue, language barriers or the rational choice not to spend scarce operational time on a process that seems remote until a transaction fails.
The policy list should therefore be treated as necessary but not sufficient. For rules that affect transferability, the discussion should include economic impact analysis: buyers of small blocks, legacy holders, sanctioned or banking-friction jurisdictions, brokers, lessors, corporate acquirers and End Users using sponsoring LIRs. A policy that changes liquidity should not be evaluated only by whether active list participants reached rough consensus; it should also say what data will be published after implementation so the community can see whether the rule worked.
The 2025-02 RPKI delegated-CA implementation shows how policy discussions can enter operational trust. RIPE NCC's policy-implementation page says the proposal was accepted by the Routing Working Group on 15 October 2025, gives RIPE NCC a mandate to revoke resource certificates associated with long-time non-functional delegated CAs to reduce relying-party workloads, and says updated certification-service terms were published on 6 May 2026 and would come into effect on 8 June 2026. After that date, RIPE NCC would monitor and notify delegated CA operators if their manifest and CRL cannot be validated and when delegation is revoked after being non-functional for 90 days.
That may be sensible technical hygiene. It also shows that policy-list outcomes can affect the security state around recognised resources. A resource certificate is not a side ornament. RIPE NCC's RPKI materials say RPKI lets LIRs request a digital certificate listing the resources they hold and provides verifiable proof that a holder's resources have been registered by an RIR. As more networks use origin validation, registry policy around certification becomes part of operational reliability. The same logic applies to transfer policy: open discussion can change market conditions.
A mature RIPE process should therefore add economic translation to openness. Every significant proposal affecting transfer-market architecture should include a plain-language impact note, affected classes, uncertainty introduced or removed, evidence needed for implementation, and post-implementation metrics. That would make the open process more credible in a scarcity economy where policy is no longer just allocation etiquette.
Registry self-interest is real even in a non-profit
RIPE NCC is a not-for-profit association. That matters, but it does not eliminate institutional self-interest. Non-profits still have budgets, staff, programmes, reputational incentives, strategic plans, service portfolios and internal definitions of mission. Once a registry relationship is necessary for a scarce resource's public recognition, the association's scope and fees become part of the market's cost structure.
The 2026 Charging Scheme makes this visible. The model is based on an annual contribution per LIR account, with additional fees for independent and legacy Internet resources as defined in the scheme. New members or those with additional LIR accounts pay a one-time sign-up fee, and members vote at the General Meeting each year on returning excess paid fees or shortages through redistribution. For 2026, the annual contribution remains EUR 1,800 per LIR account. The separate EUR 75 charge per independent Internet number resource assignment, EUR 50 charge per specified ASN assignment and EUR 1,000 sign-up fee continue. The fee for legacy holders with a direct agreement is identical to the annual fee per LIR account for that year, with no sign-up fee in the specified legacy scenarios.
These details are not merely bookkeeping. They reveal how the compulsory relationship around the registry is financed. A flat per-LIR fee is administratively simple and avoids converting every IPv4 holding into a direct resource tax. It also means that very different operators face the same base annual contribution. For a large Western European incumbent, EUR 1,800 may be negligible; for a smaller operator facing currency pressure, war exposure or banking friction, it may matter. The fee's legitimacy therefore depends on scope: what exactly is the compulsory contribution buying?
RIPE NCC's own What We Do page shows a broad institution. Member services include registration, transfers, LIR Portal maintenance and RPKI. Community services include the RIPE Database, K-root, DNS services, RIPE Atlas, RIPEstat, RIS, RIPE IPmap, reports, outreach, meetings and learning. Many of these services are valuable; some are genuine public goods. The economic question is whether the compulsory member relationship tied to number-resource recognition should finance all of them as one bundle, and whether members can discipline that scope effectively.
Market-side critiques of registry power often focus on this bundling. The narrow ledger function is easy to defend: accurate registration, transfer recording, reverse DNS, RPKI, database publication, abuse-contact quality, security and continuity. A broader institutional ecosystem may also be useful, but usefulness is not the same as necessity. When a registry charges a semi-captive base for both essential ledger functions and broader community ambitions, the distinction between ledger and institution blurs.
This is where registry self-interest intersects transfer-market architecture. A registry with reliable fee income and control over recognition has an incentive, even without bad faith, to define its mission broadly. Staff and board members may sincerely believe that more measurement, training, outreach and community infrastructure strengthen the Internet. They may be right. But in institutional economics, sincerity does not remove the agency problem. The same institution that approves transfers, checks sanctions, provides RPKI and maintains the record also benefits from being indispensable across a wider range of services.
A scarcity-aware registry should therefore practice scope discipline. It should identify the minimum ledger functions funded by compulsory fees, show their cost separately from discretionary community, training, measurement or outreach work, justify cross-subsidy where a wider public good is truly tied to registry reliability, and let members see how fee decisions affect small operators, legacy holders, sponsoring LIRs, End Users and resource-market participants. Fee votes should be treated as governance of a critical record, not routine association administration.
Transfers are said to be free of charge, and administratively they are. But if the compulsory annual relationship grows because the institution around the ledger grows, transfer participants still bear registry-layer costs: membership fees, documentation time, counsel, policy monitoring, broker reliance and uncertainty. A non-profit gate can still be a gate. The legitimacy of RIPE NCC's gate depends on whether institutional self-interest is constrained by transparency, member discipline and a narrow view of what the ledger actually requires.
Reliability is the product the market buys
After exhaustion, RIPE NCC's core market value is reliability. New IPv4 allocation is no longer the main product. The product is a public reference layer that buyers, sellers, lessors, operators, customers and security systems can trust: the RIPE Database, transfer recognition, reverse DNS, RPKI, LIR Portal services, legacy updates, due diligence, sanctions process, policy implementation and service continuity.
RPKI shows why reliability has become economic. RIPE NCC's RPKI materials say the service allows LIRs to request a digital certificate listing the Internet number resources they hold, and offers verifiable proof that a holder's resources have been registered by an RIR. RPKI supports more informed routing decisions, especially BGP origin validation. Sponsoring LIRs and End Users can request certificates for Provider Independent resources, and legacy holders can request certificates for legacy End User resources. A resource certificate does not make packets flow by itself. But as route-origin validation spreads, the security state attached to a prefix affects operational confidence and therefore economic value.
Transfers must therefore be understood as security-state transitions, not only database updates. A buyer receiving a block needs the old ROAs, route objects, reverse DNS and operational contacts to be handled correctly. A seller must avoid leaving stale security statements. A lessor must manage responsibility. A corporate acquirer must integrate routing and certification. If the public registry record moves but the security-adjacent state remains messy, the buyer receives uncertainty. If the security state changes unexpectedly because of policy, audit, closure or delegated-CA issues, the holder may face operational consequences beyond paperwork.
Assisted Registry Checks point to the same dependency stack. RIPE NCC describes ARC as a constructive process that helps LIRs improve registry data and resource quality. The material covers registry consistency, resource usage, role objects, sponsored resources, routing consistency, RPKI, reverse DNS consistency and network reachability. This is exactly the operational bundle the market cares about. A block's value depends not only on address count but on whether the records around it are clean, current and usable.
The institutional risk is that reliability functions can become leverage functions. If RPKI eligibility depends on a contractual relationship for certain legacy resources, that is understandable; it is also leverage. If audit findings can affect service continuity, that is understandable; it is also leverage. If transfer recognition depends on due diligence, that is essential; it is also leverage. The answer is not to weaken reliability. It is to define reliability powers narrowly and publish how they are used.
A good registry makes honest participation safer than avoidance. Members should feel that correcting records through ARC is cooperative, not existential. Holders should feel that RPKI improves security without turning certification into a discretionary sanction. Transfer parties should feel that database updates, reverse DNS changes and route-object cleanup are predictable parts of settlement. Legacy holders should feel that entering a contractual relationship for services is a clear choice, not hidden coercion. Buyers should feel that the official record reduces diligence cost rather than adding unexplained institutional judgement.
In the transfer-market era, RIPE NCC's most valuable promise is not that it can explain its rules. It often can. The promise must be that the rules operate with enough predictability that the market can rely on them. Reliability is not a support function. It is the thing the market buys with trust.
Ledger versus gatekeeper is the real test
The distinction between ledger and gatekeeper is the article's central test. A ledger records, verifies and publishes a constrained set of facts. It lowers search, bargaining, verification and dispute costs. A gatekeeper controls whether a scarce resource can move, be certified, be serviced, be financed or be made operationally useful. Some gatekeeping is necessary to protect the ledger. The institutional problem begins when protective gatekeeping becomes market governance.
RIPE NCC's current transfer architecture contains both sides. It lowers costs by publishing policy, requiring database reflection, checking authority, recognising inter-RIR pathways, offering legacy update routes, publishing transfer statistics, supporting RPKI and providing due-diligence documentation. It raises costs through the 24-month restriction, sanctions screening, inter-RIR dependence, legacy best-effort uncertainty, incomplete performance transparency and compulsory membership economics. None of these costs automatically makes the architecture illegitimate. Together they define the risk premium around RIPE-region IPv4.
The ledger version of RIPE NCC would say: we verify the source; we verify the recipient category; we check legal authority; we apply sanctions law; we record the transfer; we publish transfer facts; we protect RPKI and reverse DNS continuity; we isolate disputes; we avoid judging business strategy beyond what policy strictly requires. The gatekeeper version would imply something different: we decide whether movement fits our institutional view of stewardship; we keep performance data inside the institution; we let broad mission justify compulsory costs; we use policy vocabulary to restrain market behaviour without measuring the economic effect.
The mature registry challenge is that the difference may not be visible in any single document. Each rule can be justified. A 24-month restriction deters churn. Sanctions checks follow law. Due diligence prevents fraud. Legacy best-effort handling reflects historical complexity. RPKI terms protect relying parties. Published statistics provide transparency. The gatekeeper problem appears when the cumulative result is that the market must price institutional uncertainty as if it were part of the resource.
That is why RIPE NCC should be judged by friction data, not only by policy prose. Does the official transfer path close faster and more predictably than private workarounds? Are common delay causes visible? Are sanctions issues rare, explained and categorised? Are legacy updates easier to price? Are voluntary locks genuine holder protection rather than a source of confusion? Are RPKI changes communicated in a way that protects operational continuity? Can small operators understand transfer requirements without specialist counsel? Are fee debates tied to essential ledger functions rather than institutional identity?
The market does not need RIPE NCC to become a deregulated transaction platform. It needs the registry to be disciplined. Fraud control, legal compliance and accurate records are essential. But the presumption after valid verification should favour recognition and continuity. The registry should not be a moral allocator of post-exhaustion capital. It should be a high-quality public reference layer for scarce identifiers whose value is discovered elsewhere.
What a better transfer architecture would make visible
A better RIPE NCC transfer architecture would not abolish registry control. It would make the control more measurable, narrower and easier to price. The first improvement is transfer performance disclosure. Published approved transfers are useful but insufficient. Aggregate metrics would matter more: median and percentile time to approval by transfer type; document-cycle counts; restriction-related pauses; inter-RIR coordination delays; legacy best-effort outcomes; sanctions categories; abandoned requests; voluntary lock interactions; and post-approval database timing. The data can be anonymised. The market needs performance, not private contract terms.
The second improvement is clearer risk categories. Parties should know whether a problem is source authority, recipient category, 24-month restriction, sanctions, legacy holdership, missing contract, sponsoring LIR issue, RPKI continuity, reverse DNS cleanup, other-RIR approval or ordinary incomplete documentation. Category clarity lowers fear and disciplines the registry because broad discretion is harder to hide when every delay must be named.
The third improvement is legacy-resource clarity. RIPE NCC should keep respecting the distinct nature of legacy resources, but best-effort handling should be surrounded by practical guidance. What evidence usually establishes a legitimate holder? How does the process differ for a legacy holder without a contract, a holder using a sponsoring LIR and a holder with a direct agreement? What happens to RPKI eligibility after receipt? How often do cases fail because evidence is unclear? Legacy resources are a meaningful source of potential supply; ambiguity keeps that supply off the market or discounts it.
The fourth improvement is sanctions predictability. RIPE NCC cannot avoid EU legal obligations, but public process notes, pre-submission guidance, aggregate incidence data and mistake-correction channels would help parties separate legal constraint from institutional discretion. In a sanctions-sensitive region, unexplained compliance friction becomes market distrust.
The fifth improvement is policy impact review. A proposal affecting transferability, RPKI, audit obligations, legacy resources or fee structure should include an economic impact note and an after-action review. That would not make RIPE a regulator. It would recognise that policy-list outcomes now affect a scarce asset market.
The sixth improvement is fee scope transparency. The charging scheme should make it easier for members to see the cost of core registry functions apart from wider community and information services. Members may still choose to fund the wider bundle; the legitimacy gain comes from showing that the compulsory ledger relationship is not hiding institutional expansion.
The seventh improvement is a continuity principle. In unresolved disputes, the default should be preserving the last verified operational state where law and security permit. Transfers may need to pause. Conflicting updates may need to be blocked. But running networks, valid RPKI objects, reverse DNS and abuse contacts should not be disrupted casually. A transfer market depends on the belief that registry uncertainty will be isolated, not converted into customer harm.
None of these improvements requires rejecting the RIPE model. They require accepting what scarcity has changed. The registry is no longer only allocating a resource from a pool. It is maintaining the reference layer for a market in scarce, operationally embedded resources. The better that layer performs, the more valuable RIPE-region resources become. The more discretionary it feels, the more capital will route around it.
Watchpoints for the next 12 to 24 months
The first watchpoint is transfer friction. RIPE NCC should be watched for whether it publishes more granular statistics around intra-region transfers, inter-RIR transfers, legacy updates, 24-month restrictions, sanctions screening and voluntary locks. A registry that can show friction is narrow will strengthen confidence. A registry that publishes only approved transfers leaves the hidden market tax untouched.
The second watchpoint is cross-border compatibility. ARIN, APNIC and LACNIC paths with RIPE NCC remain central to global IPv4 liquidity, while AFRINIC's lack of inter-RIR policy continues to isolate one region from ordinary cross-registry settlement. Any change in compatibility, requirements or performance will affect price and transaction planning far beyond the legal text. The same is true of the M&A path: corporate restructuring will remain one of the main ways address holdings move, and buyers will price registry approval as a special risk if documentation, sanctions screening, post-update restrictions or corporate-history evidence become unpredictable.
The third watchpoint is legacy-resource treatment. Legacy supply can increase liquidity if records are clear. Watch whether RIPE NCC improves guidance around legitimate holder evidence, contractual choices, RPKI eligibility and best-effort timelines. Legacy ambiguity is not an antique problem; it is a market-supply problem.
The fourth watchpoint is RPKI governance. The 2025-02 delegated-CA implementation shows that policy can affect certification status. Watch the notice process, 90-day non-functional threshold, revocation handling, restoration path and public metrics. RPKI strengthens title-like confidence when it is technical and predictable. It becomes gatekeeper risk if certification changes are poorly explained.
The final watchpoint is institutional language and cost discipline. Open mailing lists remain vital, but proposals affecting transferability, resource status, audits, RPKI or fees should include economic impact notes and post-implementation measurement. The 2026 annual LIR contribution remains EUR 1,800, but the deeper question is whether compulsory fees are visibly tied to essential ledger functions or to a broader institutional bundle. If RIPE NCC responds to market pressure mainly with stewardship, community and stability language, critics will hear gatekeeper ambition. If it responds with metrics, narrow legal explanations, continuity commitments and cost separation, the market will hear a ledger.
Conclusion: certainty is the scarce service
RIPE NCC is a test case because it is stable enough for subtle power to matter. A failing registry creates obvious risk. A mature registry creates a more important question: whether ordinary rules around transfers, restrictions, sanctions, legacy resources, RPKI, fees and policy lists lower the cost of using scarce IPv4 resources or add an institutional risk premium to them.
The evidence is concrete. RIPE NCC exhausted its available IPv4 pool in November 2019 and acknowledges that networks use transfers and CGNAT to mitigate scarcity. Its transfer policy permits movement within the region and across compatible RIR borders, but scarce resources face a 24-month restriction after receipt; inter-RIR transfers require two-registry approval; M&A updates require documentation and sanctions checks; legacy resources can retain legacy status but are handled through a more ambiguous best-effort path; RPKI and registry-quality services make registration more than a contact record; and the 2026 charging scheme funds a broad membership association through compulsory annual contributions tied to LIR accounts.
Those facts do not prove that RIPE NCC is abusing its role. They prove that transfer market architecture is now one of the central ways the registry exercises economically significant power. The right standard is not whether RIPE NCC can cite a policy for each action. It usually can. The right standard is whether legitimate parties can understand, price and rely on the official path without disproportionate uncertainty.
The market does not need a theatrical registry. It needs a boring one: accurate records, narrow verification, predictable transfer settlement, transparent restrictions, measurable process, clean RPKI and reverse DNS continuity, fair legacy handling, clear sanctions compliance and fees tied visibly to necessary functions. Boring is the highest form of legitimacy for a private membership institution whose record supports scarce digital infrastructure.
If RIPE NCC keeps the ledger narrow and the gate measurable, RIPE-region IPv4 resources should carry a confidence premium. If it lets institutional self-interest, opaque friction or unmeasured policy controls accumulate, the market will discount the registry layer and build around it. The economics of transfer market architecture therefore points to a conservative conclusion: protect the ledger, restrain the gatekeeper, and treat certainty as the scarce service RIPE NCC is paid to provide.