Summary
- RIPE NCC cross-border compliance cost is the cost of converting registry recognition into a bankable closing condition across several legal systems, not a complaint about forms.
- IPv4 run-out in November 2019 made transferability economically central: recognition now affects price, escrow timing, lender comfort, buyer diligence and post-closing network continuity.
- The registry needs evidence for narrow ledger facts: current holder identity, authority to request a change, legal succession, uniqueness, accurate registration and absence of a recognised bar to the requested update.
- Private deal files are wider: beneficial ownership, bank review, FX classification, tax treatment, invoice language, escrow release, legal opinions, translations, route-origin assurance, reputation cleanup and customer warranties.
- RIPE NCC's service region, spanning Europe, the Middle East and parts of Central Asia across more than 75 countries and more than 20,000 LIR organisations, makes the proof bundle unusually plural.
- Sanctions screening and inter-RIR double approval are real checkpoints, but they should remain bounded exhibits, not a licence for a registry to become a broad capital-control institution.
- Fixed compliance costs fall hardest on small holders, edge networks, legacy estates, public bodies and firms in weaker banking corridors because the file can cost nearly the same for a small block as for a large one.
- The right standard is a thin but serious registry: predictable accepted evidence, narrow decision facts, reviewable timing, service-specific continuity and finality once recognition has safely changed.
The closing room is not where the network begins
Start with a cross-border IPv4 transfer file in the RIPE NCC service region. A Dutch hosting group is selling a clean block to a Gulf buyer that needs address capacity for managed enterprise services. A Baltic acquisition has left a parent company with duplicated IPv4 inventory, and the buyer wants part of it moved to a subsidiary in another country. A Central Asian network has merged with a European carrier group and must update the registration record before lenders, customers and transit providers will treat the inherited address plan as stable. The prefixes already route. Engineers can name the intended origin AS, reverse-DNS changes, RPKI state, geolocation requests, abuse-mailbox updates and customer cutover. Nothing in the packet path is waiting for a notary.
The transaction still slows. A lawyer asks whether the company in the registry is the same legal person now signing the sale agreement. The seller sends a chamber-of-commerce extract, but the buyer asks for a current certificate, a beneficial-owner chart and a board resolution. The bank wants the payment described in terms it can understand: not domain names, not software licences, not hardware, but scarce internet-number resources whose recognition is held in a member registry. The escrow provider asks what exactly releases funds: signed contract, RIPE NCC approval, visible database update, reverse-DNS handover, or a later route-origin and reputation-cleanup milestone. A tax adviser asks whether the price is capital gain, ordinary income, intangible-asset proceeds, service capacity or a mixed supply. A public-sector buyer asks whether the seller can prove chain of authority in two languages. A cloud provider asks whether the range will remain usable after the holder changes.
This is the economics of cross-border compliance cost. It is not the cost of bureaucracy in the abstract. It is the cost of turning a recognised registry state into a closing asset that private parties, banks, auditors, tax teams, upstreams, cloud platforms and customers can rely on. RIPE NCC is only one institution in that file, but its act of recognition is the centre around which the rest of the file is organised. If the registry act is predictable, the private file can be thinner. If it is opaque, the private file grows.
The point is sharper in the RIPE NCC region than in a single-country registry model. RIPE NCC is based in the Netherlands, but its service region spans Europe, the Middle East and parts of Central Asia, more than 75 countries and more than 20,000 Local Internet Registry organisations. That range includes highly digitised company registries and paper-heavy systems; euro-zone banks and local banks dependent on fragile correspondent rails; English-language corporate files and records in Arabic, Turkish, Russian, French, German, Dutch, Farsi, Hebrew and many other languages; ordinary private companies, universities, ministries, municipal networks, telecom groups, sanctions-exposed firms, free-zone companies, insolvency estates and small access providers. The shared registry record reduces coordination cost only if the evidence standard for changing it is narrow enough to be understood across that variety.
The thin-registry principle does not mean RIPE NCC should approve every request. Scarce addresses attract fraud, stale claims, opportunistic sellers, confused successors and high-pressure buyers. A registry that cannot verify who may request a change would damage every legitimate holder. The thin-registry principle means something more exacting: the registry should ask for the evidence needed to protect uniqueness, accuracy and continuity, and should stop there. It should not turn transfer recognition into a broad inquiry into whether a transaction is commercially wise, politically convenient, strategically desirable or institutionally comfortable.
That line is easy to state and difficult to hold. Every extra check can be described as caution. Every delay can be defended as diligence. Every unfamiliar legal form can be treated as a reason to ask for another letter. Yet a scarce resource market prices these choices. Delay becomes a capital charge. Uncertainty becomes an escrow condition. Broad discretion becomes a liquidity discount. If the registry acts like a gate, address capital moves only for parties able to afford the gatekeepers around it.
Scarcity turns documents into price
IPv4 exhaustion changed the economic meaning of registry paperwork. RIPE NCC exhausted its remaining free IPv4 pool in November 2019. The fact itself is widely reported by the registry and the community; its importance lies in the market it produced. After run-out, a network needing more than a tiny recovered allocation must look to transfers, mergers, leasing, address sharing, carrier-grade NAT, IPv6 migration or some combination of those strategies. That makes recognition of transfer and legal succession economically central.
Before scarcity, a document defect could often be treated as an administrative inconvenience. A growing network could apply for space, correct a record, or tolerate delay because addresses were still part of a planned allocation regime. After scarcity, the same defect can change price. If a buyer cannot know when a transfer will be reflected in the registry, it may reduce its bid, demand a holdback, refuse to release funds, choose a different seller, lease instead of buy, or postpone customer deployment. If a seller cannot produce historical merger evidence, it may accept a lower price from an intermediary able to carry the file. If a bank cannot classify the payment, a closing date may slip into a new quarter. If a tax team cannot agree on treatment, management may delay approval. If a cloud provider will not import the range until registry and route-origin evidence align, revenue migration may wait.
The price effect is not confined to completed transfers. The market sees the risk before the file is submitted. Brokers ask whether the seller is in a jurisdiction with easy records. Buyers favour holders with clean corporate histories. Lawyers write representations around registry approval. Banks ask for source-of-funds and purpose-of-payment explanations. Escrow providers set outside dates. Small networks decide whether the legal cost is worth the transaction at all. A registry procedure that looks neutral on paper can therefore shape who can use the market.
The same logic applies to mergers and acquisitions. RIPE NCC's merger and acquisition procedures require parties to provide documentation supporting the legal change, such as corporate registration material and evidence that resources should move or be reflected under the successor. That is sensible; a registry cannot accept a press release as proof of succession. But when address space is valuable, the registry update becomes part of the deal economy. A buyer acquiring a network does not merely want routers and customer contracts. It wants confidence that the registry record will follow the deal, that reverse DNS can be maintained, that RPKI certificates will not become unstable, that abuse contacts can be updated, and that customers, banks and auditors will not later discover that the address history is unresolved.
Scarcity also changes the burden of time. A two-week delay can be trivial for a large carrier and painful for a small provider that has promised a customer deployment. A three-month delay can alter a purchase price if market values move. A missed outside date can let a buyer walk. A bank's request for another document can trigger a new sanctions or beneficial-owner review. A company registry extract can expire before a later stage is reached. Every party then asks for fresher evidence, and the file loops.
This is why the phrase "just paperwork" is misleading. The paper is the visible part of a price system. It allocates risk among buyer, seller, bank, registry, escrow provider and downstream network users. It decides whether a scarce resource can move at market value or only through discounts and specialist intermediaries. Once IPv4 is scarce, compliance cost is not outside the market. It is one of the market's main frictions.
The registry cannot abolish that friction. It can, however, decide whether its part of the friction is reducing uncertainty or adding it. A ledger with predictable evidence standards compresses private diligence because parties know what the authoritative institution will need. A ledger with open-ended review expands private diligence because no one knows which concern will matter next. Scarcity rewards precision.
The registry's job is thin, but not empty
A useful registry is neither a rubber stamp nor a regulator of all commercial wisdom. RIPE NCC's value lies in maintaining a common record for internet number resources: who is the recognised holder, which resources are recorded, which parties can update data, how reverse DNS is delegated, how RPKI certificates and route-origin authorisations relate to registered resources, and how changes are reflected without duplicate claims. In transfer and merger files, the registry's strongest duty is to preserve uniqueness, accuracy and continuity.
Uniqueness means a block should not appear to have two recognised holders. Accuracy means the record should match the lawful holder or successor that can maintain responsibility. Continuity means existing users and relying networks should not suffer avoidable instability while a legitimate change is processed. These are serious duties. They justify evidence. They do not justify an unlimited inquiry.
The narrow facts are familiar. Does the current holder exist or have a lawful successor? Is the party requesting the change authorised to bind that holder? Are the resources the same resources described in the agreement or merger file? Is there an unresolved claim that the registry must respect before acting? Are the parties eligible under the relevant policy path? Are fees, service agreements and contact records in a state that allows the requested update? Is any legal prohibition, including sanctions screening, a boundary to the change? In an inter-RIR transfer, can both regional policy environments accept the movement so the record does not fall between two systems?
Private transaction assurances are much wider. A buyer may want a warranty that the seller has no hidden lender claim, no conflicting lease, no undisclosed reputation problem, no tax arrears related to the transaction and no customer obligation that will impair use. A bank may want beneficial-owner evidence and payment-purpose letters. A tax adviser may want invoice wording and asset classification. A cloud platform may want a letter of authority and route-origin evidence. A public-sector customer may want procurement approvals and continuity warranties. Those assurances may be rational. They do not all belong inside RIPE NCC's decision.
The boundary is not always visible because the same document can serve both sides. A board resolution can prove authority to RIPE NCC, satisfy a buyer's closing checklist and reassure a bank. A merger certificate can prove successor identity to the registry and tax basis to auditors. A translated company extract can satisfy both the registry and a foreign buyer. The test is not whether the document is useful to more than one party. The test is whether the registry can state the exact ledger fact the document proves.
If the registry cannot name the fact, the demand becomes discretionary theater. "More comfort" is not a standard. "We need to know whether the person signing can bind the recognised holder" is a standard. "We need to understand the entire commercial background" is not a standard. "We need to know whether this merger legally moved the resources or the network business to the successor" is a standard. Thinness is not laxity. It is discipline.
This distinction protects RIPE NCC as well as resource holders. A registry that stays close to ledger facts is easier to defend. It can explain why it asked for evidence, why a substitute was accepted, why a transfer was delayed, and why a private commercial concern was left to the parties. A registry that absorbs too much of the private file becomes responsible, at least in market perception, for every bank, tax, sanctions, reputation and business-model anxiety around the transaction. That is not neutrality. It is institutional overreach disguised as caution.
Scarcity does not turn a clerk into a landlord. The fact that a record is valuable does not give the record-keeper a general authority to decide whether value may move. The registry must guard the ledger, not own the capital.
Identity and authority are the first fixed costs
Most cross-border files begin with a deceptively simple question: who is allowed to speak for the holder? In a domestic file involving a recently formed company, the answer may be quick. In the RIPE NCC region, the answer can involve decades of name changes, holding-company structures, state-owned entities, university departments, telecom licences, insolvency offices, free-zone registries, merger certificates and delegated network teams.
The registry record may name a company that has since changed its legal name. It may name a local operating company now owned by a foreign group. It may name a predecessor absorbed in a merger. It may name a university, ministry, municipality or public agency whose internal authority rules do not look like a private board resolution. It may name a legacy network that still routes but has not modernised its legal file. The person submitting the transfer request may be a director, an employee, a consultant, a receiver, an estate officer, a parent-company officer or a person holding a power of attorney.
RIPE NCC is entitled to ask for proof. If the wrong person can move a block, every holder is at risk. But identity and authority proof are not free. A current registry extract may need to be ordered. A notarised signature may need to be obtained. A power of attorney may need translation. A beneficial-owner chart may need to be updated. A public body may need a resolution or ministry letter. A university may need evidence that the department named in old records is part of the legal entity now signing. A successor may need to show a chain of merger documents that were never prepared with internet-number resources in mind.
These costs are often fixed. The lawyer, notary, translation, board meeting and certificate fee do not fall in proportion to prefix size. That creates a hidden minimum transaction size. A large transfer can absorb the file. A small transfer can be made uneconomic by the same proof burden. The effect is not always visible in approved-transfer lists because abandoned deals do not appear. They die earlier, when a seller realises that the evidence pack is not worth the price.
Authority proof also shifts bargaining power. A buyer with counsel and cash can demand a thick file from a small seller. A seller with a clean file can command a premium. A broker with experience in RIPE NCC submissions can charge for knowing what evidence will work. A small holder with messy records may accept a discount from an intermediary rather than face the proof work alone. These are market outcomes produced by evidence cost.
Accepted-equivalent rules would reduce the burden. If the registry needs to know legal existence, it should state which jurisdictional records can prove it: company extracts, official registry certificates, ministry letters, public-law statutes, court appointments, insolvency documents, university certifications or equivalent evidence. If the registry needs signer authority, it should state which documents are generally accepted: officer certificates, board resolutions, powers of attorney, registry-listed directors, court orders or public-authority letters. If old history is missing, it should state what combination of continuous operation, historic correspondence, corporate filings and sworn statements can cure the gap.
Equivalence is not leniency. It is the opposite of form bias. A narrow, serious registry cares about the fact, not the familiar shape of the paper. That matters across a region where legal forms vary widely. A Dutch extract, a Turkish trade-registry record, a Gulf free-zone certificate, a Central Asian ministry document, a French-language Canadian-style certification and a university letter may not look alike. The registry's job is to decide whether each proves the same ledger fact.
Beneficial ownership makes the file wider
Beneficial-owner evidence is one of the places where the registry file and the bank file overlap. A registry may need to understand control when it relates to authority, sanctions boundaries, fraud risk or the legal identity of a successor. Banks and counterparties often need more: ownership charts, shareholder records, director lists, politically exposed person checks, group-structure charts, source-of-funds statements and anti-money-laundering comfort. In a cross-border IPv4 transfer, these requests can arrive together even when only some are strictly registry-relevant.
The RIPE NCC region amplifies the issue because ownership structures are heterogeneous. A seller may be a small family-owned ISP, a state-linked telecom operator, a private-equity-backed data-centre group, a foundation, a municipality, a public university, a free-zone technology company, a carrier subsidiary, a bankrupt estate or a legacy enterprise with old records. Some jurisdictions publish beneficial-owner registers. Others disclose less or require private certification. Some structures use nominees or layered holding companies. Some public bodies do not have beneficial owners in the private-company sense. A template designed for one system can fail in another.
Beneficial-owner work also creates confidentiality tension. A buyer, bank or registry may ask for sensitive corporate information that the holder does not want spread across a transaction file. A small firm may fear exposing owners to competitors or political risk. A public body may be constrained by procurement law. A group operating in a sensitive jurisdiction may worry that disclosure will be misread by foreign banks or counterparties. These concerns do not remove the need for evidence, but they increase the cost of evidence handling.
The registry should therefore separate control facts from private risk appetite. If beneficial ownership matters because of a legal prohibition or because the signer lacks clear authority, RIPE NCC should ask for a bounded disclosure tied to that issue. If the buyer's bank wants a full ownership pack for anti-money-laundering purposes, that is a bank condition. If the buyer wants warranties that no hidden owner can challenge the transfer, that is a contract condition. If a tax adviser wants group charts to classify the sale, that is a tax condition. The registry should not absorb all of these into one unbounded review.
There is also a timing problem. Beneficial-owner evidence can go stale. A bank may require documents dated within a narrow window. A company registry extract may expire for diligence purposes before RIPE NCC completes its review. A sanctions or politically exposed person screen may need to be rerun near closing. If registry timing is uncertain, private parties must refresh evidence. That raises cost and creates further delay. Predictable review clocks therefore have direct economic value.
The same principle applies to merger updates. A merger file may involve a parent company, target company, operating subsidiary, asset purchase vehicle, insolvency administrator and post-closing integration entity. The registry's fact is whether the recorded holder or its relevant assets lawfully moved to the successor that will maintain responsibility. The private file may ask whether the acquisition price was fair, whether lenders consented, whether tax was paid, whether minority owners approved and whether customer contracts assigned. Those may be real concerns. They are not all registry facts.
When ownership evidence is broad, discretion can become invisible. A reviewer may feel uneasy about a structure and ask for more. A bank may feel uneasy and ask for a legal opinion. A buyer may use the uncertainty to renegotiate. The seller may concede because the outside date is approaching. The registry has not formally controlled capital, but its unbounded evidence standard has helped create a capital-control effect. Thin standards are a guard against that outcome.
Banking, FX and escrow turn days into money
The cross-border IPv4 file often becomes hardest after everyone has agreed in principle. Money must move. A buyer may be in euros, dollars, pounds, dirhams, lira, shekels, francs, dinars, tenge or another currency. The seller may invoice from a different jurisdiction. An escrow provider may accept some currencies and not others. A correspondent bank may ask why a technology company is paying for number resources. A local bank may treat the wire as an unusual intangible purchase. A public-sector buyer may need treasury approval. A bank may ask whether the payment relates to a sanctioned territory, an export-controlled service, a telecom licence, software, consulting, data services or something else.
The registry does not control this banking world. But registry timing and wording affect it. If the parties can show a clear transfer request, a defined approval stage and a predictable registry act, banks and escrow providers can map payment to closing. If the status is vague, each private institution adds caution. Escrow instructions become longer. Funds may be held until the database update is visible. Sellers may refuse to submit final approvals until escrow is funded. Buyers may refuse to fund escrow until RIPE NCC evidence is pre-cleared. Banks may refuse to release funds until they see an invoice and contract wording that matches the registry act. The file becomes circular.
Foreign exchange adds another layer. In some jurisdictions, conversion or outbound payment requires evidence of purpose. In others, the constraint is not law but bank risk appetite. A local operator may have revenue in local currency and a seller demanding euros. A bank may have limited correspondent access. A card payment or ordinary invoice rail may not be available for the transaction size. A lawful deal can stall because the payment system is not designed for address capital.
Escrow tries to turn this uncertainty into private settlement law. The parties agree on release conditions, outside dates, holdbacks, bank-charge allocation, tax withholding, document delivery, registry confirmation, route-origin transition and fallback rights if the registry declines or delays. In a cross-border RIPE NCC file, escrow language often has to bridge several legal systems. A seller wants to avoid losing negotiating position after handing over documents. A buyer wants assurance that money will return if recognition fails. A bank wants to know that funds are not being released to the wrong legal person. A tax adviser wants the invoice and release event to match the intended treatment.
The cost of escrow is not only the provider's fee. It is the time spent translating registry state into contract language. What is "approval"? Is it a ticket message, a signed agreement update, an actual registry record change, a completed inter-RIR handoff, or completion of operational steps such as reverse DNS and RPKI? If the registry provides only informal or inconsistent status language, the contract must cover more uncertainty. If the registry provides clear status categories, the contract can be narrower.
Useful categories could include authority evidence accepted, curable evidence missing, legal review pending, sanctions screen passed, inter-RIR counterpart approval pending, transfer approved subject to final agreement, record updated, reverse-DNS action pending, RPKI action required by holder and case closed. The specific labels matter less than the principle: private contracts need registry states that are precise enough to release money without turning every case into a bespoke negotiation.
Banking friction is where address capital can be controlled without any formal prohibition. Nobody declares a ban. The buyer cannot fund escrow. The seller cannot accept payment. The registry status is unclear. The bank asks for another opinion. The outside date passes. The block remains where it was. A narrow registry cannot fix the bank, but it can avoid making the bank's caution worse.
Tax, invoices and accounting are not afterthoughts
IPv4 transfer files often expose a language gap between network operations and finance departments. Engineers see an address block. Lawyers see contract rights and registration recognition. Accountants see an intangible with uncertain treatment. Tax advisers ask whether payment is sale proceeds, service income, capital gain, ordinary income, asset transfer, licence fee, lease income or part of a broader business acquisition. In cross-border settings, the answers can differ by country.
That uncertainty affects price. If withholding tax may apply, the seller cares whether the contract price is gross or net. If VAT or other consumption tax may apply, invoice wording and buyer status matter. If the buyer capitalises the purchase, it needs audit support for recognition timing and useful life. If the seller treats the transaction as a disposal of an intangible, it needs evidence of basis and transfer event. If the address movement is part of a merger, tax teams need to know whether the resource follows shares, assets, business operations or an internal reorganisation. If the arrangement is temporary, leasing and service classifications can alter invoices and compliance.
RIPE NCC is not a tax authority. It should not decide these classifications. But the registry's process can make tax analysis easier or harder. Clear recognition timing helps parties identify the event. A narrow description of the registry act helps invoice language. Predictable evidence requirements reduce the chance that tax documents must be refreshed. Service-specific continuity reduces the risk that a tax or accounting closing becomes entangled with customer outage risk.
Problems arise when registry language is too broad or too informal. A bank or auditor may ask for proof that the "asset" transferred. The registry may insist that internet number resources are not property in the ordinary ownership sense. Both statements can be true in their own domains, but the closing file still needs a practical bridge. The buyer did not pay for a metaphysical debate. It paid for a recognised state that allows it to operate, route, document and account for scarce address capacity. A registry can help by describing the act exactly: holder record updated, resources registered to the recipient, service relationship established, reverse-DNS delegation available to the recognised holder, RPKI certificate eligibility attached to the recorded resources under the applicable service.
Tax friction also affects small transfers. A large company can pay advisers to reconcile the language. A small ISP may receive contradictory advice or avoid a transaction because the tax and invoice treatment is unclear. A public institution may face procurement rules that require a category, and no category fits. A seller in a weaker currency may care deeply about whether taxes and bank charges are deducted before receipt. The compliance burden becomes a percentage of the deal.
Accounting conservatism can also reduce liquidity. If auditors discount the value of acquired IPv4 because registry finality, reputation cleanup or RPKI continuity is uncertain, buyers will pay less. If lenders do not understand how to treat address holdings after a merger, they will not credit the value fully. If a company cannot show that the acquired block is free of conflicting claims, it may carry a reserve. These are real costs, even though no router changes.
The registry should not promise accounting treatment. It should make the facts on which accountants rely as clear and stable as possible. That is another form of thinness: do the authoritative thing well, and let each private system apply its own rules without guessing what the registry meant.
Translation and legal opinions are the cost of pluralism
RIPE NCC's service region makes legal pluralism unavoidable. A cross-border transfer or merger file may involve Dutch association materials, a German commercial-register extract, a French legal opinion, a Turkish board decision, a Gulf free-zone certificate, a Ukrainian or Georgian corporate record, a Central Asian ministry letter, an Israeli company filing, a UK law share purchase agreement and Arabic or Russian supporting documents. Some may require certified translation. Some may require notarisation or apostille. Some may be digital records whose authenticity is difficult for foreign counterparties to verify. Some may come from jurisdictions where public registries are not always fast or complete.
Translation cost is not just the translator's invoice. It is the risk that a legal term changes meaning across systems. A "director" may not have the same powers everywhere. A "manager" may be a corporate officer in one jurisdiction and an employee title in another. A "good standing" certificate may not exist. A public body may act through a statutory mandate rather than corporate articles. A merger may be documented through court approval, registry entry, shareholder resolution, notarial deed, gazette notice or ministry decision. A private template can miss the functional fact.
Legal opinions fill the gap, but they are expensive. A buyer may ask local counsel to explain that a seller exists and can transfer. A bank may ask for an opinion that payment is lawful. A registry may ask for clarification when documents are unfamiliar. A public buyer may require counsel in both jurisdictions. For a large transaction, opinions are tolerable. For a small block, they can exceed the economic gain.
This is where predictable equivalence matters again. A registry serving more than 75 countries cannot maintain a bespoke rule for every legal form, but it can publish functional categories. Legal existence. Authority. Succession. Resource connection. Absence of known competing claim. Sanctions or legal boundary. Contact responsibility. Each category can then list common forms of acceptable evidence and explain how substitutes are considered. The point is not to automate judgment. It is to stop judgment from appearing arbitrary.
Translation rules should follow the same discipline. If a document is needed only to prove company name and registration number, a full certified translation of a long corporate instrument may be excessive. If a document is needed to prove that an asset transfer included the relevant network resources, a precise translation of the operative clauses may be necessary. If a public authority issues bilingual extracts, those should be accepted where reliable. If a bank requires more than the registry, that should be identified as private diligence rather than a registry requirement.
The cost of pluralism can never be zero. A common ledger exists precisely because legal systems differ. But common ledgers reduce transaction costs only when evidence standards are predictable, narrow and reviewable. If each cross-border file feels like a fresh negotiation over legal culture, the ledger is not doing enough.
Sanctions are a checkpoint, not the whole story
Sanctions screening belongs in this analysis as a boundary exhibit, not as the central drama. RIPE NCC operates from a European legal setting and must respect applicable legal constraints. Transfer and merger files can be affected by sanctions checks on parties, ownership, control, payment routes or related legal restrictions. In some cases the result may be refusal or inability to process a transaction. No serious analysis can pretend otherwise.
But sanctions should not swallow the whole compliance file. Most cross-border cost is not the result of a listed party. It is ordinary proof cost: legal existence, authority, succession, beneficial ownership, bank classification, tax treatment, FX movement, translation, escrow timing, route-origin assurance and continuity. A registry that treats every difficult file as if it were a sanctions problem risks expanding a narrow legal boundary into a general risk culture.
The distinction matters because sanctions vocabulary has a special force. Once a concern is described as sanctions-related, counterparties become cautious, banks slow down, lawyers ask for opinions, and sellers lose bargaining power. A possible match, a jurisdictional sensitivity, a bank question and a confirmed legal prohibition are different states. They should not be blurred. If they are blurred, legitimate holders in politically exposed regions pay a risk premium even when no prohibition applies.
A thin registry should maintain clear categories. Legal prohibition. Possible match under review. Ownership or control clarification needed. Payment rail unavailable but no transfer prohibition identified. Inter-RIR compatibility pending. Ordinary authority document missing. Each category has different consequences. A legal prohibition may block recognition. A possible match may justify a pause and request for evidence. A payment-rail issue may require alternate payment or timing arrangements if law permits. A missing authority document should not acquire geopolitical weight merely because the party is from a sensitive region.
Continuity is also important. A refusal to approve a new transfer is not the same as disrupting existing registry services. The last verified state should normally remain stable unless law, fraud, court order or a clear registry-integrity problem requires action. RPKI, reverse DNS and contact maintenance should not become bargaining chips in a transfer review. If a specific legal measure requires service restriction, the scope should be specific. If not, the registry should avoid converting a transaction checkpoint into operational instability.
This narrow approach is not soft on compliance. It is better compliance. It lets RIPE NCC obey law without allowing caution to become an unreviewable capital-control layer. It also protects the institution from claims that it is using legal anxiety to widen its role. In a region where politics, banking and conflict already affect networks unevenly, category discipline is part of fairness.
Inter-RIR transfers add a second rulebook
Cross-border does not always mean inter-RIR. Many RIPE NCC-region transactions cross national borders while remaining inside RIPE NCC. But when a transfer moves between RIPE NCC and another regional registry, the file gains a second institutional rulebook. Inter-RIR transfers must satisfy the policy environments of both registries where such transfers are available. That double approval protects uniqueness and destination recognition. It also adds settlement risk.
The economic reason is straightforward. A block leaving one registry must not become unrecognised in the next. The source registry must be satisfied that the current holder can release it. The destination registry must be satisfied that the recipient can be recognised. Both may apply transfer eligibility, waiting periods, documentation, legal screening and contact requirements. If either side pauses, the private closing pauses. If one side lacks a compatible path, the market path may not exist at all.
This is not an argument for unilateral movement. A global IPv4 market without mutual recognition would be unsafe. The question is whether double approval is used as interoperability or as policy border control. Interoperability asks: can the record move cleanly, with one recognised holder, accurate provenance, no duplicate claim and operational continuity? Policy border control asks broader questions about regional preference, allocation history, conservation sentiment or discomfort with market movement. The first protects the ledger. The second can trap capital.
Inter-RIR asymmetry also affects contracts. A buyer in another region may need to meet destination requirements that the seller cannot control. A RIPE NCC-region seller may ask the buyer to prove eligibility before signing. Escrow may require both source and destination approval before release. The outside date may be longer. Documents may need to be acceptable to two institutions, not one. A legal opinion sufficient for one registry may be unfamiliar to the other. The parties may need to coordinate RPKI and reverse-DNS changes across two systems. Each additional institution adds a timing distribution, not merely a step.
Price adjusts accordingly. A block movable within RIPE NCC under a known path may be valued differently from a block moving to a region with different requirements. A buyer with a smooth destination profile can offer more. A seller with clean authority evidence can demand more. A transaction involving a region with no compatible inter-RIR path, or a policy mismatch, may be forced into leasing, corporate acquisition or no deal. The number of addresses is identical. The mobility option is not.
Aggregate data would help. Completed-transfer listings show what closed. They do not show files abandoned because a buyer failed destination criteria, a seller could not prove authority, a second registry required more evidence, a waiting period applied, a sanctions or legal review caused delay, or the parties could not align escrow timing. Market health is visible in both approvals and disappearances. A registry that wants to reduce transaction cost should measure the silent side of the market.
For RIPE NCC, the principle should be: double rulebooks are acceptable when they secure finality; they are damaging when they multiply discretion. The registry's own contribution should be as narrow and transparent as possible so that the second institution's review is not compounded by avoidable ambiguity from the first.
Registry finality is only the start of operational cleanup
A cross-border transfer does not end when the holder record changes. The market treats registry recognition as the decisive closing event because it is the public settlement point. But the operational work after finality can determine whether the acquired resource performs as expected. Routing reputation, reverse DNS, RPKI, abuse contacts, geolocation data, routing-registry entries, cloud import, customer allowlists and security filters all need attention.
Routing reputation is especially important. IPv4 blocks carry histories. A range may have been used for mail, hosting, broadband pools, VPNs, public-sector services, content delivery or less reputable activity. It may appear in blacklists, threat-intelligence systems, geolocation databases, reputation feeds or private allowlists. A clean registry transfer does not automatically cleanse that history. Buyers know this and ask for representations, holdbacks, remediation cooperation and post-closing support.
Reverse DNS matters for mail, logging, diagnostics, abuse handling and customer systems. In the RIPE NCC context, reverse delegations are tied to the registry and database machinery. A buyer may need to plan when delegations move, who can edit them, whether old zones remain stable during transition and how customers are notified. If reverse-DNS continuity is uncertain, escrow may hold funds or the buyer may delay customer migration.
RPKI is a different but related dependency. Route Origin Authorisations influence how networks using origin validation treat announcements. A transfer can require old ROAs to be withdrawn and new ROAs to be created under the recognised holder's arrangements. A poorly timed change can create invalid or missing states. The economic risk is not that every route disappears at once. It is that some networks treat the prefix differently, cloud platforms hesitate, security teams ask questions and the buyer's launch becomes noisy.
Abuse contacts and registry data also need cleanup. If the old holder remains in public records after the buyer begins using the block, complaints may go to the wrong desk. If geolocation data lags, customers may see wrong regional content or fraud checks. If routing-registry entries remain stale, upstreams may reject route filters. If cloud platforms or transit providers require authorisation letters, the buyer needs the seller's cooperation even after registry recognition. These are not RIPE NCC's full responsibility, but its finality event triggers them.
That is why closing contracts increasingly separate registry finality from operational finality. Funds may be released in stages: part when RIPE NCC updates the record, part when RPKI and reverse DNS are in place, part when reputation remediation is underway, part after a short continuity period. The more predictable the registry handoff, the easier these private milestones are to write. The more uncertain the handoff, the thicker the contract.
The registry should not promise reputation cleanliness. It should provide clean, timely and unambiguous records so others can clean the rest. It should tell holders what happens to reverse-DNS authority, RPKI eligibility and database maintenance during transfer. It should preserve the last verified state until the new state is ready. It should avoid leaving a period in which sellers and buyers disagree over who can maintain operational records. Public finality should be operationally usable.
Small holders pay the highest percentage price
The distributional problem is simple: many compliance costs are fixed. A company extract, certified translation, legal opinion, board resolution, escrow setup, bank explanation, beneficial-owner chart and route-origin transition plan may cost nearly the same for a /24 as for a much larger block. A large cloud buyer, telecom group or address portfolio holder can absorb the fixed file. A small ISP, public body, university department, regional hoster or legacy company selling one modest range may not.
This fixed-cost structure changes market access. Small sellers may sell to intermediaries at a discount because intermediaries can absorb proof work and wait. Small buyers may lease from larger holders because acquisition cost is too high. Edge networks may avoid direct RIPE NCC membership or address holdings because the administrative burden feels too large. Public bodies may leave old records untouched because updating them requires legal work no one budgeted. A small network in a country with weaker banking rails may face higher effective cost than a larger network in a financial centre.
None of this requires discriminatory intent. The process can be formally equal and economically regressive. The same evidence request lands differently depending on counsel capacity, language, bank sophistication and deal size. A standard that looks modest in Amsterdam may be expensive in a smaller market. A bank review that a multinational treats as routine may be a board-level crisis for a regional provider. A translation that costs little relative to a large transaction may erase the margin on a small one.
Small holders also have less voice in shaping process. Large operators and frequent market actors learn the path. They know which documents to prepare, which lawyers to hire, which banks understand the transaction, which escrow clauses work and how long RIPE NCC review may take. Small holders often learn only when a deal is urgent. The difference becomes a private-information premium. Expertise is useful; dependence on private lore is unhealthy.
The registry can reduce this inequality without lowering integrity. It can publish small-transfer guides, accepted-equivalent evidence maps, sample authority letters, timing expectations, pre-check options, service-continuity explanations and aggregate delay data. It can distinguish missing curable evidence from serious legal risk. It can state when a certified translation is needed and when a targeted translation is enough. It can provide status language that helps banks and escrow providers without disclosing private material. It can make the ordinary path legible.
Fee design and support capacity matter too. If the transfer or merger path requires specialised staff, the cost must be funded. But funding should not create incentives to thicken the path. A service fee, if any, should reflect processing cost rather than address value. A registry should not quietly become a toll collector on scarce capital. Its legitimacy comes from reducing coordination cost, not harvesting scarcity rent.
Small-holder asymmetry is the best test of whether a registry standard is thin. Large parties can survive broad discretion. Small parties reveal its true cost.
What a predictable evidence standard looks like
A better RIPE NCC cross-border standard would begin with a checklist, but not the mechanical kind. It would be organised around ledger facts. For each fact, the standard would state why the fact matters, common evidence, accepted substitutes, confidentiality treatment, timing, review route and likely effect if evidence is missing. The aim would be to make diligence predictable before parties sign.
The first fact is legal identity. The registry must know who the current holder is, whether it still exists and whether the requested record change relates to that holder. Evidence could include registry extracts, formation documents, public-body records, university certifications, insolvency appointments, merger certificates or equivalent official material. The standard should recognise that not every jurisdiction issues the same document.
The second fact is authority. The registry must know that the person or entity requesting the change can bind the holder. Evidence could include officer status, board resolution, power of attorney, court appointment, receiver authority, ministry approval, public-authority letter or other legally valid act. The standard should explain when parent-company authority is enough and when local operating-company approval is needed.
The third fact is succession or transfer connection. In a merger or acquisition update, the registry must know that the relevant resources or network business moved to the successor. Evidence could include merger deeds, asset schedules, court approvals, purchase agreements, corporate filings, public notices, auditor letters or targeted legal opinions. The registry should not demand full commercial disclosure when specific operative clauses prove the fact.
The fourth fact is eligibility and absence of a recognised bar. This includes policy requirements, waiting periods, service standing, known disputes, inter-RIR compatibility and legal boundaries such as sanctions screening. Each should have a distinct status. A waiting period is not a sanctions issue. A curable document gap is not a dispute. A bank payment delay is not proof of ineligibility. Category precision reduces risk premiums.
The fifth fact is continuity. The registry should state what happens to database maintenance, reverse DNS, RPKI, contacts and existing records while review is pending and after recognition changes. The default should be preservation of the last verified state unless a specific reason requires alteration. Post-closing obligations should be clear enough for escrow and engineering teams to plan.
The sixth fact is reviewability. Parties should know how to challenge an evidence interpretation, how to supply substitutes, how long complete files typically take and what kind of explanation is available when a request is refused or delayed. Reviewability does not mean every private party wins. It means the market can learn the standard rather than guessing.
Aggregate reporting would complete the design. RIPE NCC could publish counts and timing distributions for transfers and merger updates by broad category: completed, withdrawn, delayed for authority evidence, delayed for succession evidence, affected by inter-RIR coordination, affected by legal review, refused, or pending beyond defined thresholds. Private data need not be exposed. The market needs enough information to price process risk.
This standard would not eliminate cost. It would move cost from surprise to preparation. That is the economic value of a ledger.
Finality without permission theater
The hard institutional balance is between two failures. One failure is under-verification: false transfers, stolen resources, broken succession records, duplicate claims, unstable RPKI, reverse-DNS confusion and market distrust. The other is overreach: a registry that treats every transfer as a discretionary permission file and every unfamiliar jurisdiction as a reason for indefinite caution. The first destroys confidence by making the record unsafe. The second destroys confidence by making the record too political, too slow or too expensive to use.
RIPE NCC should be judged by how well it avoids both. Its service region is large, legally varied and geopolitically exposed. It cannot operate as if every file were a simple domestic company update. It also cannot use that complexity to justify open-ended gatekeeping. The more varied the region, the stronger the case for narrow, predictable evidence standards. Pluralism is a reason for discipline, not a reason for institutional fog.
The market needs finality. A buyer must know when it can treat the range as acquired. A seller must know when it can receive funds and end responsibility. A bank must know what event supports payment. A tax adviser must know what event supports treatment. A cloud provider must know when the holder can authorise use. An upstream must know whose route-origin evidence to trust. Customers must know that service will not be disturbed because a registry file is still being interpreted.
Finality does not mean irreversibility in cases of fraud, court order or serious error. It means that once a safe recognition change has occurred, the registry should not leave the market wondering whether the transaction is merely provisional because an internal preference may later shift. Market finality is a public good. Without it, every deal carries a hidden discount.
The phrase address capital control should be used carefully, but not avoided. RIPE NCC is not a central bank and does not set exchange policy. Yet when a scarce productive input can move only after a registry act, and when that act can be delayed or conditioned by broad discretion, the registry has a capital-control surface. The legitimate answer is not denial. It is constraint: exact facts, accepted evidence, limited legal screens, service-specific continuity, reviewable decisions and aggregate transparency.
The thin registry is therefore a demanding institution. It must know enough to protect the ledger and refuse unsafe changes. It must also know when to stop. It must resist the temptation to become the buyer's diligence department, the bank's risk office, the tax adviser's classification authority, the broker's referee, the cloud platform's admission committee or a regional allocator of scarcity rents. Its job is narrower and more valuable: maintain the common record so that private systems can transact with less fear.
The closing room will never become simple. Cross-border IPv4 transfers and merger updates will always involve lawyers, banks, taxes, translations, escrow, routing cleanup and operational promises. RIPE NCC cannot remove legal pluralism from a region stretching across Europe, the Middle East and Central Asia. It can decide whether its ledger reduces the cost of that pluralism or amplifies it. In a post-run-out market, that choice is not clerical. It is one of the main economic functions of the registry.