Summary

  • “Transfer” is an administrative umbrella, not an economic conclusion. A legal-name change, statutory conversion, merger into a successor, intra-group migration, operational spinoff and sale to an unrelated buyer can all require a different organisation in the registry record, but they do not create the same market event.
  • The first classification question should be continuity: did ultimate economic control, the operating business, customers, equipment, staff, routes and service obligations remain substantially connected? The answer does not eliminate document review; it determines whether the registry is verifying succession or judging an arm's-length disposition.
  • Current RIR practice already contains useful distinctions. ARIN's 8.2 process accepts merger, amalgamation, court and public filings, applies no recipient needs test and recognises regional continuity after a reorganisation. APNIC and RIPE NCC publish simpler legal-name paths. RIPE NCC also waives the ordinary transfer agreement for consolidation between accounts held by the same member.
  • Cross-border groups require a chain, not suspicion by default. Registries should verify each legal step, the entity that will operate the network, the continuity of customers and the resulting regional service relationship. Tax residency, holding-company location and legal form are relevant facts, but none alone proves that IPv4 space was sold.
  • Spinoffs require their own test. They can create a genuinely independent company without an arm's-length purchase of addresses. Where the separated operating business, network assets, staff, contracts and users move together, the addresses may follow the business as succession infrastructure rather than as isolated inventory.
  • A proportionate registry offers a fast lane for verified continuity, a standard lane for operational succession and a market lane for unrelated buyers. It records why the case was classified, asks only for evidence tied to that reason and publishes separate statistics so reorganisations are not counted as address-market sales.

The group chart changes at midnight; the packets do not

A multinational operator completes a legal reorganisation at the end of its financial year. One subsidiary merges into another. Customer contracts transfer by operation of law or under a documented novation. The same engineers arrive for work the next morning. The routers remain in the same facilities. The same autonomous system originates the same prefixes. Upstreams, abuse desks and customers see no commercial sale of address space and no change in service.

The registry may still show a company that no longer exists.

Correcting that record is not optional. A dissolved entity cannot remain the permanent administrative face of a live network. Contacts, billing, security credentials and authority need to move to the surviving company. The registry must verify that the survivor is real and that the reorganisation connects it to the old holder.

But the necessary correction does not turn the transaction into an address sale. There may be no unrelated buyer, no negotiated price for the prefixes, no release of unused inventory and no competitive decision about which network deserves scarce capital. The economic enterprise may remain under the same parent and beneficial control. The only thing crossing the registry boundary is the legal person through which that enterprise operates.

The opposite case exists. A holder can place address space in a dormant subsidiary and sell the shares to an unrelated buyer. The paperwork may call the event a corporate acquisition, yet the economic substance may be a market disposal of the resources. Labels do not settle classification in either direction.

A competent registry therefore asks what changed. Legal identity? Ultimate control? Operating assets? Customers? Routing? Geographic nexus? Consideration? The answers determine the evidence needed and the discretion justified. Treating all cases as equivalent “transfers” makes the record simpler for the institution and less truthful for everyone else.

Six corporate events sit behind one administrative label

The differences can be organised into six common forms.

A pure legal-name change leaves the legal person intact. Its registration number and continuity remain, while its official name changes through a filed amendment or similar act. The registry should update the name after verifying the government record. No resource has moved between legal persons.

A statutory conversion changes legal form, such as a corporation becoming a limited liability company, where applicable law treats the converted entity as continuing. The registration number may change in some jurisdictions and remain in others. The decisive evidence is the legal effect of the conversion, not the appearance of a new suffix.

A merger or amalgamation may leave one survivor, create a new successor or combine businesses under a different parent. Control may remain within a group or pass to an acquirer. The old entity can disappear by operation of law, making succession evidence necessary even if no address-specific bargain occurred.

An intra-group reorganisation moves a business among entities under common ultimate control. It may be motivated by financing, regulation, tax, licensing, risk separation or geographic management. Consideration may appear for accounting purposes, but the economic owners can remain the same.

A spinoff or demerger separates a business into an independent entity. Shareholders may receive interests in the new company rather than an unrelated purchaser paying the old company for addresses. The operating division, customers and network can move together. Control after separation is different, but the event is still not necessarily an arm's-length address sale.

An arm's-length sale places resources or a resource-using business with an unrelated buyer for negotiated consideration. The addresses may be an isolated subject of sale or one component of a broader asset transaction. Source authority, recipient qualification, transaction finality and market rules become central.

These forms can overlap. A cross-border acquisition may be followed by an intra-group merger. A spinoff may later sell a block it no longer uses. A rename may accompany a conversion. The registry needs a chain of classifications rather than one label attached to the final form.

Continuity is not a slogan; it is a set of observable facts

“Same business” can be abused if it means nothing more than a lawyer's assertion. A simplified lane needs a concrete continuity test.

Start with ultimate economic control. Identify the persons, parent or public shareholder structure that controlled the relevant business before and after. Common control does not mean every intermediate subsidiary is irrelevant. It means the move is not an arm's-length market choice between unrelated owners. A public-company reorganisation can show continuity through filings and group accounts. A private group may need ownership registers, signed charts or other lawful evidence.

Then test operating continuity. Did the network equipment, facilities, autonomous systems, engineering teams, network-management functions and customer-service obligations move with the successor? Are the addresses still used for the same access network, hosting platform, enterprise service or infrastructure? A business that keeps its routers and customers has a stronger succession case than an empty company carrying only a prefix registration.

Next comes customer continuity. Subscriber agreements, enterprise contracts, assignment records, billing transitions and notices can show that the resource-using business continued. These documents should be sampled or redacted to protect customers. A registry usually needs proof of continuity, not an entire customer list with commercial terms.

Finally test resource isolation. Were the prefixes singled out, priced separately, marketed to outsiders or moved without the business that used them? Did the old company retain the customers and equipment while only the registry position moved? Isolation does not automatically prove misconduct, but it weakens the claim that the change is merely corporate housekeeping.

No single factor controls every jurisdiction. The purpose is administrative classification, not a universal corporate-law rule. The registry records the facts it can verify and identifies uncertainty. A continuity score cannot replace judgment, but a public factor set is better than an unexplained instinct that one corporate form looks like a sale.

ARIN's 8.2 process recognises succession without a needs test

ARIN's current transfer guide provides a useful institutional distinction. Under section 8.2 of the Number Resource Policy Manual, ARIN considers transfers connected to mergers, acquisitions and reorganisations when evidence shows that the new entity acquired the assets using the resources or acquired the registered organisation as a whole.

The listed proof is transaction-specific: an asset purchase agreement and bill of sale, a final merger or amalgamation instrument filed with a governmental authority, a final court order, public securities filings, amended articles or government verification of a name change. If several transactions connect the old and new organisations, ARIN requires the documents for each link. Sensitive financial information can be redacted, and a standard nondisclosure agreement is available.

Most importantly, ARIN says resources moved under 8.2 are not subject to a needs-based assessment. That is not a favour to corporate groups. It is recognition that the registry is verifying succession to a business and its network assets, not allocating addresses among competing buyers. Applying the ordinary recipient-demand test would let an administrator re-decide how much infrastructure a surviving company is permitted to keep after the legal transaction has occurred.

ARIN also addresses cross-border continuity. If a merger, acquisition or reorganisation leaves the surviving entity without a real and substantial connection to the ARIN region, it may continue to hold resources previously issued by ARIN, although it does not qualify for additional resources until the required regional connection returns. This separates continuity of existing registration from eligibility for new issuance.

The model is not free of difficult boundaries. A share sale of a resource-rich shell can fit the form of acquiring the registrant as a whole while resembling a market purchase economically. An asset deal can carry a genuine operating network or only a thin set of assets. The answer is not to impose a needs test on every 8.2 case. It is to ask whether the acquired business and resource use are real, and to route isolated resource transactions into the appropriate market-transfer lane.

ARIN also shows why a rename should not be confused with succession

ARIN's organisation-record guidance has a separate name-change route. An authorised account user submits the new legal name, and ARIN reviews the request. The page warns that a change connected to a merger, acquisition, reorganisation or similar event must use a transfer request instead.

The distinction is sensible because a pure rename preserves the legal person while succession changes it. Yet the present guidance also illustrates the contract-boundary issue: after approval, ARIN says an organisation may need to sign a new RSA under the new name before the change is processed. Its RSA FAQ says a new RSA is required where the organisation's legal status has changed since the earlier agreement.

The registry should state exactly which condition applies. If the same legal person merely adopted a new name, the document should preserve continuity of the existing agreement or explain why re-execution is needed to align the party name. If the legal person converted or a successor emerged, the registry should classify the event accordingly. “New name” must not hide “new obligor,” and “new obligor” must not be mistaken for “unrelated buyer.”

Historical ARIN guidance makes the taxonomy concrete. Its archived explanation of three registration changes treated a filed name amendment or a conversion such as LLC-to-corporation as potentially appropriate for the name-change lane, while directing mergers and asset movements to 8.2. Corporate law differs by jurisdiction, so the exact effect cannot be universalised. The enduring point is that the registry can and should distinguish legal continuity from succession.

A reasoned name-change receipt would identify the evidence, state whether the legal person continued, map the former and current name, identify any agreement treatment and confirm that no market transfer was recorded. That receipt is more useful than a generic transfer row.

RIPE NCC separates names, business changes and same-member consolidation

RIPE NCC's current business-structure guidance starts from record accuracy. LIRs and End Users must update their information when the organisation's structure changes. A legal-name change without a structural change can be made through the LIR Portal, while a merger or acquisition requires recent registration documents and official legal materials supporting the change.

That distinction is reinforced by the operational transfer pages. RIPE NCC's within-region transfer guidance ordinarily requires a transfer agreement signed by authorised representatives. For a consolidation between LIR accounts held by the same member, however, no transfer agreement is required, although recent company-registration evidence may be requested.

This is a valuable proportionality rule. Moving resources between two accounts of the same legal member is an administrative consolidation. Demanding a bilateral bargain between the member and itself would produce paperwork without proving an additional fact. The registry verifies the common holder and records the consolidation.

RIPE policy does impose a 24-month restriction on scarce resources after they are received through a transfer or business-structure change, although further merger or acquisition changes remain possible during that period. The distinction prevents the lock from blocking genuine subsequent succession while still affecting later discretionary transfers. Whether every business-structure change should start the same lock is a separate policy question; at minimum the registry should label the event accurately so the restriction can be audited.

RIPE NCC's published transfer statistics distinguish policy transfers from changes due to business structure. That field matters. If analysts count both as market turnover, they invent liquidity from corporate housekeeping. Every RIR should publish the same separation, with a further category for pure renames and same-holder consolidation.

APNIC draws a bright line between legal-name change and entity movement

APNIC's transfer overview defines a transfer as movement of resources from one legal entity to another and expressly says this differs from an organisational legal-name change. The separate name-change procedure allows a corporate contact to submit the new legal name, a description and a certificate or similar government document. APNIC then confirms which records will be amended.

Where a business structure changes, APNIC uses a merger, acquisition or reorganisation process. The source initiates the request, supplies relevant legal documents issued by governing authorities, and the recipient acknowledges it. If the recipient lacks an APNIC account, one must be created so the future record has an accountable manager.

The strength of this design is classification. The weakness is that the published examples can still make a sales agreement appear more central than other succession instruments. Corporate reorganisations differ across the Asia Pacific region. A statutory vesting document, court-approved scheme, government conversion certificate or chain of group resolutions may be the operative evidence. APNIC's reference to governing-authority documents helps keep the door open, but the reason for each requested document should remain visible.

APNIC's transfer conditions also show that reorganisation is not costless administration. Account creation, annual membership fees or transfer fees can apply, and all transferred resources become subject to current APNIC policies. Certain 103/8 resources carry a five-year restriction that also applies to merger, acquisition and reorganisation changes. The source loses rights after completion, and the recipient's annual fees may rise.

These consequences make a before-and-after statement essential. Even where the economic business continues, the registry relationship can change. Simplified verification should not mean hidden consequences. The institution should distinguish the absence of market discretion from the continuing need to disclose service, fee and policy effects.

LACNIC recognises broad reorganisation forms but retains a capital-allocation test

LACNIC's current IPv4 policy recognises partial or complete mergers, acquisitions, business reorganisations and relocations for both ISPs and end users. It asks for legal support and gives examples: documents validating asset transfer, an inventory of assets used to keep the resources in use and a list of customers using them.

That breadth is important. It acknowledges that a company can reorganise or relocate without fitting one narrow merger form. It also places operational evidence beside corporate paperwork. A legal succession document says who succeeded; assets and customers help show that the network business followed.

The policy then goes further. It requires the organisation to justify continued need for all resources and can force return or transfer of surplus. This turns a succession review into a capital-allocation review. The legal business may have continued, customers may still rely on the network and the registry record may plainly need correction, yet the institution reopens whether the successor is permitted to retain the full block.

That is precisely the discretion a continuity lane should avoid. A reorganisation does not create more or less scarcity. It changes the legal form through which an existing network operates. If there is evidence of fraud, abandonment or an unrelated resource sale, the registry can investigate that fact. Treating every successor as a fresh applicant risks making a necessary record update conditional on surrender of capital.

LACNIC's public merger, acquisition and name-change procedure groups absorptions, asset-and-liability purchases, mergers and legal-name changes under the same procedural heading. That convenience should not erase the distinctions inside the case. The public record should say whether the legal person continued, whether a business succeeded and whether an unrelated purchase occurred.

A thinner rule would preserve LACNIC's evidence strength while removing the needs reallocation. Verify the legal event, assets, customers and current use. Record the successor. If demonstrably unused resources are later offered to a third party, process that later event under the market-transfer rule rather than treating corporate succession as a compulsory divestment moment.

AFRINIC's asset-and-customer test identifies substance but should remain bounded

AFRINIC's resource-transfer guidance describes merger and acquisition transfers in operational terms: an organisation acquired assets such as customers and equipment from another organisation, and those assets use resources obtained from AFRINIC. It distinguishes a legal-name change not connected to a merger, acquisition or reorganisation from the transfer path.

That framing identifies the right evidentiary link. The resources should follow a real business or recognised successor, not a paper claimant with no connection to use. Customer and equipment continuity can protect against fabricated mergers that serve only to move prefixes.

AFRINIC also says it assesses utilisation and may work with holders to transfer required resources while seeking voluntary return of extras. As with LACNIC, the danger is that a verification process expands into a fresh allocation decision. A registry can test whether the claimed operating assets are genuine without reopening every historical sizing judgment.

The distinction is especially important for legacy holders and cross-border groups. Old allocations may not map neatly to contemporary efficiency rules. A group may centralise equipment while preserving customers across several subsidiaries. A cloud or hosting operator may change architecture without reducing dependence on the addresses. An apparent utilisation ratio can miss reserve capacity, customer assignments, transition space and disaster recovery.

A bounded test asks whether the transaction story is true: did the business, customers or infrastructure that justified succession move? An unbounded test asks whether the registry would issue the same quantity today. Those are different questions. The first protects the record. The second lets corporate reorganisation trigger a discretionary reallocation of existing capital.

AFRINIC's current environment also warrants careful dating. Policies and implementation status can change, and a ratified transfer framework does not prove every inter-RIR path is operational. A company planning a cross-border reorganisation should obtain a current written statement from each responsible registry. The structural recommendation remains stable: verify succession, publish the service state and avoid treating the correction as an address auction.

Successor evidence should form a chain, not a document dump

Corporate succession is rarely proved by one universal instrument. The evidence should be organised into a chain with a beginning, intermediate events and a current endpoint.

The beginning is the registered holder. Record its official name, number, jurisdiction and resource set as they appeared before the change. If the public record uses an old trading name, connect it to the legal entity. If the entity has already dissolved, preserve the last reliable record rather than rewriting history to match the claimant.

Each intermediate event then gets one row: date, predecessor, successor, event type, governing jurisdiction, official instrument, legal effect claimed and resources or operating business affected. A group that merged A into B and later contributed B's network division to C must prove both links. Presenting only the final parent-company chart is limited public evidence.

The endpoint identifies the entity that will become responsible for the registry relationship. Its authorised signers, current registration and service-region nexus must be established. If a sponsoring arrangement, national registry or another RIR is involved, the chain should show where responsibility lands.

Public documents should be preferred where they prove the fact. Government registers, court orders, securities filings, filed merger certificates and official conversion records create independent anchors. Private agreements may be necessary for an asset transfer, but the registry should permit redaction of price, tax advice, customer-specific terms and unrelated schedules. It needs the parties, signatures, effective event and connection to the resource-using business.

The chain should end in a reasoned finding: legal-person continuity, statutory succession, operational-business succession, intra-group transfer under common control, spinoff of the resource-using business, or arm's-length disposition. That finding determines the lane. It does not purport to decide every tax, creditor or property issue.

Customer continuity is evidence of operation, not a demand for surveillance

Customer continuity matters because number resources are embedded in services. An ISP's address blocks can support access subscribers, enterprise circuits, hosting clients, voice platforms, security services and internal infrastructure. If those obligations move to a successor, leaving the resources behind may break the business that the legal transaction intended to preserve.

Registries therefore reasonably ask whether customers moved. The evidence can be proportionate. A signed transaction schedule can identify the transferred business. Audited accounts can show revenue continuity. Notices can show that customers were informed of a new contracting entity. A sample of redacted invoices or assignment records can connect prefixes to service. Network diagrams and routing observations can corroborate ongoing use.

The registry rarely needs the identity and contract terms of every customer. A complete list creates privacy, security and commercial risks. It can reveal vulnerable networks, negotiated pricing and market strategy. The proof question is whether a continuing customer base exists and uses the resources, not who every end user is.

Routing evidence is similarly bounded. An unchanged origin ASN supports operational continuity but does not prove legal succession. A changed origin can reflect a planned network integration rather than a resource sale. Geolocation, reverse DNS and abuse contacts may lag. The evidence works as a mosaic.

Customer continuity also helps identify a disguised sale. If no customers, staff, equipment or service obligations move and the resource is immediately announced by an unrelated network, the corporate form deserves closer review. That does not make the route a title record. It gives the registry a fact-based reason to ask for the commercial-transfer evidence rather than accepting a thin reorganisation story.

The disciplined rule is data minimisation with corroboration. Ask enough to establish the operating link. Do not turn succession review into customer surveillance.

Tax structure and legal form are context, not verdicts

Corporate groups reorganise for reasons that have little to do with IPv4. They consolidate tax residency, respond to licensing rules, ring-fence liability, prepare financing, simplify reporting, place assets near staff or comply with foreign-ownership restrictions. These motives can produce consideration, intercompany balances and valuation entries even when ultimate control remains constant.

A registry should not treat a booked price as proof of an arm's-length address sale. Intercompany transfers often require values for accounting or tax purposes. Conversely, a zero-price transfer can still move valuable resources to an unrelated party. Consideration is one factor, not the classifier.

Legal form also varies. Some jurisdictions provide universal succession in a merger; others require asset-specific transfer steps. A conversion may continue the same legal person in one country and create a successor in another. A branch is not a subsidiary. A partnership conversion may have different effects from a corporate amalgamation. The registry should ask for a concise legal-effect statement supported by the relevant official instrument rather than applying the law of its own headquarters to every foreign event.

Tax residence should be kept separate from incorporation and network location. A group may have a parent in one country, a contracting subsidiary in another, infrastructure in several RIR regions and customers worldwide. None of those facts alone decides the correct registry. Current regional policy may require a service nexus, membership or sponsoring relationship. Those requirements should be applied to the resulting holder without pretending that a tax migration itself sold the resources.

Registries need not endorse a group's tax planning. They need to keep their records true. If a lawful reorganisation makes a different entity the successor, the registry verifies that fact and applies its published service rules. Tax authorities, courts and regulators retain their own roles.

Cross-border groups need a two-map review

A cross-border reorganisation should be reviewed with two maps: the legal-control map and the operational-resource map.

The legal map shows parents, subsidiaries, ownership percentages, jurisdictions, registration numbers and the sequence of merger, contribution, conversion or spinoff steps. It identifies where ultimate control changed and where it remained. It also identifies the entity authorised to sign at each step.

The operational map shows prefixes, origin ASes, facilities, customers, engineering teams, route authorisations, reverse DNS, abuse contacts and regional network elements. It identifies which business uses each block and where the resulting holder will operate.

The maps need not be identical. A holding company can control a network it does not operate. An operating subsidiary can use resources registered to a parent under an accepted structure. The purpose is to make the difference visible. A registry that sees only the legal map may mistake a tax-driven migration for a market sale. One that sees only BGP may miss that the old operator ceased to exist.

For inter-RIR movement, each registry should state the facts it is responsible for. The source verifies the existing holder, chain and release. The destination verifies the recipient relationship and regional conditions. Both agree on the resource set, event category and effective date. The group receives a statement of any status, fee, certification or retransfer consequence before completion.

ARIN's rule allowing a surviving entity outside its region to continue holding pre-reorganisation resources is a useful example of separating existing continuity from new-resource eligibility. RIPE NCC requires an active regional network element for many incoming transfers but treats qualifying legacy status separately. APNIC requires a destination account. These differences are service conditions, not evidence that the underlying corporate event was a sale.

Cross-border complexity justifies more coordination, not more economic discretion. The registries should prove one coherent successor record and let tax, company and competition law govern the corporate transaction.

A spinoff deserves a succession lane of its own

Spinoffs expose the weakness of a binary “same company or sale” model. A parent separates a division into a new independent company. Existing shareholders may receive shares in the new entity. Employees, facilities, customers, contracts, routers and prefixes move with the business. No outside buyer may pay the parent for the address blocks.

Control after separation is not identical. The new company has its own board, creditors and strategy. Treating the event as a mere rename would be false. Treating it as an arm's-length address sale can be equally false.

The succession test should ask whether the addresses are necessary infrastructure of the separated business and whether they moved with it under the demerger instruments. Evidence can include the separation agreement, public information statement, court or regulator approval, allocation schedules, customer transfer plan, employee transfer and network cutover plan. The resource schedule should identify which blocks follow which services.

Partial blocks create an operational issue. A parent may use one allocation across both retained and spun-off businesses. The registry should support technically valid subdivision where policy permits, while the companies renumber or reorganise assignments. It should not force the entire block to one side merely because the historical record has one line, and it should not invent a right to fragment below safe operational boundaries.

Post-spinoff restrictions should reflect the event. An immediate resale of the received blocks to a third party may justify closer examination because it weakens the claimed business link. Continued use by the spun-off network supports succession. A time-limited retransfer restriction can deter a disguised sale, but it should permit further genuine mergers or restructurings and should be stated before completion.

Spinoffs are where customer continuity is most valuable. If customers continue receiving the same service from the separated business, the registry's priority should be an accurate, safe handover. Scarcity policy should not interrupt the separation by demanding that the new operator re-prove its network as if it were an unrelated greenfield buyer.

Fraud controls should target disguise, not corporate complexity itself

A simplified continuity lane can be abused. Parties may create a shell merger, transfer one nominal asset, or sell shares in a dormant registrant to avoid market-transfer requirements. That risk is real.

The answer is a substance test with targeted red flags. Did the resource-using business move? Did ultimate control change to an unrelated party? Were addresses separately marketed or valued as the principal asset? Did customers, staff and equipment remain with the source? Was the recipient recently formed with no operational history? Did the prefixes change origin immediately to an unrelated network? Are the corporate documents final and filed? Is there inconsistent information across registries?

Red flags trigger additional evidence, not automatic condemnation. A newly formed spinoff can have no history and still be legitimate. A route can move immediately because the network cutover was carefully planned. A block can be valuable without being the sole transaction purpose. The reviewer should state which inconsistency requires explanation.

Anti-avoidance should also work in the other direction. A registry should not classify a genuine sale as a reorganisation simply because the parties acquired a small piece of equipment with the addresses. The operating link must be substantial enough to explain why the resources follow the business.

Random and risk-based post-completion audits can protect the lane. The registry can verify that the successor remains connected to the declared business and that no immediate contradictory transfer occurred. Aggregate findings should be published: how many continuity cases were reclassified, what red flags mattered and how often decisions were reversed. Private documents remain protected.

The design principle is proportionality. Corporate complexity is common in global networks. It is not itself evidence of evasion. Fraud controls should make false stories costly without making every genuine group change wait in the same queue as a contested market sale.

Fees, waiting periods and statistics should follow the event category

Administrative classification affects money and time. APNIC charges can change when resources move to a new account. ARIN charges a transfer processing fee and requires the future service relationship. RIPE NCC transfers are free, but scarce resources can become subject to a 24-month restriction after a business-structure change. LACNIC and AFRINIC can connect the review to utilisation consequences.

These effects should be justified by cost and risk. A pure name correction should cost little and complete quickly. A same-holder account consolidation should not attract the evidentiary burden of an unrelated transaction. A multi-step cross-border succession may reasonably cost more to verify. An arm's-length sale with conflicting claims requires the most scrutiny.

Waiting periods need event-specific exceptions. If a group reorganises twice within a year, the second correction may be necessary because the first legal entity merged again. Blocking the update would leave a false record. RIPE NCC's policy expressly permits further merger or acquisition changes during the 24-month restriction. That is the right distinction: restrict discretionary retransfer if policy chooses, but do not prevent accurate recording of later succession.

Statistics must preserve the same taxonomy. Public transfer logs should include at least: legal-name change, same-entity conversion, same-holder consolidation, common-control reorganisation, merger or acquisition of operating business, spinoff or demerger, arm's-length resource sale, court or insolvency succession, and inter-RIR movement. Some fields may be combined for privacy where volumes are low, but corporate changes should not be counted as market sales.

Misclassification distorts price and liquidity analysis. A thousand addresses moved in an internal merger did not clear an open market. Their appearance in a transfer log says the registry changed the recognised holder, not that a buyer paid a market price. Analysts, policymakers and registries should stop using one administrative verb as evidence of one economic event.

A three-lane registry is enough

The practical reform does not require a corporate-law tribunal inside every RIR. It requires three lanes and a clear escalation rule.

Lane one: identity maintenance. Use for pure legal-name changes, contact corrections and same-entity conversions where official evidence establishes continuity. Verify the government record, align the existing agreement if needed and update promptly. Do not publish the case as a market transfer.

Lane two: operational succession. Use for mergers, amalgamations, common-control reorganisations, genuine business acquisitions, spinoffs and court-ordered succession where the resource-using business moves. Verify the chain, authority, assets or customers, resulting holder and service relationship. Do not apply an ordinary buyer needs test merely because the legal entity changes.

Lane three: market disposition. Use where resources move to an unrelated buyer independently or where the operating-business link is too weak to explain the change. Apply the published market-transfer rules, recipient conditions, inter-RIR requirements and transaction finality controls.

Escalation occurs when facts contradict the selected lane. A name change that produces a new registration number and extinguishes the old entity may move to succession. A supposed reorganisation with no business continuity may move to market disposition. A market sale whose source has dissolved may first need a succession step to establish the authorised seller.

The applicant should see the reason for reclassification and have an opportunity to supply evidence or seek review. The registry should not benefit from choosing the lane with the highest fee or broadest discretion. Service targets and fee schedules should be public by lane.

This model is demanding where risk exists and simple where it does not. It preserves the registry's essential interests: authentic parties, one coherent record, lawful restrictions and accountable future service. It removes interests the registry does not need: judging tax motives, re-pricing internal capital or deciding whether a board should have reorganised its subsidiaries.

The record should follow the enterprise without governing it

Corporate life is dynamic. Operators rename, convert, merge, separate, relocate, acquire businesses and rationalise groups. The registry cannot insist that the legal person named in an old allocation remain frozen forever. Nor can it accept every new claimant on a polished group chart.

The middle path is evidence-led succession. Establish the predecessor. Trace every legal step. Identify ultimate control before and after. Show whether customers, staff, equipment and obligations moved. Verify the entity that will maintain the future record. Apply the resulting service terms openly. Protect routing continuity. Record the event category accurately.

Current RIR practice already contains pieces of this design. ARIN exempts 8.2 succession from the needs test and accepts several forms of official evidence. APNIC and RIPE NCC separate pure name changes from entity transfers. RIPE NCC recognises same-member consolidation without a bilateral transfer agreement. LACNIC and AFRINIC look for asset and customer continuity, although their utilisation review can become an unnecessary reallocation of existing capital.

The next step is to make the distinction systematic. Same economic control and continuing operations should create a presumption of simplified verification. A spinoff that carries a real business should receive an operational-succession review. An unrelated resource buyer should use the market lane. Red flags can rebut the presumption; labels cannot decide it.

The registry is not being asked to ignore scarcity. It is being asked to identify the event before exercising scarcity power. A corporate reorganisation does not place addresses back in a free pool and invite an administrator to choose a better owner. It places a duty on the registry to keep the record aligned with the legal and operational enterprise that continues.

That duty is narrow and consequential. Performed well, it preserves customer service, reduces fraud and makes corporate transactions legible. Performed badly, it lets an administrative correction become leverage over capital that never entered the market.

Corporate form can change at midnight. The network may continue without a dropped packet. The registry should be able to tell the difference between that continuity and a sale.

Sources