Summary

  • Today an operator's registry relationship, records, membership rights and regional governance are closely bundled. A disputed board election can therefore appear to place every route to accountability inside the institution whose leadership is contested.
  • Portability would mean changing the provider responsible for maintaining and authenticating an unchanged holder's registration while preserving prefixes, ASNs and routing relationships. It is different from transferring resources to a new holder or moving addresses between regions.
  • Domain-registrar transfers and telephone-number portability show the institutional ingredients: a shared authoritative layer, authenticated requests, gaining and losing provider duties, time limits, locks, dispute resolution, continuity and auditable updates. Internet number resources introduce distinct scarcity, routing-security and policy risks.
  • A safe design would require recognised providers, common record semantics, a neutral trust anchor, anti-hijack controls, reversible emergency states, public performance data and a provider-of-last-resort. Portability should supplement elections and public duties, not permit evasion of valid policy.

Why one election can feel like everything

A regional registry board does not configure every route, own every network or decide every address policy alone. Yet its choices reach deep into institutional life. The board supervises the corporation that maintains registration records, collects fees, employs staff, operates security services, represents the institution and responds to crisis. When the board election is disputed, operators can feel that the referee, record keeper and service provider all sit behind the same contested door.

Voice is the traditional answer. Members nominate, vote, question, petition and use meeting rights. Open communities discuss number policy. Courts and recognised coordination bodies provide additional checks in exceptional circumstances. These mechanisms matter, but they mostly require repairing or persuading the incumbent institution. An operator dissatisfied with registry service cannot ordinarily move the same registration to a competing recognised provider as easily as a domain holder can change registrar.

Exit would change the bargaining structure. It would not make governance optional. It would give a resource holder a bounded ability to choose who performs specified registration-service functions, while a shared authoritative system preserves uniqueness and policy. A board election would continue to determine the leadership of a major provider and regional institution. It would become less existential because losing confidence in that board would not necessarily mean losing every practical route to accurate records and secure service.

This is a counterfactual, not a description of a service already operating. Designing portability for Internet number registrations would be harder than naming the principle. The value of the thought experiment is that it forces current governance to identify which powers truly require a single regional organisation and which persist only because service, authority and representation have historically been bundled.

Portability is not a transfer of the resource

The first distinction is decisive. Existing number-resource transfers change registration rights between organisations, sometimes across RIR regions, under policy. ARIN's transfer guide describes authorised accounts, merger and acquisition cases, specified recipients, inter-RIR coordination, agreements, fees and record maintenance. Those processes answer who holds registration rights.

Registry-service portability would answer a different question: which recognised provider maintains the authoritative service relationship for the same holder and the same resources? The organisation does not sell its prefix. The ASN does not acquire a new operator. Routing announcements do not need to change merely because the service provider changes. The holder changes the administrative intermediary while the durable registration remains continuous.

This resembles changing a domain registrar without changing the registrant or domain, but the analogy has limits. Internet number resources are allocated under regional policy, carry routing-security entities and may have legacy or contractual status. They cannot be treated as ordinary consumer accounts. A portable design must preserve policy history, holder identity, chain of registration and the distinction between use, registration and property.

The terminology should therefore be precise. “Porting a registration service” is safer than “moving an IP block.” The first suggests continuity under common authority. The second can be mistaken for reallocation, sale or routing relocation. Governance will fail if the public cannot tell what changed.

Domain transfers show how exit can be rule-bound

ICANN describes its Transfer Policy as supporting competition by giving domain holders a straightforward procedure to transfer registrations between accredited registrars. The policy does not allow a domain to leave the coordinated DNS. It changes the contracted intermediary under shared requirements.

The detailed policy assigns duties to gaining and losing registrars, defines authorisation, provides denial grounds, uses time periods and addresses disputes. Portability is not an unreviewed database edit. It is a governed transaction whose legitimacy depends on identity, consent and consistent implementation.

That design changes accountability. A registrant facing poor service can leave, subject to valid locks and safeguards. Providers compete on support, tools and price while remaining bound to common obligations. The central authority can enforce rules without becoming the sole retail service point. Elections to one provider's board, where such a board exists, do not determine the registrant's only possible service relationship.

Number registrations cannot copy the domain rules. Address policy, RPKI, reverse DNS, route objects, sanctions, fees and regional recognition differ. The comparator proves a narrower proposition: a globally coordinated identifier can remain unique while service-provider choice exists. It demonstrates that authoritative coordination and portable intermediaries are not logical opposites.

Telephone numbers show operational continuity

Telephone-number portability offers another useful comparison. The Number Portability Administration Center describes a central system supporting local number portability in the United States and distributing changes to operational systems. A subscriber can change service provider while keeping the number, and network systems learn where service now resides.

Again, the analogy is institutional rather than technical. An IP prefix participates in routing differently from a telephone number. The resource holder controls announcements through network arrangements, not a central call-routing update. Still, number portability shows how durable identifiers, provider competition and a shared authoritative record can coexist. It also shows that portability requires operational coordination after the customer makes a choice.

The comparison highlights a key design decision. A portable number registry should not require the new provider to become the network's transit provider or host. Registry service concerns record stewardship, authentication and related functions. Keeping it separate from connectivity prevents the portability right from becoming a forced network migration.

Operational continuity must be measured. A port should not make accurate public registration disappear, invalidate properly issued route authorisations without replacement or interrupt reverse delegation. The transition needs an agreed state in which old and new providers cannot both make conflicting authoritative changes.

A neutral trust anchor is indispensable

Competition among providers creates value only if the world can still identify one authoritative state. Without a neutral trust anchor, portability risks split-brain records: two providers claim responsibility, update different data and issue conflicting attestations. Networks and security systems would not know which to trust.

The anchor could be operated by a recognised coordinating body or distributed under jointly governed controls. It would record provider of record, holder identifier, resource set, status and transition events. Providers would maintain richer service records and submit authenticated updates. The anchor would not need to centralise every support interaction, but it would make authority unambiguous.

Governance of the anchor is more important than its software. Who appoints its overseers? Which providers and affected parties participate? How are emergency changes reviewed? What happens if a provider fails or the anchor itself is captured? Portability merely moves monopoly risk upward if the shared layer has no credible accountability.

The governing body should publish decisions, security assurance, uptime, incident reports and provider treatment. Its mandate should be narrow: preserve uniqueness, authenticate provider changes, enforce baseline obligations and coordinate continuity. It should not use technical control to create unreviewable policy.

Recognition prevents a race to the bottom

Anyone should not be able to declare themselves a portable registry provider and alter global records. Providers need recognition based on legal capacity, security, financial resilience, technical competence, data protection, audit access and commitment to common policy. Entry should be possible but not casual.

The NRO's RIR Governance Document addresses recognition, operation and possible derecognition of regional registries. A portable-provider regime would need a related but distinct category. A service provider would not automatically become an RIR or acquire authority to write regional policy.

Recognition criteria should be public and reviewable. Incumbent RIRs should not be able to exclude competitors merely because portability threatens revenue. Equally, applicants should not gain entry through political sponsorship without evidence of capability. Independent technical assessment, consultation and reasoned decisions can balance openness and safety.

Ongoing obligations matter more than admission. Providers should publish service performance, security incidents, ownership, conflicts, fees, complaint outcomes and continuity reserves. Serious breach can trigger remediation, transfer suspension or derecognition. Customers need enough warning and a provider-of-last-resort plan.

The losing provider cannot hold the record hostage

Portability fails if the incumbent provider can delay every request, demand invented documents or degrade service during departure. Rules need objective grounds for refusal and firm deadlines. A provider may reject an unauthorised request, a resource under a valid dispute or a transfer blocked by a narrowly defined security hold. It should not refuse because the customer criticised the board or owes an unrelated contested fee.

The gaining provider should verify holder identity and authority. The losing provider should receive notice and an opportunity to flag defined risks. The holder should confirm through an independent channel. The trust anchor should record each step and complete automatically when conditions are satisfied, unless a review body imposes a hold.

Locks can protect against hijacking after credential changes or suspicious recovery. They must be time-limited, visible and appealable. A permanent “security” lock controlled by the losing provider would recreate captivity. Emergency holds should produce independent review and audit trails.

Fees should reflect reasonable processing and not function as exit penalties. Public comparisons can expose providers with unusual delays or denials. A customer who leaves should receive an export of relevant records and history in a common format, while the authoritative transition occurs through the shared layer rather than a private file handoff.

Fraud is the strongest argument against careless portability

An attacker who ports a registration relationship could change contacts, reverse delegation or routing-security material and make a hijack appear legitimate. The harm could exceed ordinary account takeover because multiple relying systems may trust the new provider. Security cannot be an afterthought added after competition goals.

High-risk actions should use strong multifactor authentication, verified organisational authority and out-of-band confirmation. Resource holders can pre-register recovery trustees or require multiple approvers. Large or critical resource sets may use longer notice and a public pending state. Providers should support hardware-backed credentials and protect recovery from social engineering.

The system should notify current contacts, technical operators and designated security contacts without revealing sensitive information. A short reversible period can permit emergency restoration when fraud is proven. Reversal authority must be narrow and logged so it cannot become political interference.

Historical records help detect anomalies. A sudden provider change accompanied by contact and routing-authorisation changes deserves enhanced review. Risk scoring can prioritise human examination, but opaque automation should not deny legitimate exit. Hold reasons and appeal paths remain necessary.

Security comparisons should be public. Providers can report attempted fraudulent ports, holds, confirmed incidents and response times in aggregate. A portability regime earns trust by showing how attacks were contained, not by claiming they never happen.

Policy must follow the resource, not the preferred provider

Provider choice cannot permit a holder to evade valid number-resource policy. Otherwise organisations would shop for the provider with the weakest needs review, transfer controls, contact accuracy or abuse response. Portability would become regulatory arbitrage rather than accountability.

Common baseline policy should attach to the registration and applicable recognised framework. Providers can compete on service, support, tooling, language, assurance and price. They should not contradict authoritative allocation history or invent ownership rights. Where regional policy legitimately differs, the design must state which rules follow service region, holder, resource origin or provider.

This is one of the hardest questions. A provider operating across regions might offer consistent service while resources remain subject to origin-region obligations. Cross-regional portability could weaken the connection between affected communities and policy. An initial design may therefore allow provider choice only among recognised providers committed to the same regional policy, expanding after evidence.

Policy disputes should use existing or jointly designed appeals, not provider discretion. A provider can help a customer navigate rules but cannot promise exemption. Public enforcement data can reveal whether one provider interprets requirements unusually leniently or harshly.

Elections would change, not disappear

If members can leave a provider, its board still controls budgets, security, staff and service quality. Elections remain a primary voice mechanism for those who stay. Portability changes the consequence of losing: a member unable to reform the provider may transfer service rather than remain captive.

That threat can discipline boards. Fee increases, poor support or opaque security decisions may produce measurable departures. Directors can no longer assume that every resource holder in a service region must maintain the same provider relationship. Performance becomes part of electoral debate.

Exit can also weaken voice. The most dissatisfied members may leave, reducing pressure for reform and leaving less mobile members behind. Wealthy operators may maintain sophisticated providers while small networks remain with a provider of last resort. Elections could become narrower if portability drains engaged entities.

Governance should therefore preserve member rights during and after transition. A member may choose to retain association membership even if another provider serves the registration, or a separate regional public-interest membership could exist. Voting eligibility should not be manipulated to punish exit. The design must decide whether corporate membership funds services, policy participation, oversight or all three.

Portability makes these relationships explicit. Current bundling hides them. An election becomes less existential only if exit is real and voice remains available where collective policy still affects everyone.

Provider failure needs an automatic answer

A provider can become insolvent, lose accreditation, suffer an attack or abandon service. Portability must work when the customer cannot obtain cooperation. The trust anchor should support bulk emergency transfer to a provider of last resort, with records and cryptographic material preserved under predetermined controls.

Continuity reserves or insurance can fund the transition. Providers should maintain tested escrow of necessary service data, not private keys that create new attack risk. Regular exercises can demonstrate that records are exportable and that another provider can assume responsibility without changing resource holders.

The provider of last resort should be neutral and temporary. It should preserve records and essential functions, notify holders and offer a period to choose a new provider. It should not exploit failure to capture customers permanently. Fees and governance should be transparent.

Derecognition decisions require due process but cannot wait while authoritative data decays. Interim restrictions can block risky changes while allowing read access and urgent security maintenance. Independent oversight should review both intervention and restoration.

This continuity architecture may be the strongest public benefit of portability. Current regional concentration can make institutional failure a systemic event. Multiple providers with a common recovery layer create redundancy, provided concentration does not simply reappear among two global companies.

Competition can concentrate too

Choice does not guarantee diversity. Large providers may use scale, low prices and integrated services to dominate. Operators may choose the same provider because peers do, creating a new single point of failure. Private equity or state-linked ownership can consolidate nominal competitors.

Recognition should require ownership disclosure and monitor market share. Merger review can consider systemic resilience, not only price. The trust anchor can publish provider concentration by resource count and criticality without exposing sensitive customer details. Procurement by large networks should consider diversity.

Interoperability reduces lock-in. Common exports, standard authentication and maximum transfer times keep a successful provider from closing the door after gaining scale. Providers can innovate above the baseline but must not make essential records proprietary.

A public or cooperative option may serve small operators and preserve competitive pressure. Incumbent RIRs could become providers within the new regime, using their expertise and member governance. Portability need not destroy regional institutions; it can require them to earn service relationships while continuing defined coordination duties.

NRS illustrates demand, not completed authority

The Number Resource Society presents membership and representation offerings on its public pages. Its terms describe individual and corporate membership, and its network-member page describes organisations that have appointed it in relation to RIR governance. These activities show demand for assistance and collective voice outside ordinary direct participation.

They do not establish that NRS is a recognised alternate RIR, operates a globally interoperable registry-service port, or can alter the authoritative registration chain. A power of attorney for governance matters is not portability. Membership in an advocacy or service organisation is not transfer of registry responsibility.

That boundary is essential because future design should not be marketed as present fact. NRS can advocate a model, organise members or offer support within lawful authority. The operational proposition evaluated here would require recognition, shared technical controls, provider obligations and acceptance across the number registry system.

The gap is analytically useful. It shows that an organisation can aggregate dissatisfaction without yet supplying exit. Elections remain existential when representation by another body cannot change the service relationship. A credible reform agenda must move from rhetoric about choice to testable institutional architecture.

A phased experiment would be safer than a revolution

Portability should begin with a limited pilot. Entities could volunteer low-risk registrations, remain under the same regional policy and choose among a small set of independently assessed providers. The anchor would record provider changes while incumbent records remain synchronised for observation. Routing and holder identity would not change.

The pilot should test authentication, transfer time, denial, reversal, data quality, RPKI continuity, reverse delegation, support and dispute handling. Independent security teams should attempt fraudulent ports. Operators should rehearse provider failure. Results, including failures, should be public.

No pilot should rely on irreversible production changes without recovery. Parallel verification can compare old and new records before authority moves. A narrow resource set and explicit stop conditions protect the wider system. Entities should understand rights and residual risks.

Governance experiments matter as much as technology. The pilot board should include operators, incumbents, prospective providers, security specialists and affected non-members. Conflicts and decisions should be published. An appeal body should exist before the first disputed request.

Expansion would depend on evidence: low fraud, accurate records, acceptable continuity, real provider choice and no policy evasion. Failure could justify redesign or abandonment. Portability is a means to accountability, not an article of faith.

Measure whether exit improves accountability

Success is not the number of ports. A healthy market may have low switching because providers perform well. The important measures include transfer completion time, improper denial, fraud, service continuity, correction quality, provider concentration, cost and user confidence.

Governance measures should ask whether boards respond faster, disclose more and face more competitive elections. Does the possibility of exit improve service, or do providers focus only on large accounts? Do departing members retain policy voice? Are small networks stranded? Does the provider of last resort become a neglected warehouse?

Reasons for switching can be collected voluntarily in broad categories: price, support, security, language, governance, consolidation or organisational change. Confidential surveys can supplement public totals. Providers should not receive individual political profiles.

The anchor and recognition body need review too. If every dispute escalates centrally, portability may have added bureaucracy without distributing power. If the central body consistently favours incumbents, competition is cosmetic. Appeals, audit and stakeholder participation should measure that layer.

Common records need common meaning

A port can be technically successful and substantively wrong if providers interpret fields differently. Holder identity, authorised contacts, resource status, transfer restrictions, reverse delegation, routing-security authority and historical notes need common definitions. Otherwise the gaining provider may import a record that looks complete while silently changing its legal or operational meaning.

The common layer should define mandatory fields, evidence classes, timestamps and provenance. It should distinguish a fact supplied by the holder from one verified by a provider or inherited from allocation history. Corrections should preserve prior state and authority. Providers can add services and presentation, but they cannot rewrite the durable record to make migration easier.

Data quality disputes need a route separate from provider transfer. A holder should not be forced to accept an inaccurate record before leaving, yet portability should not become a way to erase a legitimate restriction. The trust anchor can mark contested fields, preserve both claims and allow the new provider to serve unaffected functions while an independent reviewer decides.

Language and transliteration also matter. Legal names can appear in several scripts; corporate forms differ; contacts move. Common meaning does not require English-only public records. It requires stable identifiers, faithful display and a clear authoritative form. Privacy controls should define which data are public, restricted to providers or available only to reviewers.

Interoperability testing should include meaning, not merely file transfer. Auditors can port sample records between every provider pair, compare resulting authority and verify that no field gains or loses effect. Published conformance results let operators choose providers based on demonstrated compatibility.

Fees must not recreate captivity

Provider competition can lower prices, but the shared functions still need funding. The trust anchor, recognition body, appeals, security coordination and last-resort service produce collective benefits. If financed entirely by port fees, they may discourage exit. If financed by one incumbent, independence becomes doubtful.

A transparent common levy based on resource-service categories, provider market share or a mixed formula could fund shared duties. The amount and budget should be governed separately from individual providers. Operators should see which charge pays for their provider and which supports collective infrastructure. Cross-subsidy for small networks can be explicit rather than hidden.

Losing providers should not impose early-termination penalties unrelated to unrecovered, disclosed costs. Outstanding undisputed service fees may remain collectible through ordinary means without freezing authoritative records indefinitely. Disputed invoices should go to a rapid process. Essential registration accuracy should not become collateral for a commercial claim.

Gaining providers may offer discounts, but inducements should not encourage insecure bulk ports or misrepresent policy. Contracts need clear renewal, data export and failure terms. Providers should publish total prices in comparable categories so low headline fees do not conceal charges for RPKI, reverse delegation, support or exit.

Affordability is a governance measure. If only large holders can move, portability will increase inequality. A standard low-cost transfer, fee waivers for provider failure and support for small operators should be part of recognition. The right to exit is credible only when those most dependent on a provider can exercise it.

Appeals must move faster than operational harm

Disputes over a port can affect security and service in hours, while ordinary corporate or judicial review may take months. The system needs a specialised rapid appeal with authority to hold, complete or reverse a transaction temporarily. Its scope should be narrow enough to avoid becoming a shadow policymaker.

The first tier can handle documentary questions: authority of the requester, valid lock, provider deadline and notice. A second independent panel can hear contested fraud, ownership or policy restrictions. Courts remain available where law requires, but the operational state should not drift while parties wait.

Every interim order should identify the safest state. Sometimes that means preserving the old provider; sometimes the old provider has failed and the new one must maintain service under restriction. The decision should protect routing-security and contact continuity without deciding ultimate registration rights prematurely.

Appeal statistics should show who succeeds, delay, reasons and provider patterns. A provider with repeated unjustified denials needs supervision. A gaining provider submitting weak authorisations needs remediation. Publication can omit holder identities while exposing institutional behaviour.

Costs should not deter legitimate challenge. Routine appeals can be free or low-cost, with penalties only for demonstrated abuse. Providers, not individual complainants, should fund the standing capacity through the common levy. Fast review is part of the portability service, not an optional legal luxury.

Regional knowledge should remain a public asset

Incumbent RIRs hold decades of knowledge about local law, member practice, network development, language and operational history. Portability should not scatter that capacity into private companies or make it available only to customers of the largest provider. Some functions remain regional public goods even in a multi-provider environment.

Policy facilitation, statistics, training, coordination with governments and support for developing networks may need collective funding and governance. An operator choosing another service provider should still benefit from accurate regional data and participate in open policy. Providers can contribute fees and expertise without controlling the forum in proportion to market share.

Historical records require stewardship beyond customer contracts. Allocation provenance, policy versions and public statistics should survive provider entry and exit. A neutral archive can preserve them. Providers should submit required events while protecting personal and confidential data.

Regional institutions could evolve rather than vanish. An RIR might operate the trust anchor under independent oversight, serve as one provider, facilitate policy and maintain last-resort capacity through separated accounts and decision bodies. Separation would prevent the incumbent provider from using anchor control against competitors.

The objective is not to replace public-minded associations with vendors. It is to distinguish contestable service from shared stewardship. Regional knowledge remains accountable to the broader community, while operators gain choice over the organisation handling their daily registration relationship.

Exit is not a substitute for duty

Markets often answer poor service with “leave.” That response is limited public evidence where accurate records, routing security and regional coordination produce public benefits. A small operator may lack capacity to compare providers. A country's networks cannot escape systemic failure one account at a time. Providers must meet duties regardless of customer mobility.

Portability also cannot justify neglecting elections. Boards set provider strategy and influence collective institutions. Members need fair ballots, candidate transparency, conflict controls and remedies. Exit works best as leverage behind voice, not as an invitation to abandon it.

Some decisions must remain common. Uniqueness of resource registration, baseline security, authoritative policy and crisis coordination cannot fragment into consumer preference. The design challenge is to locate those functions in accountable shared institutions while opening contestable service functions to choice.

Public-interest obligations should follow every recognised provider. Accurate contacts, privacy, security cooperation, non-discrimination and continuity are not optional premium features. A holder should not be able to choose a provider that hides abuse or fabricates registration history.

The election after portability

Imagine a board election in which members assess fees, security and leadership knowing they can move registration service under common rules. Candidates could no longer frame every criticism as a threat to regional continuity. Challengers could propose better service while the trust anchor protects the durable record. Incumbents could defend performance with measurable retention and quality.

The campaign would still matter. The provider might serve a large share of the region, operate important systems and contribute to policy coordination. A bad board could cause real harm. But the consequence of defeat for dissatisfied operators would not be absolute dependence for another term.

Exit data would sharpen debate. Directors could see whether members left after delays, price changes or governance failures. Departures would not prove the leavers were right, but they would be harder to dismiss than survey silence. Providers could win members back through verifiable improvement.

Portability might also expose the value of incumbent RIRs. Many operators could stay because regional expertise, trust and member control outperform alternatives. Choice would turn that loyalty from necessity into evidence. A strong RIR need not fear an exit right designed with common safeguards.

Exit should be possible without political declaration

A holder should not have to accuse a board of failure before moving providers. Portability works best as an ordinary administrative right exercised for service, language, price, security or organisational preference. Requiring a statement of grievance would chill exit, invite retaliation and turn every transfer into a referendum on leadership.

Providers and the coordinating body can collect voluntary reasons in broad categories for accountability analysis. Individual answers should remain confidential and should never affect transfer approval. Aggregate trends can inform elections: a sustained rise in departures for delayed support or weak security deserves attention. No director should receive a list of political opponents disguised as customer research.

Ordinary exit also protects the legitimacy of sanctions against abuse. If all ports are treated as hostile, a valid security hold looks retaliatory. When routine requests proceed automatically under clear rules, exceptional intervention becomes easier to justify and audit. The institution can show the precise risk rather than rely on suspicion about motive.

Providers should be prohibited from degrading service, changing support priority or restricting member participation after notice of departure. The losing relationship continues until the authoritative change completes. Data exports, final invoices and security notifications should follow standard timing. A cooling-off offer may be permitted, but it cannot delay the port or exploit confidential dispute information.

Depoliticised exit does not remove political consequences. Directors will examine why members leave, candidates will debate performance and providers will respond competitively. The difference is that the operator controls whether its own reason becomes public. Choice becomes infrastructure rather than a loyalty test, which is exactly how it can discipline governance without destabilising every election.

Separate the record from the ruler

The central proposition is constitutional rather than commercial. A durable Internet number registration should not depend entirely on confidence in one corporate board. The authoritative record can remain coordinated while the service relationship becomes portable. Elections can govern providers without making each contest a referendum on whether operators retain usable institutional continuity.

This separation demands more governance, not less: recognition, a neutral anchor, common policy, authentication, locks, appeals, security reporting, concentration controls and last-resort service. Poor design could enable hijacking or arbitrage. Good intentions are not enough.

The comparisons show possibility, not equivalence. Domain transfers preserve names across registrars. Telephone portability preserves numbers across carriers. Existing RIR transfers preserve controlled changes of holder. A future registry-service port would need its own rules because Internet number resources connect registration, routing and public coordination in distinct ways.

NRS-style advocacy helps place exit on the agenda, but authority must be demonstrated through recognised operation. Until then, the proposal should be assessed as a future institutional choice. Its strongest promise is not convenience. It is proportionality: no single board election should carry every service, record and accountability consequence for an operator that has no safe alternative.

Voice without exit can become pleading. Exit without shared duty can become fragmentation. Portable registries would be worthwhile only if they join the two: members continue to govern collective obligations, while resource holders can change the provider that serves them without changing who they are or what their networks announce. That balance would make elections less existential and governance more real.

The threshold for adoption should therefore be demanding and public. Proponents should demonstrate safer authentication, continuity under provider failure, consistent policy, affordable access and a governable trust anchor before asking operators to depend on the model. Opponents should identify testable risks rather than defend historical bundling as inevitable. A staged trial can then produce evidence capable of changing either side's view. The final measure is not whether portability sounds competitive, but whether it preserves the common number registry while giving operators a credible, reversible and non-punitive choice of steward.