RIPE NCC and the economics of documentation burden

Summary

• Documentation burden is the cost of producing evidence that RIPE NCC can accept before it changes registry recognition for scarce Internet number resources.
• The burden is justified when it proves a decision-relevant fact: current legal existence, authority to bind the holder, succession after merger or insolvency, absence of conflicting claims, sanctions status or eligibility for the requested registry update.
• It becomes costly because IPv4 scarcity has turned registry recognition into a closing condition for buyers, sellers, lenders, public bodies, universities, legacy holders and network operators that need timing certainty.
• RIPE NCC's service region makes the burden unusually varied: national company registries, languages, notarisation practices, public-sector records, insolvency files, sanctions checks and bank-risk constraints differ across Europe, the Middle East and Central Asia.
• A ledger should verify uniqueness and continuity; it should not turn proof production into discretionary merit review of whether a transaction, restructuring or business plan is institutionally preferred.
• The fixed cost of evidence falls unevenly. Large carriers and professional buyers can maintain clean files and counsel capacity; small networks, old academic holders, public agencies and insolvency estates often have to reconstruct history.
• The practical test is proportionality: every requested document should map to a specific registry fact, allow safe substitutes where history is messy, protect confidentiality and be reviewable enough that the market can price risk without guessing.

The Amsterdam file that cannot close

Imagine a closing file in Amsterdam for a modest but valuable IPv4 transfer. The addresses already route. The buyer has checked the reputation history. The seller still serves customers but no longer needs the whole block. The broker has agreed the timeline. The purchase price is ready to move through escrow once registry recognition changes. Engineers have a cutover plan. Lawyers have a schedule of prefixes. Nobody is waiting for the Internet to become technically possible.

The file stops on a different question: what document proves that the company asking RIPE NCC to update the registry is the legal successor to the name currently attached to the resources?

The seller is not a fraudster. It is a regional network business that crossed borders as it grew. The original allocation sat with a Dutch subsidiary. Later the customer contracts moved to a German parent. A service company in the Gulf operated part of the infrastructure. A holding company changed legal form. One director signed an acquisition deed in English, but the local company register extract is in another language and has an older transliteration of the name. The buyer's counsel wants certainty. The seller wants to close. The registry needs proof that the person requesting the update can bind the current holder or its legal successor. The missing paper is not a physical asset. It is acceptable evidence.

That is the economics of documentation burden. It is tempting to call the problem bureaucracy. That is too crude. A registry that updates scarce-number-resource records on weak evidence invites false transfers, captured accounts, shell-company claims, revived dissolved entities, sanctions ambiguity and stale-holder disputes. The ledger has value because it does not merely accept whatever a private buyer and seller assert. It preserves global uniqueness, records recognised holdership and gives the market a public reference layer that can survive private confusion.

Yet the same proof requirements impose costs. They require corporate extracts, merger records, asset-transfer documents, board or authorised-signatory confirmations, insolvency papers, translations, notarisation, old correspondence, historical schedules and sometimes explanations of local law. They consume counsel time, staff time and calendar time. They can delay a sale, complicate a financing condition, interrupt a network migration or discount a block whose routing history is clean but whose corporate history is not.

The central question is therefore not whether RIPE NCC should demand documents. It must. The question is whether the burden is tied tightly to the registry decision being made. Good documentation verifies a fact needed to protect the ledger. Bad documentation expands into a general demand for comfort. The difference matters because IPv4 scarcity has made recognition valuable. A resource transfer changes registry holdership; it does not move a physical thing. But in a post-exhaustion market, that change is often the moment at which money is released, warranties narrow, customers can be migrated and the buyer can rely on the public record.

RIPE NCC is a particularly revealing case because its region is legally and politically wide. It is a Dutch membership association serving networks across Europe, the Middle East and parts of Central Asia. That means a single registry process has to read evidence from many legal systems. A company registry extract in the Netherlands, a board resolution in Turkey, a notarised succession document in the Gulf, a court order in an insolvency estate, a university governance record in Scandinavia and a sanctions-sensitive payment case involving a high-risk jurisdiction may all be part of the same registry economy. The proof problem is not generic paperwork. It is the cost of making heterogeneous legal histories legible to one ledger.

The right institutional model is a ledger, not a gatekeeper. A ledger verifies who can act, what changed, whether the resource is eligible and whether the resulting record remains unique and continuous. A gatekeeper goes further, judging commercial merit or using documentation to settle broader institutional discomfort. The first role is necessary. The second is dangerous.

Documentation burden means acceptable evidence, not paper volume

Documentation burden should be defined with precision. It is the cost of producing evidence that the registry will accept for a specific decision. The cost includes locating documents, translating them, notarising them, aligning names across languages, proving legal succession, obtaining director or board confirmation, explaining insolvency authority, reconciling old allocation records, responding to follow-up questions, protecting confidential commercial material and waiting while a reviewer decides whether the file proves enough.

This is not the same as the number of attachments. A short request can be expensive if the relevant document is old, foreign, confidential or never drafted in the form now expected. A longer request can be cheap if the holder has modern corporate-secretarial systems and has prepared for transfers before. A large network group can often produce fresh extracts, power-of-attorney material and resource schedules quickly. A small hosting company that acquired a local ISP fifteen years ago may have to reconstruct a chain from archived email, customer invoices, tax files and a purchase agreement that never named Internet number resources explicitly.

The official RIPE materials provide useful technical exhibits. RIPE NCC's transfer page describes transfers of Internet number resources as changes of holdership. Its required-documents page identifies categories such as signed transfer agreements, recent registration documents, company papers, national-authority records for business-structure changes, closure confirmation and authorised-person confirmation where the old entity no longer exists. Its mergers and acquisitions page describes registry updates after business-structure change and notes evaluation under applicable policies and procedures, including sanctions checks. These pages do not settle the economics, but they show how proof becomes registry recognition.

The key word is "acceptable". A registry does not merely ask whether evidence exists. It asks whether the evidence is strong enough, current enough, complete enough and connected enough to justify changing the record. That test is necessary. But it also creates a cost that varies with institutional capacity. A company in a jurisdiction with a fast English-language registry extract may face a small burden. A public body whose authority rests in legislation, ministerial delegation or archived administrative records may face a larger one. A university with pre-commercial legacy space may have good operational continuity but a weak corporate paper trail. An insolvency estate may have a court-appointed administrator who can sell assets, but the registry still needs to understand whether Internet number resources were included, excluded or treated as part of the network business.

The burden is also about substitutes. The ideal document is not always available. A merger deed may not list each prefix. A purchase agreement may refer to "network assets" without an Internet-number schedule. A dissolved entity may have no officer left to sign. A legacy holder may predate modern service agreements. A national authority may record a change under a local corporate concept that has no neat English equivalent. A mature registry needs a proof map that asks: what fact are we trying to prove, and what combination of documents can prove it with tolerable risk?

If the fact is current existence, a recent company registry extract may be enough. If the fact is authority to bind the holder, authorised-signatory evidence or board confirmation may be relevant. If the fact is succession, merger records, asset-transfer agreements, court documents or historical registry correspondence may matter. If the fact is absence of a conflicting claim, the registry may need confirmation from more than one surviving entity. If the fact is sanctions exposure, screening and payment-risk review may be needed. If the fact is eligibility under transfer policy, the type of resource and recipient relationship become important. No single universal checklist can do all this work.

The danger begins when the registry cannot explain which fact remains uncertain. "Send more documents" is not an adequate economic instruction. It pushes the holder into open-ended legal spending. It also gives repeat players an advantage because they can infer from experience what the reviewer probably wants. The more RIPE NCC can map requests to decision-relevant facts, the lower the hidden tax on legitimate transactions.

Proof protects the ledger from false transfers and stale claims

The case for documentation is strongest when one starts with what can go wrong. IPv4 scarcity has turned old registry entries into valuable claims. Valuable claims attract opportunism. A person with control of an old email account may try to move resources for a company that no longer authorises them. A buyer may present a seller that cannot connect itself to the recognised holder. A shell company may claim to be the successor of a dissolved entity. A broker may press for speed before a conflict is visible. A former director may sign after losing authority. A buyer may want certainty that the seller is not merely the party currently routing the block.

In that environment, a registry that treats documents casually would damage the very market it is supposed to support. The registry record is not useful because it is easy to change. It is useful because it is hard to change without proof. When RIPE NCC asks for a transfer agreement signed by legally authorised directors, recent registration documents, evidence of business-structure change or closure documents, it is not moving a box from one shelf to another. It is deciding whether the public record should recognise a new holder.

False transfers are the obvious risk, but they are not the only one. Sham succession is a subtler version. The original holder may have disappeared, split, been absorbed or sold a business line. One surviving entity may control the customer contracts. Another may own the legal name. A third may have operated the network. A fourth may have bought assets in insolvency. Without evidence, the registry can only guess which claimant inherits the relevant authority. Guessing is not a registry function.

Hijack risk is another reason for caution. Routing control and registry control are related but different. A network may announce a block because it has technical access, customer arrangements or historic habit. That does not prove it can sell the block. Conversely, the recognised holder may not currently route the resource but may still be the legal party whose authorisation is needed for a registry update. Documentation connects operational reality to institutional recognition. It prevents a party from laundering routing control into legal control without proof.

Sanctions and corporate-risk ambiguity add another layer. RIPE NCC is based in the Netherlands and operates under European legal constraints. In a region that includes jurisdictions subject to changing sanctions regimes and bank-risk classifications, a transfer or restructuring file can raise questions that are not visible from routing tables. A registry may need to know whether either side is sanctioned, whether a payment path is possible, whether service can continue and whether a legal entity is the same entity that appears on a list. These are not ordinary customer-service preferences. They are legal operating constraints that affect whether the registry can approve or process a change.

Stale-holder claims are the slow risk. Old allocations and assignments were often made in a less formal era. Contacts changed. Universities reorganised. Early Internet service providers were acquired. National research networks became different institutions. Telecom subsidiaries were merged or sold. The public registry may have been maintained well enough for operations but not well enough for a sale, insolvency or restructuring. Documentation burden rises because the market now asks old records to perform a role they were not designed to perform: support high-value settlement.

The benefit of proof is therefore collective. Buyers gain confidence that the source can transfer. Sellers with clean files get better execution. Lenders and acquirers can underwrite network businesses with less uncertainty. Legacy holders are protected from opportunistic claims. The registry preserves uniqueness and continuity. The wider Internet avoids duplicate or contested recognition. Strong evidence standards are not anti-market. They are part of market infrastructure.

But the benefit is conditional. Evidence must remain connected to ledger protection. Proof that a legal successor exists is justified. Proof that an authorised person can bind the holder is justified. Proof that a merger carried the resources can be justified. A broad inquiry into whether the buyer is a worthy business, whether the seller should have used the space differently or whether the transaction aligns with a discretionary institutional preference is a different matter. A ledger is allowed to ask whether the record can change safely. It should be cautious about asking whether private capital should be allowed to move.

Scarcity turns a document request into a price signal

Before IPv4 exhaustion, a delayed registry file could be annoying without being decisive. Replacement address capacity was easier to obtain, and the economic stakes around a particular block were often lower. After exhaustion, the registry process has become part of price formation. A proof request changes timing, risk and bargaining power.

The first price is time. If a buyer needs addresses for customers, data-centre expansion, security appliances or access-network growth, a month spent chasing a local registry extract is not neutral. It may force temporary leasing, customer delay, additional NAT, renumbering or the purchase of a cleaner but more expensive block. If a seller needs proceeds for debt reduction, insolvency distribution or capital expenditure, registry delay changes cash timing. Escrow conditions may keep funds locked until recognition is complete. A document request can become a financing cost.

The second price is spread. A block with clean succession and predictable documentation sells differently from one with a complicated history. The buyer discounts for the chance that RIPE NCC will ask for additional evidence, that a translation will be rejected, that a dissolved entity will require court confirmation, that a sanctions question will slow approval or that the seller's authority will be challenged. The seller may insist that the block has routed for years and that customers rely on it. Both statements can be true. The discount is not about packets. It is about registry finality.

The third price is minimum efficient size. Documentation costs are often fixed. A small transfer may need the same legal categories as a large one: current existence, authorised signature, succession, transfer agreement, resource schedule and registry review. If the legal, translation and staff costs are similar, the cost per address is much higher for a small block. A rule that appears neutral can become regressive because small networks cannot amortise proof production across large transactions or repeated deals.

The fourth price is abandonment. Some files are not denied. They are never filed. A small legacy holder may decide that reconstructing history is not worth the expected proceeds. A public institution may avoid a clean registry update because the internal authority path is too cumbersome. A buyer may choose a larger seller with better paperwork even when it needs fewer addresses. A broker may avoid modest blocks from old holders because the execution risk is too high. The market becomes thinner, and underused capacity remains trapped.

The fifth price is shadow practice. If the recognised transfer path is too costly or uncertain, parties may rely more heavily on leasing, contractual control, routing arrangements, customer migration without registry cleanup or acquisition structures designed to avoid a clear transfer filing. Some of these arrangements are legitimate. Some increase opacity. A registry that makes the clean path too expensive can unintentionally encourage the messy path.

This is why a zero transfer fee is not the same as a low transfer cost. RIPE NCC may not charge a fee for resource transfers, but the market pays in evidence, counsel time and uncertainty. That is not an argument for a fee. It is an argument for measuring friction. If documentation protects the ledger, the cost is justified. If documentation reflects unclear expectations, repeated follow-up or broad risk aversion, it becomes a hidden tax on liquidity.

Scarcity also changes who benefits from better documentation. Clean files become a form of capital. A large carrier that keeps corporate records, transfer schedules and authorised-signatory evidence ready can move faster. A repeat buyer knows which documents to ask a seller for before signing. A professional broker can identify weak files early. A small operator that has run a reliable network for twenty years but lacks formal archives faces a discount. The market rewards administrative legibility.

That reward is not always unfair. Good records reduce risk. But it should not become an insider premium created by opaque registry expectations. If the registry's evidence map is predictable, smaller holders can prepare. If it is unpredictable, those with prior experience capture value from those who do not understand the process. The ledger then starts to allocate wealth through procedural knowledge rather than only through scarcity and operational use.

The RIPE region makes proof a cross-border problem

Documentation burden is different in the RIPE NCC region because the region is not one legal market. It spans mature EU company-law systems, non-EU European jurisdictions, Middle Eastern commercial registries, Central Asian corporate forms, public-sector networks, universities, research institutions, carriers, small ISPs, cloud platforms, sanctions-sensitive jurisdictions and companies using holding structures that cross several of these categories. The registry sits in Amsterdam, but the evidence comes from many places.

National company registry extracts are a good example. In one jurisdiction, a current extract may clearly show company name, registration number, directors and status in a form familiar to international counsel. In another, the extract may be local-language only, may require apostille or notarisation, may record authorised persons differently, may not show historical mergers cleanly or may use a concept of legal form that does not map neatly into Dutch or English corporate vocabulary. A transliteration difference can look trivial to the parties and material to a reviewer trying to match entities.

Translations and notarisation are not mere formalities. They are mechanisms for making evidence portable. A registry reviewer cannot safely rely on every local document without understanding what it says and whether it is authentic. Yet translation and notarisation add cost, especially when documents are urgent, old or commercially sensitive. In some jurisdictions, obtaining a certified extract or notarised copy is routine. In others it can be slow, expensive or affected by public holidays, conflict, political risk or administrative backlog.

Mergers and acquisitions multiply the complexity. A cross-border acquisition may involve a share sale in one country, asset transfer in another, customer-contract migration in a third and operational network control in a fourth. The private deal may be commercially coherent while the registry-relevant chain is unclear. Did the entity that held the resources merge into the buyer? Were the resources included in an asset schedule? Did a subsidiary retain the registry relationship while a parent acquired the business? Was the seller dissolved after the transaction? Which entity can sign now?

Insolvency adds still more uncertainty. A court-appointed administrator, liquidator or receiver may have authority to sell business assets, but the scope of that authority depends on local law and court orders. The registry needs to avoid recognising a transfer from a party that cannot bind the estate. The buyer needs confidence that a later claimant will not challenge the sale. The estate needs speed because delay erodes value. The cost of producing court documents, translations and resource schedules can be high, but weak proof would create even higher risk.

Universities and public bodies present a different evidentiary grammar. They may not have ordinary directors or commercial board minutes. Authority may flow through statutes, ministries, rectors, trustees, procurement offices or delegated IT departments. Historical Internet resources may have been requested by a research unit that later became part of a central institution. The registry fact remains the same: who can bind the recognised holder or successor? But the evidence categories must be flexible enough to fit non-commercial governance.

Sanctions and bank-risk review are also region-specific. The RIPE NCC's public materials in recent years have discussed sanctions screening and payment risks linked to jurisdictions that banks classify as high risk. A documentation request in such a case may need to establish not only corporate continuity but also whether service can lawfully continue, whether a party is listed, whether a payment route is permissible and whether a legal entity in one jurisdiction is controlled by a sanctioned person or organisation elsewhere. These checks are burdensome because they are not only registry checks. They are institutional survival checks.

The policy culture matters as well. RIPE NCC operates in a community-developed policy environment. That culture gives legitimacy because rules are not simply imposed by a vendor. But it also means that process, mailing-list consensus, procedural documents and member expectations can shape how evidence standards evolve. The danger is mandate drift by accumulation. A proof requirement that begins as a narrow defence against false transfer can gradually absorb broader concerns: market suspicion, sanctions anxiety, database hygiene, fee standing, merger policy, anti-speculation sentiment and reputational caution. Each concern may be reasonable. Together they can make the file heavier than the decision requires.

Mergers and insolvency expose the succession problem

The hardest documentation cases are often not ordinary transfers between two current, well-documented companies. They are succession cases. A registry must identify the legal successor, not the person who happens to control an account, route the resource or possess old correspondence. That distinction is the core of documentation burden.

In a clean merger, the proof may be straightforward. Recent company registration documents for the involved entities, official documents supporting the change in business structure and a signed transfer or service-agreement path can show the chain. In a real corporate history, the path is often less tidy. The holder changed name twice. A subsidiary was absorbed. An asset sale happened before a merger. A business line was sold without a resource schedule. A dissolved entity no longer has officers. A buyer acquired customer contracts but not the legal entity. The resource has routed continuously, but the legal paper trail is partial.

RIPE NCC cannot simply follow the router. Routing continuity is evidence of operational use, not proof of legal authority. Nor can it simply follow the newest account user. Account control is evidence of access, not necessarily succession. The registry has to answer a narrower question: what evidence shows that this current party can authorise the requested registry change for this resource?

That question protects the market. If a company buys a network business, it should want the registry to verify that the seller could sell. If an insolvency estate sells resources, the buyer should want court-backed evidence. If an old holder was acquired, the successor should want a clean public record. Without succession discipline, every buyer inherits latent litigation risk.

But succession discipline can also trap value. A small operator may have bought a local network years ago with a simple contract that everyone understood at the time. The contract may mention customers, equipment, towers, domain names and "all network assets" without listing each prefix. The seller may have dissolved. The buyer may have used the addresses continuously and paid for registry services. When the buyer later tries to transfer the block, the old contract may be considered incomplete for the decision now required. The historical bargain was real, but the evidence is not ideal.

The registry should not solve this by accepting any story. It should solve it by recognising evidence bundles. Continuous operation, old registry correspondence, invoices, public filings, acquisition documents, officer declarations, customer migration records, tax treatment, technical control and absence of competing claims may together prove a succession fact when the ideal document is unavailable. The standard should be high enough to deter fraud but not so rigid that only modern corporate archives count.

Insolvency illustrates the tradeoff sharply. A failing network business may hold scarce resources that could serve customers elsewhere. The estate has an incentive to realise value. Buyers need timing certainty. Creditors may depend on proceeds. Yet the registry faces heightened risk: distressed companies attract opportunistic claims, rushed transactions and incomplete files. A proportional documentation process would ask for the court authority, the administrator's power, the asset scope, the resource schedule and sanctions status, then move the file as predictably as possible. It would not turn insolvency into a general moral review of whether address value should exist.

Public-sector succession needs similar care. A ministry may merge agencies. A municipality may reorganise a broadband project. A university may transfer a research network to a national education provider. The evidence may be statutory, administrative or institutional rather than commercial. A proof standard built only for private companies can overburden these cases. The ledger fact is still real, but the evidentiary form differs.

The wider lesson is that succession is not a side case. In a mature region, many valuable resources sit inside organisations with long histories. As IPv4 value rises, old histories come back to the surface. The burden of documentation is the cost of translating that history into a registry update that others can trust.

Good-standing and compliance checks should stay narrow

Transfer and registry-update files often interact with membership standing, service agreements, fees, sanctions screening and contractual relationships. These checks can be legitimate. A registry cannot ignore its own service framework. But they must remain narrow. Documentation burden becomes excessive when a proof file becomes a container for every institutional concern.

Membership standing is the simplest example. If a member owes fees or has not maintained the service relationship needed for a transfer, the registry may have reason to pause certain actions. The economic risk is that a documentation process becomes a leverage point unrelated to the specific registry fact. A fee dispute, a sanctions payment problem, a missing contact update and a succession question are different issues. They may all need resolution, but they should be separated so parties understand what blocks recognition and why.

Sanctions checks deserve special discipline. The RIPE NCC cannot operate as if sanctions law is optional. If either side is sanctioned or if control risk is unresolved, the registry may be unable to approve a transfer or continue a service. But sanctions review should not become vague geopolitical discretion. The registry should identify, at the level confidentiality permits, whether the concern is party listing, ownership or control, payment route, jurisdictional banking risk, documentation authenticity or legal uncertainty. Different concerns require different evidence and different timelines.

Corporate-risk ambiguity is similar. A company may be legally active but opaque in ownership. A buyer may be incorporated in one jurisdiction and controlled from another. A seller may use a holding-company structure that is common in its industry but unfamiliar to a reviewer. Asking for additional evidence can be justified. But the request should still map to a decision-relevant fact. "We need to understand who controls the receiving entity for sanctions screening" is different from "we are uncomfortable with the transaction."

The ledger-not-gatekeeper distinction is most useful here. A ledger can verify identity, authority, resource status, policy eligibility, sanctions constraints and contractual prerequisites. A gatekeeper uses those categories to make broad judgments about commercial merit. For example, it is appropriate to ask whether a receiving party has the contractual relationship required for a particular Provider Independent resource update. It is riskier to ask whether the receiving party's business model deserves the resource if the policy does not make that a decision criterion.

The same principle applies to historical use. Evidence of routing, customer service and continuous operation can help prove succession or absence of an adverse claim. But documentation review should not become a retrospective trial of whether every past use matched an ideal allocation philosophy, unless a specific policy question requires it. Scarcity can tempt institutions to relitigate history. A registry should resist that temptation. Its job is to decide whether the current registry change can be recognised safely.

Confidentiality also matters. Transfer files can contain purchase agreements, company extracts, ownership details, court orders, sanctions-sensitive information, customer references and internal approvals. A registry needs enough evidence to decide. It does not need to make sensitive material public. Nor should it require more disclosure than the fact demands. Safe handling of confidential documents is part of proportionality. If holders fear that commercial or personal data will be exposed or over-retained, they may avoid the clean path.

Reviewability is the final constraint. A party denied or delayed by documentation should be able to understand the missing fact, not merely receive a conclusion. That does not require disclosing privileged analysis or third-party confidential information. It requires a structured explanation: the current file does not prove X; examples of acceptable evidence include A, B or C; substitute evidence may be considered if it proves the same fact; sanctions or legal constraints limit further detail if applicable. Such explanations reduce appeals, disputes and market uncertainty.

Small networks and legacy holders carry the fixed cost

Documentation burden is unequal because administrative capacity is unequal. A multinational carrier, cloud platform or professional IPv4 buyer can maintain counsel, compliance teams, corporate-secretarial records, prior transfer experience and dedicated registry staff. A small ISP, family-owned hosting provider, university, public body, local broadband project or legacy holder may encounter the process once in a decade. The formal standard may be the same. The cost is not.

Large organisations can prepare before the registry asks. They can obtain extracts, map subsidiaries, align names, clean up service relationships, update contacts, create resource schedules and negotiate transfer agreements with registry conditions in mind. They can treat RIPE NCC evidence as a standard closing deliverable. They can also absorb delay. If one file takes longer, the legal team keeps working and the network continues.

Small operators often pay in concentrated management time. The person who knows the old acquisition may also handle customers, routing, billing and outages. Locating a fifteen-year-old agreement may mean searching personal archives. Paying for counsel may be difficult when the block is small. A notarised translation can be a meaningful cost. A follow-up request that is minor for a large company can consume a week for a small one.

Legacy holders face a special version of the problem. Their resources may predate modern service agreements, modern portals and modern transfer markets. They may have good faith, continuous use and a long public history, but not a clean paper chain. The people who requested the resource may have left. The original institution may have changed name or form. The registry may need proof precisely because legacy histories are vulnerable to stale claims. Yet a proof standard that assumes modern corporate records can overburden the very holders it is trying to protect.

Universities are a common example. Early Internet resources may have been associated with a department, research project or national academic network. Over decades, the institution may centralise IT, change governance, merge campuses or transfer services to a consortium. The current university may be the obvious operational successor, but the evidence may be institutional minutes, trustee authority, statutes or administrative records rather than commercial merger deeds. If the registry asks for the wrong legal vocabulary, the burden rises without reducing risk.

Public bodies face similar translation problems. A government agency may not have directors. A municipality may not have an ordinary company extract. A public network may operate through delegated authority. A ministry may reorganise agencies by statute. The registry still needs evidence that the signer can bind the entity and that the resources follow the legal change. But acceptable evidence should match the institution.

Insolvency estates face a timing asymmetry. The estate needs to preserve value quickly. The registry needs to protect against invalid sale. Buyers need certainty before releasing funds. Court documents, administrator authority, asset schedules and sanctions screening may all be required. If the process is slow or unclear, value leaks from creditors and customers. If it is too loose, a later challenge can corrupt the ledger. The proportional answer is not lower proof; it is a predictable proof path.

The regressive effect is most visible in small blocks. A /24, /23 or /22 may be important to a regional network but not large enough to support extensive legal reconstruction. If the same categories of proof are required as for a much larger transfer, the per-address cost rises. The result is a market that favours larger, cleaner files. Scarcity already advantages incumbents. Documentation uncertainty can deepen that advantage.

This does not mean RIPE NCC should adopt a lower evidentiary standard for small parties. Fraud does not become harmless because the holder is small. It means the registry should reduce avoidable fixed cost: clearer examples, substitute evidence categories, early triage, standard explanations, limited document retention, confidentiality assurances and predictable escalation. A smaller holder should not have to pay counsel to infer what the registry needs when the fact to be proved can be stated directly.

Buyer timing makes evidence a settlement condition

The buyer in an IPv4 transfer buys more than routed addresses. It buys certainty that the public registry will recognise the change, that the transfer will not be undone by a stale claim, that reverse DNS and routing-security dependencies can be managed, and that the resource can support customers without a cloud over its status. Documentation burden therefore sits inside settlement architecture.

A private contract can allocate risk between buyer and seller, but it cannot by itself change the RIPE Registry. Escrow providers, brokers and counsel build closing conditions around the registry process. Payment may be released only when the update is accepted. Warranties may survive until a challenge period expires. Customer migration may wait for recognition. RPKI and reverse DNS changes may be sequenced around the registry update. A document request from RIPE NCC can therefore move money, not because the registry is a bank, but because the market treats its record as a settlement layer.

Timing uncertainty is expensive. A buyer may have a network plan tied to a customer launch. A data-centre operator may need addresses for servers already contracted. A security provider may need clean space for appliance deployment. A broadband operator may be trying to reduce pressure from address sharing. If the transfer file is delayed by a missing extract, the buyer may seek alternatives, renegotiate price or demand stronger escrow terms.

Sellers feel the mirror image. A seller may have accepted a price based on expected closing. If documentation review extends, the seller's proceeds are delayed. If the buyer's financing expires, the seller may lose the deal. If a follow-up request reveals that succession is weaker than expected, the seller may face a discount. Even if the registry ultimately approves, the proof process has altered bargaining power.

Professional buyers understand this and price it. They may prefer a larger block with a clean file over a smaller block whose corporate history is messy. They may demand a pre-closing document package. They may ask the seller to obtain registry confirmation before signing. They may require indemnities for succession risk. They may refuse an insolvency file unless the court documents are already translated and accepted. Documentation quality becomes a market attribute like reputation or fragmentation.

This is not inherently bad. It encourages better records. But there is a public-system issue because the registry's clarity determines how much of the discount reflects real risk and how much reflects uncertainty about process. If RIPE NCC can explain evidence requirements in scenario-specific terms, buyers can price real risk. If expectations are opaque, buyers price fear. Fear widens spreads and reduces liquidity.

The same is true for inter-RIR and cross-border transactions. When a RIPE-region buyer acquires resources from another region, or when resources move out of the RIPE region, timing depends on more than one registry. Requirements may include recipient eligibility, source-region approval, receiving-region commitments, needs-based compatibility in some cases, sanctions screening and coordinated update dates. The buyer needs a schedule. Documentation uncertainty in either registry becomes settlement risk.

The market therefore needs not only rules but performance data. Approved transfers are visible in published statistics, but abandoned or delayed files are less visible. A registry can publish transfer lists and still leave the market guessing about the invisible cost of missing evidence, business-structure review, sanctions escalation, legacy uncertainty and translation cycles. Aggregate process indicators would help: median time by request type, common reasons for follow-up, counts of business-structure cases requiring additional documents, and anonymised categories of non-approval or withdrawal. Confidentiality can be preserved while uncertainty is reduced.

Good evidence practice should make the registry a source of lower settlement risk. If the registry becomes a source of unpredictable delay, the market will build premiums around it. The cost will not appear on RIPE NCC's invoice. It will appear in discounts, escrow terms, abandoned deals and private structures designed to avoid uncertainty.

The proof target should be proportional and explainable

A proportional documentation standard begins with the decision. What is RIPE NCC being asked to do? Update holdership after a transfer? Recognise a merger? Change a legal name? Update an End User sponsorship relationship? Process closure? Recognise a legacy-resource change? Each decision has a different risk profile and therefore a different proof target.

The next step is to identify the fact that remains unproven. The file may fail because the current legal existence of a party is unclear. It may fail because the signatory's authority is not shown. It may fail because the chain from old holder to current claimant is incomplete. It may fail because the resource schedule does not match the agreement. It may fail because a dissolved entity cannot sign. It may fail because sanctions screening requires ownership detail. It may fail because the transfer restriction applies. These are not interchangeable problems.

A registry should request documents in a way that names the missing fact. That discipline protects both sides. The holder avoids spending money on irrelevant evidence. The reviewer avoids turning discomfort into open-ended fishing. The market learns how to prepare. The registry's legitimacy improves because its burden is intelligible.

Proportionality also means accepting substitutes where they prove the same fact. A national company extract may prove current existence. If an institution is public and has no extract, a statute or official letter may serve the same purpose. A merger certificate may prove succession. If the transaction was an asset sale, a purchase agreement plus schedule, court order, administrator confirmation and operational continuity evidence may prove the relevant chain. A board resolution may prove authority. If the entity uses a different governance form, a delegated-authority document may be better.

Explainability does not require disclosure of every internal judgment. Some details are confidential. Sanctions analysis may be legally sensitive. Third-party documents may not be shareable. Fraud indicators should not be published. But the requesting party should still know enough to respond. The difference between "not sufficient" and "the file does not prove that the dissolved transferor's resources passed to the receiving entity" is economically large. The second statement creates a path. The first creates uncertainty.

Reviewability is part of proportionality. If a party believes the registry has asked for evidence beyond the decision, it should have a practical way to challenge or escalate the issue. Formal arbitration or court action is too heavy for many documentation disputes. A pre-dispute review step, independent internal review or structured escalation can reduce unnecessary conflict. The aim is not to let holders evade proof. It is to prevent proof standards from drifting without accountability.

Confidentiality should be explicit. Parties should know how sensitive documents are handled, who sees them, how long they are retained, when redactions are acceptable and how commercially sensitive terms can be separated from registry-relevant facts. A buyer and seller may not want the registry to hold full economics of a deal if a resource schedule and authority evidence are enough. A public institution may need to protect personal data. An insolvency estate may have court documents that can be shared only in limited form. Narrow requests reduce confidentiality risk.

Proportionality also requires time discipline. Some evidence takes time because local law takes time. But follow-up cycles should not be indefinite. Early triage can identify missing core documents before parties assume a deal is ready. Scenario checklists can prevent avoidable surprises. Status categories can distinguish "awaiting party evidence", "under sanctions review", "policy restriction", "legal succession review" and "registry update scheduled". These categories do not reveal confidential conclusions. They let buyers and sellers manage risk.

Most importantly, proportionality keeps the registry in its institutional lane. RIPE NCC is a bookkeeper for unique Internet number resources, not a sovereign allocator of corporate destiny. It should be demanding where the ledger is at risk and restrained where the decision does not require broader judgment. That is not a weaker registry. It is a more reliable one.

Documentation can become mandate laundering

Mandate laundering occurs when an institution uses a narrow legitimate function to carry broader discretionary aims without saying so. Documentation review is vulnerable to this because proof requests are often technical, confidential and hard for outsiders to evaluate. A registry can expand its influence by asking for more evidence, slowing a file, interpreting uncertainty conservatively or making parties satisfy concerns that are adjacent to, but not required for, the registry decision.

The risk is not necessarily bad faith. Institutions learn from difficult cases. A forged file makes reviewers more cautious. A sanctions surprise creates new checks. A disputed merger encourages broader succession review. A court challenge teaches the value of fuller documentation. Each change may be reasonable in isolation. Over time, the file gets heavier. The registry can begin to treat every case as if it contained the worst fact pattern.

Scarcity intensifies the temptation. When IPv4 resources have market value, some community members may dislike transfers, speculation, leasing or the asset-like treatment of addresses. Documentation can become a way to express that discomfort without changing policy directly. A registry that cannot prohibit a valid transfer may still make the path more burdensome. A community that distrusts markets may tolerate heavy evidence demands because they slow transactions. The language remains "proof"; the effect becomes capital control.

That is why official policy and operational documentation should be read separately. A policy may allow legitimate holders to transfer resources subject to restrictions. A procedure may require evidence of authority and succession. A reviewer may feel institutional pressure to avoid appearing permissive. If those layers blur, the holder experiences a discretionary gate rather than a ledger.

Mandate laundering can also happen through compliance. Sanctions screening is necessary. Corporate-risk review can be necessary. Banking constraints can be real. But if "compliance" becomes a general label for unease about certain jurisdictions, counterparties or transaction types, the burden loses discipline. The registry should say, within legal limits, what compliance fact is at issue. Is the party listed? Is beneficial ownership unclear? Is payment blocked by bank policy? Is the legal entity in a high-risk jurisdiction but not sanctioned? Does the concern affect transfer approval or only fee collection? These distinctions matter.

Database hygiene is another adjacent concern. Accurate records are essential. But documentation burden in a transfer file should not become a broad audit of every historical data weakness unless those weaknesses affect the requested change. If the file reveals inaccurate contacts, they should be corrected. If it reveals unclear succession, that must be resolved. But a transfer should not become an opportunity for an open-ended review of unrelated historical imperfections.

Fee standing and service relationship issues should also be bounded. A member may need to satisfy contractual prerequisites before a transfer. But a registry should avoid using a high-value transfer as leverage for unrelated pressure beyond the rules. The market can accept clear prerequisites. It struggles with discretionary bundling.

The antidote is explicit purpose limitation. Every proof request should answer: which registry decision is this for, what fact is being verified, what risk does the fact control, what evidence can prove it, what substitute evidence may be acceptable, and what happens if the evidence cannot be produced? This turns documentation from mandate laundering into disciplined verification.

A better burden is measurable

The economics of documentation burden cannot be managed if it is invisible. RIPE NCC already publishes information about approved transfers and public policy documents. That is useful, but it is not enough to understand proof friction. The key data often sit in the process: how many files require follow-up, what categories of evidence cause delay, how long business-structure changes take, how often translation or notarisation is requested, how many cases are withdrawn, how often sanctions review changes the outcome, and how frequently legacy-resource files require succession reconstruction.

Publishing individual files would be inappropriate. Transfer documents contain confidential commercial, legal and personal information. But aggregate reporting is possible. The registry could publish median and percentile processing times by broad request category: ordinary intra-region transfer, merger or acquisition, name change, sponsorship change, legacy transfer, inter-RIR transfer, insolvency-related update. It could report common follow-up categories without naming parties: missing current registration document, unclear signatory authority, incomplete succession chain, resource schedule mismatch, sanctions or ownership review, transfer restriction, outstanding contractual prerequisite, translation or authenticity issue.

Such reporting would help several audiences. Buyers would price execution risk more accurately. Sellers would prepare documents earlier. Brokers would reduce failed deals. Small holders would see what to expect. The community would know whether documentation burden is growing. RIPE NCC staff would have evidence for process improvement. The board and members would be able to distinguish necessary caution from avoidable friction.

Measurement should also include abandoned and withdrawn files. Approved transfer statistics show where the market succeeded. They do not show where proof costs were too high, where parties gave up or where uncertainty led to private alternatives. A confidential aggregate count of withdrawn requests by broad reason category would reveal whether documentation burden is trapping resources.

Time-to-first-triage matters as much as final approval time. A buyer and seller need early notice that a file has a serious succession problem, a sanctions-review issue or a missing authority document. Reporting should also distinguish party-caused delay from registry review time. If a holder takes six weeks to produce a court document, that is not the same as six weeks of internal queue time.

The goal is not to turn RIPE NCC into a transaction-acceleration service for traders. The goal is to make the ledger predictable. Predictability is a public good. It lowers risk premiums, reduces disputes and encourages holders to use official channels. A registry that measures burden can defend necessary proof with evidence. A registry that does not measure burden asks the market to trust that friction is always justified.

The rule for a mature registry

The mature rule is simple: documentation is justified only when it is tied to a specific registry decision and a specific risk to uniqueness, continuity, legal authority, contractual eligibility or legal compliance. Everything else should be treated with suspicion.

This rule does not weaken RIPE NCC. It strengthens it. A registry that can explain why it needs evidence is harder to attack and easier to trust. A registry that accepts substitute evidence, protects confidentiality, reports aggregate friction and separates ledger proof from commercial merit review is more resilient across a diverse region.

Several practical principles follow. Define the missing fact in every additional request. Allow evidence bundles where the ideal paper no longer exists. Scale the explanation to the burden: a recent extract needs little commentary, while a notarised translation of old court papers or a reconstructed acquisition chain deserves a clear reason. Protect confidential material by allowing redactions, separate schedules and limited-purpose submissions where those still prove the relevant fact.

The registry should also separate issues. A fee matter, sanctions review, legal succession gap and transfer restriction may all affect a file, but they should not be blurred. It should publish aggregate process data on timings, follow-up categories and withdrawal reasons. It should maintain review paths short of litigation for disputes over evidentiary scope. And it should keep public policy separate from hidden friction: if the community wants stricter transfer restrictions, it should debate policy; documentation should not become a backdoor way to implement market suspicion.

The RIPE NCC region needs documentation discipline precisely because the registry is important. Europe, the Middle East and Central Asia contain old academic networks, small operators, public institutions, sanctions-sensitive members, large carriers, cloud platforms, brokers, buyers and insolvency estates. They all rely on one recognition layer for scarce resources that may have decades of history. Weak proof would invite fraud and contested claims. Excessive proof would trap value and favour those with the largest legal budgets.

The right answer is neither frictionless transfer nor paperwork maximalism. It is narrow, explainable, reviewable evidence. The ledger should be hard to corrupt and easy to understand. It should verify succession without becoming a court of commercial virtue. It should protect scarcity from fraud without treating every transfer as suspect. It should remember that documentation burden is not free simply because it is borne outside the registry's budget.

The Amsterdam file eventually closes only when the missing evidence proves the fact that matters: the current party can bind the holder or successor, the resource can move under the applicable policy, and the registry update will preserve a unique and continuous record. That is a legitimate burden. The problem to watch is everything added after that point.