Inter-RIR transfers sound like a narrow administrative topic. They are not. They are where the Internet's regional registry model meets the global market for scarce IPv4 capital. Packets move globally. Companies sell services globally. Address demand appears wherever customers, cloud deployments, broadband networks, hosting platforms, security products and digital businesses need usable space. Yet the recognised records for those addresses remain inside regional institutions. When IPv4 was abundant, that arrangement looked like sensible decentralised administration. After exhaustion, regional rulebooks became checkpoints for global asset mobility.
RIPE NCC is a useful test because it sits at the centre of several tensions at once. It is a Dutch not-for-profit membership association serving Europe, the Middle East and parts of Central Asia. It operates in a region with sophisticated capital markets, small access providers, conflict-exposed networks, sanctions-sensitive jurisdictions, legacy holdings, multinational carriers, cloud demand and active IPv4 trading. Its public culture is open, policy-driven and technically literate. Its legal documents describe membership, services, transfers, registration, RPKI, reverse DNS and closure. None of that removes the economic fact that a cross-registry transfer is now a capital-mobility event.
The official inter-RIR transfer page supplies the factual core. RIPE NCC says resources can be transferred between its service region and another Regional Internet Registry region, subject to each registry's policy framework, and that an inter-RIR transfer must first be approved by both RIPE NCC and the other RIR. Resources remain subject to the policies of the source registry until the transfer is complete; after completion they are subject to the recipient registry's policies. The page describes pathways with ARIN, APNIC and LACNIC, while noting that AFRINIC currently lacks an inter-RIR transfer policy, so resources cannot move to or from that region through such a route. These statements are procedural facts. Their economic meaning is larger: registry geography has become part of asset quality.
The politics of inter-RIR transfer are therefore not mainly ideological. They are market design. Compatibility rules decide whether an address block can move from one legal, policy and operational environment to another. Waiting periods decide when it can move. Provenance rules decide what history must be trusted. Documentation rules decide who can bear transaction costs. Compliance checks decide which parties are commercially acceptable. Operational services such as RPKI and reverse DNS decide whether transfer settlement is clean or risky. A regional registry may think it is applying community policy. A market participant sees a settlement layer.
This distinction matters because IPv4 scarcity has already turned past allocation into productive capital. A /16, a /19 or even a clean /24 can support revenue, customer continuity, reputation, routing reachability and strategic optionality. It can be sold, leased, contributed to a merger or kept as a hedge against migration risk. The registry does not create all of that value. Scarcity, users and networks do. But the registry record helps the value become recognisable and transferable. Once that is true, inter-RIR transfer policy becomes an instrument of capital mobility.
The right question for RIPE NCC is not whether cross-registry transfers should be unregulated. They cannot be. A global market without reliable provenance, fraud checks, authority validation, legal screening, RPKI continuity and destination-recognition rules would be a market in uncertainty. The right question is whether the registry system acts as neutral ledger interoperability or political gatekeeping. The first reduces friction while preserving trust. The second turns regional stewardship into a barrier to the movement of productive capital.
Regional stewardship meets global demand
The RIR system was built around regional responsibility. That made sense when addresses were allocated according to need within a service region and when the main institutional problem was unique distribution from a remaining pool. Regional communities could develop policies reflecting local conditions. Registries could know their members, operate in particular languages and legal environments, and coordinate with networks that used resources in that region. The model was imperfect, but it matched the allocation era better than a single global office would have.
IPv4 exhaustion changed the premise. RIPE NCC exhausted its remaining IPv4 pool in November 2019. Since then, the region's official path for new address demand has been narrow: an eligible Local Internet Registry may join a waiting list for a single /24 from recovered space. Earlier final-/8 policy allowed one /22 per LIR, but that era is over. Serious incremental demand is met through transfers, leasing, corporate transactions, renumbering, address sharing, carrier-grade NAT, IPv6 migration or some mixture of those measures.
Demand is global, but the rules remain regional. A data-centre business in one region may want space held in another. A European network may acquire a business in North America or Asia. A cloud platform may rationalise address holdings across subsidiaries. A legacy holder may wish to sell to the highest bidder, regardless of region. A broker may maintain a buyer list that does not match RIR boundaries. A network in a region without an inter-RIR path may find that its address capital is effectively trapped even if there is foreign demand.
This is where stewardship becomes political. A regional registry can argue that addresses originally distributed through its community should remain aligned with that community's needs. It can also argue that once a resource is scarce and transferable, blocking mobility preserves local scarcity at the expense of global efficiency. Both claims can be made in good faith. The first emphasises regional responsibility; the second emphasises productive reallocation. Inter-RIR policy is the arena in which the claims collide.
The collision affects price. If a block can move from the RIPE NCC region to ARIN, APNIC or LACNIC through a predictable process, it is more liquid than a block trapped behind an incompatible policy environment. If a block cannot move to or from AFRINIC through an inter-RIR transfer route because no compatible policy exists there, its economic universe is narrower. If a block is subject to a 24-month restriction, its liquidity is delayed. If corporate authority or legacy documentation may complicate a transfer, its market value changes again. The number of addresses is the same; the mobility rights are not.
In ordinary commodity markets, transportation cost shapes price. In securities markets, clearing and settlement rules shape liquidity. In real estate, local title systems shape capital value. IPv4 now has analogous frictions. The physical address is just a number. The economic address is a number plus recognised provenance, transferability, routing reputation, RPKI status, reverse-DNS manageability, legal continuity and policy mobility. Regional rulebooks are part of the asset.
Compatibility is the market design
The word compatibility can make inter-RIR transfers sound technical and benign. It is neither purely technical nor automatically benign. Compatibility is a policy choice about mutual recognition. A source registry must be willing to let a resource leave. A destination registry must be willing to recognise the incoming holder. Each registry may ask whether its own community's rules are satisfied. Each may apply different views of need, eligibility, holding periods, legacy status, documentation, anti-abuse obligations or post-transfer restrictions. The transfer succeeds only if both sides' rules can be satisfied.
Dual approval is defensible. Without it, a source registry could be forced to remove a record that the destination registry refuses to recognise. Or a destination registry could be asked to accept a resource with unclear authority, bad provenance or an unresolved dispute. Dual approval prevents duplicate claims and reduces fraud. It ensures that the block has one recognised home at the end of settlement. In a world where routing depends on shared trust, that matters.
Dual approval is also a two-key veto. A transaction can fail because the seller lacks standing under the source registry's rules, because the buyer fails destination requirements, because the resource is still under a waiting period, because documentation is incomplete, because one registry's interpretation of legacy status differs from another's, because legal concerns arise, or because a policy gap between regions makes the path unavailable. The market experiences all of these as settlement risk.
Settlement risk has a price. Buyers discount uncertain closings. Sellers prefer counterparties with smoother paths. Brokers build businesses around knowing which combinations of region, status and buyer profile are likely to pass. Legal counsel writes representations and conditions around registry approval. Escrow providers hold funds until the registry record changes. Operators delay network plans while a block waits for recognition. In the IPv4 market, compatibility is not a background condition. It is the infrastructure of liquidity.
The policy issue is not whether RIPE NCC should approve every cross-registry transfer. It should not. The issue is whether compatibility rules are narrow enough to protect ledger integrity without becoming disguised regional control. A good compatibility rule asks whether the resource can be reliably identified, whether the current holder can authorise the transfer, whether the recipient can be recognised under the destination registry's rules, whether fraud and duplicate claims can be prevented, and whether operational services can transition without confusion. A bad compatibility rule uses procedural differences to protect incumbents, preserve local supply, punish unfavoured jurisdictions or impose moral preferences unrelated to registry accuracy.
The difference can be subtle. A requirement for current corporate documentation may be a fraud control. The same requirement, applied without flexibility to a disrupted jurisdiction or a legacy record, may become a barrier. A waiting period may deter speculation. The same waiting period, applied rigidly after a bona fide corporate rescue, may trap capital. A destination eligibility rule may preserve local policy coherence. The same rule, if used to reject otherwise clean global demand, may reduce efficient allocation. Market design lives in these margins.
RIPE NCC's institutional challenge is to show which side of the line its practice occupies. The public documents state the process. They do not by themselves reveal the market cost of the process. For that, members and market participants need aggregate data: how many inter-RIR requests were approved, rejected, withdrawn, delayed by documentation, delayed by another registry, blocked by waiting periods, affected by legal review, or unable to proceed because no compatible regional path existed. Completed-transfer lists are useful. They do not show the failed or abandoned side of the market.
Reciprocity, or the politics of mutual recognition
Inter-RIR transfers depend on reciprocity, but reciprocity can mean different things. At its narrowest, it means that both registries have policies permitting transfers and enough procedural alignment to prevent broken settlement. At its broadest, it becomes a political test: does the other region share our values, our conservation instincts, our needs standard, our treatment of legacy resources, our view of speculation and our appetite for market liquidity?
The narrow version is necessary. The broad version is dangerous. No global market can function if every regional institution uses compatibility to export its entire political economy. A registry that insists on perfect policy symmetry is not building interoperability. It is using regional difference as a barrier. The Internet's address layer cannot afford that kind of purity after exhaustion.
The absence of an inter-RIR route with AFRINIC illustrates the cost. The factual point is simple: RIPE NCC says AFRINIC currently has no inter-RIR policy, so transfers to or from that region through the inter-RIR path are not possible. The economic effect is not simple. It means address capital registered in the AFRINIC environment is less globally mobile than address capital in regions with recognised transfer pathways. Buyers may discount it. Sellers may have fewer exits. Operators may seek alternative corporate structures, leasing arrangements or routing arrangements. Disputes inside one regional registry can affect global capital allocation.
This does not prove that AFRINIC should adopt any specific rule, nor that RIPE NCC should ignore counterpart policy. It shows that compatibility is a market good. When a region lacks it, the cost is borne by holders, buyers, lessees and networks that cannot move resources through a clean ledger path. The burden may be especially heavy for small operators who cannot create complex structures around the restriction.
Reciprocity also affects bargaining between regions. If one registry has a stricter recipient-eligibility rule, another registry may need to accommodate it for outbound transfers. If one applies a holding period, the other must recognise that the source block is not yet movable. If one has stronger legal exposure, transactions involving that region may face additional checks. Each RIR's internal politics therefore spills outward. Regional autonomy becomes a global externality.
RIPE NCC's role should be to make those externalities visible. It cannot force another registry to create an inter-RIR policy. It can, however, publish clearer information about paths that are unavailable, reasons for delay, categories of incompatibility and the practical consequences for members. It can avoid presenting inter-RIR friction as mere administrative variation. In a scarce market, variation is capital cost.
Waiting periods and anti-arbitrage politics
RIPE NCC's transfer policies include a 24-month restriction on scarce resources such as IPv4 and 16-bit ASNs after receipt through allocation, transfer or certain changes in business structure. The rule is often understood as an anti-speculation mechanism. In inter-RIR terms, it is also an anti-arbitrage mechanism. It slows the ability of a holder to buy or receive resources in one context and quickly move them to another where demand or pricing may be stronger.
Anti-arbitrage rules can be justified when they protect a rationing system from manipulation. If a region still has recovered addresses distributed through a waiting list, it has reason to prevent immediate conversion of that residual allocation into private profit. If a transfer market attracts purely financial churn, a waiting period may reduce noise and preserve confidence. If mergers are used as a pretext for disguised transfers, a restriction may deter abuse.
Yet waiting periods are blunt tools. They apply time as a proxy for intent. A legitimate operator can be trapped along with a speculator. A company that acquires a network and then needs to reorganise its address holdings may face immobility. A distressed small holder may be unable to sell into a better market. A buyer may discount addresses because future exit options are constrained. A leasing arrangement may become more attractive than a sale even when a sale would be cleaner. The rule may reduce one type of arbitrage while encouraging another.
In inter-RIR transfers, the bluntness is larger because regional price differences may reflect real differences in demand, documentation, legal certainty and operational need. Arbitrage is not always parasitic. Sometimes it moves a scarce input from a lower-value use to a higher-value use. A market that forbids all fast reallocation may preserve an old distribution pattern at the cost of current productivity. Scarcity makes that cost visible.
RIPE NCC therefore needs to treat waiting periods as liquidity policy, not only anti-abuse policy. The institution should be able to explain how often the rule affects cross-region transfers, how often exceptions or merger-specific treatments arise, how many requests are delayed rather than denied, and whether the rule's anti-speculation benefits outweigh its deadweight cost. This does not require revealing private contracts. It requires aggregate market evidence.
The politics of waiting periods also reveal a deeper unease. Many RIR communities are uncomfortable admitting that IPv4 addresses behave like tradeable capital. The discomfort is understandable. The address system was not designed as a financial market. But denial is not governance. If a rule restricts transferability, it is shaping capital mobility whether or not official language says so. Better to analyse the effect openly than to let liquidity rules hide behind conservation rhetoric.
Provenance is useful until it becomes a border
Every serious IPv4 buyer cares about provenance. Was the resource legitimately allocated? Is the current holder recorded accurately? Are there disputes? Are there stale maintainer objects? Has the block been hijacked? Does it carry abuse reputation? Has it moved through mergers, bankruptcy, legacy claims or previous transfers? Can the seller sign? Are there route objects, ROAs and reverse-DNS delegations that need to be changed? Provenance is not bureaucracy. It is the information that separates a clean asset from a lawsuit, routing problem or reputation sink.
Inter-RIR transfers intensify provenance questions because the resource is moving between record systems, legal environments and policy histories. The source registry must trust the current holder's authority. The destination registry must trust that the incoming record can be incorporated without duplicating claims or importing unresolved disputes. Both must ensure that the handoff does not create a period in which the market is unsure who controls the block.
RIPE NCC's transfer policy states that transfers must be reflected in the RIPE Database and that the original holder remains responsible until completion. That is a sound settlement principle. Responsibility remains anchored until the recognised record changes. But it also means the transfer interval is a risk interval. If a buyer has paid but the registry update is delayed, the buyer lacks the recognised record. If a seller has agreed to transfer but remains recorded, the seller may still carry responsibility. Escrow and contracts manage the gap, but they do not erase it.
Provenance becomes political when it is used not only to verify authority but to judge whether a resource should be allowed to leave a region. A registry should care whether the chain of control is real. It should be cautious about using the historical origin of a block as a reason to restrict legitimate mobility. If a university, carrier or legacy company received space decades ago and no longer needs all of it, the question should be whether the current holder can lawfully transfer it, not whether the block's original allocation story fits today's regional sentiment.
The line is important for legacy resources. Historical records may be incomplete, names may have changed, companies may have merged or dissolved, and early allocation practices may not match modern documentation expectations. In inter-RIR transfers, a weak record can become a cross-border obstacle. Some obstacles are legitimate; fraud loves old paperwork. But provenance review should be an evidentiary process, not a nostalgia test. The market needs clarity on what documents cure uncertainty, what records are fatal, and how disputes are marked without destroying unrelated value.
Provenance also contains operational history. A block with clean ROAs, accurate abuse contacts, coherent route objects and maintained reverse DNS is easier to move than a block whose operational state is stale. The transfer of a scarce resource is therefore not only a legal event. It is a handoff of accountability. The registry should help that handoff by defining what must be clean before settlement and what can be corrected after settlement. A vague demand for "clean records" gives discretion too much room. A defined checklist lowers transaction cost.
The community process and absent markets
RIR policy is often described as community-developed. That is partly true and institutionally important. It is also incomplete. A policy mailing list is not the same as a market referendum. The people who participate in policy discussions are usually those with time, expertise, institutional memory and an appetite for public argument. The parties affected by inter-RIR mobility include many others: small holders, buyers in other regions, lessees, merger advisers, creditors, customers, hosting platforms and operators who will discover the rule only when a transaction is urgent.
Inter-RIR transfers make this representational gap wider because one region's policy affects outsiders. A RIPE NCC policy discussion can influence whether a buyer in another RIR region can obtain space from a RIPE-region holder. A counterpart registry's policy can influence whether a RIPE NCC member can buy or sell across the boundary. The affected market is larger than the speaking community. Formal openness is valuable, but it does not solve participation asymmetry.
This matters because compatibility debates can sound technical while embedding distributional choices. A policy that preserves a waiting period may be framed as anti-speculation. It may also reduce exit options for small sellers. A rule that requires particular documentation may be framed as integrity. It may also burden legacy holders and cross-border firms. A destination-recognition rule may be framed as local policy coherence. It may also exclude global demand. If the affected outsiders are absent from the list, consensus can be real inside the process and thin in the economy.
The remedy is not to abandon community policy. A closed staff model would be worse. The remedy is to add economic translation. Proposals affecting inter-RIR transfers should identify the expected effect on liquidity, small-operator access, legacy holders, counterpart registry compatibility, transaction cost and operational settlement. Chairs should treat silence as weak evidence where the affected parties are likely outside the room. RIPE NCC impact analysis should separate implementation cost from market cost. Post-implementation review should examine actual delays, refusals and workarounds.
This would help the board as well. Board accountability in a post-exhaustion registry is not only about staff efficiency and fee levels. It is about the institution's risk posture toward scarce address capital. If inter-RIR mobility is slow, opaque or politically contested, members should know whether the board sees that as a policy success, a necessary cost, or a problem to reduce. If the association's fees, legal exposure, transfer-team capacity or RPKI services influence cross-region transactions, the board should treat that as market infrastructure, not routine administration.
Legitimacy fails when an institution points to a process that affected parties could formally use but practically could not influence. It succeeds when the institution recognises the limits of its own process and compensates with evidence, transparency and narrow discretion.
Transaction costs decide who can use the market
In theory, a transfer market allocates scarce IPv4 to the users who value it most. In practice, transfer markets allocate to the users who can value it, document it, finance it, wait for it and survive the risk that it does not close. Inter-RIR transfers raise every one of those requirements.
A cross-region transaction may require corporate records from multiple jurisdictions, authority documents, board approvals, proof of current registration, evidence of resource holdership, policy eligibility checks, legal review, buyer qualification, destination membership arrangements, escrow terms, technical planning, RPKI changes, reverse-DNS updates, route-object cleanup and communication with two registries. Each item has a reason. Together they form a fixed cost.
Fixed costs advantage scale. A large cloud platform, telecom group or specialised broker can absorb them. A small ISP selling a modest block cannot. A regional hoster buying enough space to serve a customer base may struggle with the legal and procedural overhead. A legacy holder with old records may need specialist help. A firm in a politically exposed jurisdiction may face additional banking and documentation cost. If the transaction is large, these costs may be tolerable. If the transaction is small, they can kill the deal.
This is how policy friction becomes market structure. A registry does not need to favour incumbents intentionally. It can do so by making the official path expensive to navigate. The market then shifts toward actors who can aggregate, intermediate or absorb complexity. Brokers may become more important. Leasing may expand because it avoids permanent transfer. Address holdings may concentrate in firms with legal capacity. Small holders may sell at a discount to intermediaries rather than directly to end users. Small buyers may lease from larger portfolios rather than acquire. The official policy may look neutral while the market outcome becomes less diverse.
RIPE NCC can reduce this effect by publishing better process data and clearer guides, but it can also use design. Standardised document checklists by transaction type, pre-submission review for authority evidence, clearer timelines after complete submission, distinction between ordinary deficiencies and serious disputes, and coordinated handoff guidance with counterpart RIRs would lower fixed costs. So would aggregate reporting on why requests fail or pause. If brokers compete on commercial service rather than privileged process knowledge, the market becomes healthier.
The aim is not to remove all professional intermediation. IPv4 transactions can be complex, and good brokers or counsel can add value. The aim is to prevent the registry process itself from becoming a rent-generating maze. A neutral ledger should be readable without an insider.
Operational settlement matters as much as legal recognition
An inter-RIR transfer is not finished simply because two institutions approve a record change. The address block must continue to work. Routing objects, RPKI certificates, ROAs, reverse-DNS delegations, abuse contacts, geolocation records, customer allowlists and internal network documentation may need to change. Some of those items are under registry control, some under holder control, and some under third-party systems that react slowly or imperfectly.
RIPE NCC's RPKI service illustrates the point. RIPE NCC allows eligible holders to request resource certificates that list the number resources they hold. Those certificates support route-origin authorisations and BGP origin validation. When a resource moves between registries, the trust path and certificate arrangements may also need to move. If the transition is poorly timed, a buyer may face route-validation uncertainty. If ROAs are missing or wrong, routes may be treated differently by networks that filter on validation state. The block's economic value depends on avoiding that confusion.
Reverse DNS is similar. RIPE NCC registers reverse delegations and uses the RIPE Database as the management database for producing reverse-DNS zones. When a resource moves to another region, reverse-delegation responsibility may shift. Mail deliverability, logging, anti-abuse systems and customer integrations can be affected by errors or delays. These details may not dominate the purchase contract, but they influence the operational cost of settlement.
The public registry record also matters for reputation. Abuse desks, peering coordinators, security teams and automated tools use registry data to understand who is responsible for a block. If an inter-RIR transfer creates a period of inconsistent records, stale contacts or unclear maintainers, the buyer inherits a trust problem. If the old holder remains visible after the economic transaction, the seller may carry unwanted responsibility. If the destination registry updates cleanly but third-party systems lag, customers may still see friction.
The registry's duty is not to manage every downstream database. It is to make the authoritative handoff as precise and predictable as possible. The source record should remain stable until settlement. The destination record should appear with clear timing. RPKI guidance should tell holders how to avoid invalid or stale ROAs. Reverse-DNS guidance should identify when delegation changes and what the holder must do. Transfer completion should be unambiguous enough for escrow, technical teams and counterparties to rely on it.
Operational settlement is where ledger interoperability proves itself. A system that lets legal recognition change while routing security or reverse DNS breaks is not a high-quality market design. A system that preserves service through the transition and explains responsibilities reduces the capital cost of moving across regions.
Legal geography without importing every legal argument
Inter-RIR transfers do not escape legal geography. RIPE NCC operates under Dutch law and screens transfer and merger requests against applicable lists and legal constraints. A cross-registry transfer can therefore be blocked or delayed by legal constraints that enter through RIPE NCC even when the destination market is elsewhere. The counterpart registry may have its own legal exposure. A buyer, seller, bank or broker may add further restrictions. The transaction becomes a meeting point of registry policy and public-law risk.
This does not mean RIPE NCC should ignore sanctions, court orders or corporate disputes. It cannot. It does mean that legal constraints should be separated from policy discretion. A denial because a party is legally prohibited is different from a delay because documents are incomplete. A delay because another registry must approve is different from a refusal because a waiting period applies. A compliance review is different from a provenance dispute. Markets need to know these categories because each carries a different risk premium.
If all problems are communicated as undifferentiated policy or compliance concerns, the result is broad uncertainty. Buyers may avoid entire paths. Sellers may accept lower prices. Brokers may demand more control. Small operators may never attempt cross-region transactions. Legal caution then becomes a de facto mobility tax even when the law does not require broad exclusion.
The court dimension is similar. A resource may be involved in a corporate dispute, insolvency, injunction or court order. A registry may need to freeze, refuse or modify a record because a competent authority requires it. But the existence of litigation should not automatically convert a resource into dead capital. The better model is preservation of the last verified state unless a specific order or verified authority change requires action. That principle protects the ledger from being used as a pressure point in commercial disputes.
Inter-RIR politics are especially sensitive here because a dispute in one venue may affect a transaction in another. A block registered in one region may be sold to a buyer in another. A court in the source region, the destination region or a corporate domicile may claim relevance. If registries lack clear principles for conflict, the market will price the worst case. RIPE NCC can reduce that price by publishing how it treats legal holds, court orders, disputed authority and cross-border conflicts in transfer contexts, without disclosing private cases.
Recognition politics become dangerous when legal caution merges with regional preference. A transfer delayed by binding law is one thing. A transfer delayed because a buyer's geography is unfavoured, a block's origin is seen as morally inconvenient, or a region's address stock is being protected through rhetoric is another. The more pressure registries face from governments and public opinion, the more they need narrow written categories.
Inter-RIR transfers as an exit function
Inter-RIR transfers are often described as a service for moving resources where they are used. They are also an exit function. They allow a resource holder, under defined conditions, to move address capital out of one registry's rulebook and into another. That possibility matters even when few members use it.
Exit is one of the disciplines missing from monopoly infrastructure. A member dissatisfied with RIPE NCC's fees, procedures, policy culture or legal environment cannot simply choose another registry for existing RIPE-region resources in the way a customer can choose another software vendor. An inter-RIR transfer is not a general right of exit: it requires a transaction, a recipient, compatible policies and approval by both registries. But where it exists, it creates some discipline. If one registry becomes too costly, too slow or too uncertain, capital has a route out through sale or corporate movement.
This is why regional registries may be ambivalent about mobility. Inter-RIR transferability helps address capital find users and gives holders liquidity. It can also reduce the captive nature of the membership base. A region that permits outbound transfers may lose address stock and fee relationships. A region that restricts them may preserve stock but reduce asset value and market confidence. The policy choice has institutional self-interest embedded in it.
RIPE NCC should be explicit about that tension. A not-for-profit association may not seek profit from captivity, but it does depend on membership fees and regional relevance. Its charging scheme, service model, transfer policies and governance legitimacy all interact with the ability of holders to leave. If exit is too constrained, fees and procedures face less market discipline. If exit is too loose without accountability, the region can become a transit point for speculative movement or laundering of weak provenance. The answer is not to deny the tension. It is to design exit as transparent portability with accountability preserved.
The exit function also matters for small operators. A large holder can sometimes use corporate restructuring, mergers or multi-region affiliates to manage registry exposure. A small holder may have only a clean sale. If inter-RIR mobility is expensive or uncertain, the small holder's bargaining power falls. The registry may never intend this result, but the market will feel it.
Brokers, escrow and the private price of opacity
Where public transfer systems are hard to read, private intermediaries become more valuable. That is not automatically a problem. Brokers can find counterparties, check address reputation, structure escrow, coordinate paperwork and help parties understand market price. Good intermediaries reduce search costs in a fragmented market. They can be especially helpful where a seller has never transferred address space before or where a buyer lacks experience with cross-registry settlement.
But intermediation can also become a symptom of institutional opacity. If the main value of a broker is not market matching but knowledge of how to navigate registry uncertainty, the public system is transferring rents to private expertise. A large buyer can hire that expertise. A small holder may sell at a discount to a broker because direct sale feels too risky. A foreign buyer may avoid direct negotiation with a RIPE-region seller because the registry path is unclear. The address still moves, but the surplus is redistributed toward those who understand the institutional maze.
Escrow has a similar double role. It is a prudent commercial tool because payment and registry recognition do not occur at exactly the same moment. A seller wants assurance that funds exist. A buyer wants assurance that the registry record will change. Escrow can align those interests. Yet heavy dependence on escrow also reveals that the public settlement layer is not immediate enough to stand alone. Every extra uncertainty about policy compatibility, documentation, waiting periods, legal screening or operational handoff increases the complexity of escrow conditions and raises legal cost.
This private cost is rarely visible in registry statistics. A completed inter-RIR transfer may appear as a successful record change, while the parties paid significant legal, brokerage and escrow fees to make it happen. Another transaction may never appear because the expected private cost exceeded the value of the block. A small holder may lease rather than sell because a lease can be arranged faster than a permanent cross-region transfer. A buyer may buy a less suitable block in another region because the path is clearer. None of this necessarily shows up in official transfer counts.
Opacity also affects price discovery. IPv4 prices are already uneven because blocks differ by size, reputation, route history, fragmentation, buyer urgency and contract terms. Inter-RIR uncertainty adds a regional-policy discount. A block that should command a higher price because it is clean and contiguous may still trade lower if buyers fear that moving it will be slow. Conversely, a block in a smoother policy path may command a premium even if its technical quality is similar. The market is not just pricing addresses; it is pricing confidence in registry recognition.
RIPE NCC cannot and should not eliminate private intermediation. It can reduce the share of intermediary value that comes from public opacity. Clearer guidance, standardised evidence expectations, published timing ranges, named categories of delay, and better coordination with counterpart registries would push brokers back toward genuine market functions: finding buyers, assessing reputation and negotiating commercial terms. That would help small operators most. They would still be able to use brokers, but they would not have to treat them as translators of an obscure public process.
Data that would make the market less political
Inter-RIR transfer politics are worsened by poor visibility. Participants see completed transfers, anecdotes, broker commentary, list debates and occasional institutional explanations. They often do not see the denominator: how many requests began, how many were paused, how many were withdrawn, how many failed documentation, how many were blocked by counterpart registry rules, how many were affected by waiting periods, how many involved legacy-resource uncertainty, and how long each category took.
RIPE NCC does not need to publish private contracts, prices, names or sensitive legal details to improve this. It could publish a periodic transfer-performance report with broad categories. For inter-RIR cases, the useful data would include requests opened, approved, withdrawn and refused by counterpart registry and resource type; median and distribution of time from complete submission to decision; categories of delay, including documentation, waiting period, counterpart registry approval, legal review, legacy authority, dispute and technical transition; the number of cases where a transfer path was unavailable because the counterpart region lacked compatible policy; and aggregate post-transfer operational issues involving RPKI, reverse DNS or database authority.
Such data would not weaken the registry. It would discipline speculation. If delays are rare, RIPE NCC can show it. If a particular counterpart path is slow because of the other registry, the market can see it. If waiting periods account for many blocks, the policy community can evaluate the rule. If legacy uncertainty is a major source of delay, holders can improve records before transacting. If small transfers face disproportionate fixed costs, policy can respond.
Transparency also reduces political temperature. In the absence of data, every group tells a story that serves its interests. Incumbents may claim transfers are orderly. Brokers may claim the registry is obstructive. Small holders may believe the system is stacked against them. Registries may blame each other. Activists may describe every friction as capture. Aggregate evidence does not end disagreement, but it moves disagreement from suspicion to measurement.
The key is to report process performance, not only policy existence. A rulebook can look compatible on paper and still impose high transaction cost. A transfer system can publish success stories while abandoned deals remain invisible. A ledger institution that wants trust should measure the hidden side of friction.
What neutral interoperability should mean
Neutral interoperability is not the absence of rules. It is a set of rules that make cross-registry movement predictable, narrow, auditable and operationally safe. For RIPE NCC, a neutral inter-RIR posture would have several elements.
Authority verification should be rigorous but proportionate. The registry should confirm that the current holder can transfer the resource and that the recipient can be recognised. It should not use historical allocation narratives or regional sentiment to block otherwise legitimate movement. Legacy and merger cases may need extra work, but the work should be directed at proving the chain of control, not relitigating whether the original allocation would have been made under modern policy.
Policy friction should be identified as friction. Waiting periods, destination eligibility rules, counterpart incompatibility and legal checks may be necessary. They should be described as market-relevant constraints with aggregate performance data. If a rule is designed to reduce speculation, the registry should measure both prevented abuse and legitimate transactions delayed. If a path is unavailable because another registry lacks policy, holders should receive clear guidance rather than vague uncertainty.
Operational transition should be treated as part of the transfer product. RPKI, reverse DNS, database authority and contact data should have clear handoff guidance. The transfer should preserve the last verified state until completion and avoid avoidable gaps. The registry should distinguish legal settlement from operational cleanup, so buyers and sellers know what is complete and what remains their responsibility.
Small-operator access should be a design constraint. If the process is usable only by large firms and specialised brokers, the official market will concentrate. Checklists, timelines, pre-checks, plain-language guidance and staff support lower fixed costs. They also reduce the risk that leasing or informal arrangements become the default for parties who would prefer a clean transfer.
Legal constraints should be separated from policy discretion. Sanctions, court orders and corporate disputes must be handled seriously. But the registry should communicate categories at the highest level allowed by law. A transaction blocked by binding prohibition is different from one delayed by ambiguous documentation. Markets price both poorly when the categories are hidden.
This is not a radical programme. It is the ordinary discipline of a settlement institution. The Internet number registry system did not begin as capital-market infrastructure. IPv4 scarcity pushed it into that role. Neutral interoperability is how it can perform the role without pretending to be a financial exchange or a regulator.
Watchpoints for cross-registry transfer politics
The first watchpoint is the treatment of compatibility as a factual settlement requirement rather than a political veto. RIPE NCC should be expected to approve clean cross-registry movement where authority, policy restrictions, recipient recognition and legal constraints are satisfied. It should be pressed to explain, in aggregate, where counterpart rules or regional incompatibilities block movement. The absence of an AFRINIC inter-RIR path is not merely a footnote; it is a live example of how one region's policy gap affects global asset mobility.
The second watchpoint is the 24-month restriction and its inter-RIR effects. A rule designed to prevent speculation can become a liquidity tax on legitimate holders. The relevant evidence is not only whether the rule exists, but how often it delays or prevents cross-region transactions, how often parties use leasing as a workaround, and whether small operators are hit harder than large holders.
The third watchpoint is provenance. Cleaner records reduce fraud and lower market cost. But provenance review must not become a reason to freeze old resources indefinitely or to enforce regional nostalgia. Legacy holders, merger cases and small operators need practical evidence standards that distinguish a real authority problem from historical paperwork weakness.
The fourth watchpoint is regulatory arbitrage. Movement toward another region is not inherently abuse. It may be market feedback about trust, fees, predictability and legal environment. The registry should prevent evasion of law and fraud, not punish legitimate portability. A healthy RIR system should learn from mobility rather than fear it.
The fifth watchpoint is operational settlement. RPKI, reverse DNS and database authority should move without avoidable service gaps. Inter-RIR transfer politics should be judged not only by whether a record changes, but by whether the address block remains clean, routable, auditable and manageable through the transition.
The final watchpoint is who can afford the official path. If cross-region transfers are predictable only for large operators, brokers and repeat participants, the market will concentrate and small holders will accept discounts or workarounds. A neutral ledger must be legible to the small network as well as the multinational buyer. That is the practical test of whether RIPE NCC's inter-RIR posture is interoperability, or whether regional stewardship has hardened into gatekeeping over global IPv4 capital.