Summary
- Today, an operator's relationship with the registry, the records, member rights and regional governance are tightly linked. A contested board election can therefore appear to concentrate all lines of accountability inside the institution whose leadership is contested.
- Portability would mean changing the provider responsible for maintaining and authenticating the record of an unchanged holder, while preserving prefixes, ASNs and routing relationships. This differs 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 authority layer, authenticated requests, duties of the losing and gaining provider, timeframes, locks, dispute resolution, continuity, and audited updates. Internet number resources introduce distinct risks of scarcity, routing security, and policy.
- A safe design would require recognised providers, common record semantics, a neutral trust anchor, anti-hijacking controls, reversible emergency states, public performance data, and a provider of last resort. Portability should complement elections and public duties, not enable circumvention of legitimate policies.
Why a single election can seem decisive
A regional registry board does not configure every route, own every network, or single-handedly decide every addressing policy. Yet its choices penetrate deep into institutional life. The board oversees the company that maintains registry records, collects fees, employs staff, runs security services, represents the institution, and responds to crises. When the board election is contested, operators may feel that the arbiter, the record-keeper and the service provider are all behind the same contested door.
Voice is the traditional response. Members nominate, vote, inquire, petition and use their meeting rights. Open communities discuss numbering policy. Courts and recognised coordination bodies provide additional checks in exceptional circumstances. These mechanisms matter, but they generally require repairing or persuading the incumbent institution. An operator unhappy with registry service cannot normally transfer the same record 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 the resource holder a limited ability to choose who performs specific registry-service functions, while a shared authority system preserves uniqueness and policy. A board election would continue to determine the direction of a large provider and the regional institution. It would become less existential because losing confidence in that board would not necessarily mean losing every practical path to accurate records and secure service.
This is a counterfactual hypothesis, not a description of a service already in operation. Designing portability for Internet number records would be harder than stating the principle. The value of this thought experiment is that it forces current governance to identify which powers genuinely require a single regional organisation and which persist only because service, authority and representation have always been bundled.
Portability is not a resource transfer
The first distinction is decisive. Existing transfers of number resources change the registration rights between organisations, sometimes between RIR regions, in accordance with policy. ARIN'stransfer guidedescribes authorised accounts, merger and acquisition cases, specified recipients, inter-RIR coordination, agreements, fees, and record maintenance. These processes answer the question of who holds registration rights.
Registry-service portability would answer a different question: which recognised provider maintains the official 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 simply because the service provider changes. The holder changes the administrative intermediary while the durable record remains continuous.
This resembles changing a domain registrar without changing the holder or the domain, but the analogy has limits. Internet number resources are allocated according to 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, the record chain, and the distinction between use, registration and ownership.
Terminology must therefore be precise. 'Porting a registry service' is safer than 'moving an IP address block'. The former suggests continuity under a common authority. The latter can be confused with reallocation, a sale, or routing movement. Governance will fail if the public cannot discern what has changed.
Domain transfers show exit can be rule-governed
ICANN describes itsTransfer Policyas supporting competition by providing domain holders a simple procedure to transfer registrations between accredited registrars. The policy does not allow a domain to leave the coordinated DNS. It changes the contractual intermediary according to shared requirements.
Thedetailed policyassigns duties to losing and gaining registrars, defines authorisation, provides grounds for refusal, uses time periods, and handles disputes. Portability is not an unexamined database change. It is a rule-governed transaction whose legitimacy depends on identity, consent, and consistent implementation.
This design changes accountability. A holder facing poor service can leave, subject to valid locks and safeguards. Providers compete on support, tools, and price while remaining bound by common obligations. The central authority can enforce rules without becoming the sole point of retail service. A provider's board elections, where such a board exists, do not determine the only service relationship possible for the holder.
Number records cannot copy domain rules. Addressing 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. This demonstrates that authority coordination and portable intermediaries are not logical opposites.
Telephone numbers show operational continuity
Telephone number portability provides another useful comparison. TheNumber Portability Administration Centerdescribes 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 through a central call-routing update. Nevertheless, number portability shows how durable identifiers, provider competition and a shared authority registry can coexist. It also shows that portability requires operational coordination after the customer has chosen.
The comparison highlights a key design decision. A portable number registry should not require the new provider to become the transit provider or network host. The registry service is about record-keeping, authentication and related functions. Separating it from connectivity prevents the right to portability from becoming a forced network migration.
Operational continuity must be measured. A port must not make the accurate public record disappear, invalidate properly issued route authorisations without replacement, or interrupt reverse delegation. The transition requires an agreed state in which the old and new providers cannot both make conflicting official changes.
A neutral trust anchor is essential
Competition among providers creates value only if the world can still identify a single official state. Without a neutral trust anchor, portability risks split-brain records: two providers claim responsibility, update different data, and emit conflicting attestations. Networks and security systems would not know which to trust.
The anchor could be operated by a recognised coordination body or distributed under jointly governed controls. It would record the registered provider, 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 all support interactions, but it would make authority unambiguous.
The anchor's governance matters more than its software. Who appoints its supervisors? Which providers and stakeholders participate? How are emergency changes reviewed? What happens if a provider defaults or if the anchor itself is captured? Portability merely shifts monopoly risk upward if the shared layer lacks credible accountability.
The governing body should publish decisions, security assurance, availability, incident reports, and provider treatment. Its mandate should be narrow: preserve uniqueness, authenticate provider changes, enforce basic obligations, and coordinate continuity. It should not use technical control to create unreviewable policy.
Recognition prevents a race to the bottom
It should not be possible for anyone to declare themselves a portable registry provider and modify 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 informal.
The NRO'sRIR Governance Documentdeals with the recognition, operation and possible loss of recognition 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 draft regional policy.
Recognition criteria should be public and revisable. Incumbent RIRs should not be able to exclude competitors simply because portability threatens their revenue. Likewise, candidates should not gain entry through political sponsorship without demonstrated capacity. Independent technical assessment, consultation, and reasoned decisions can balance openness and security.
Ongoing obligations matter more than admission. Providers should publish service performance, security incidents, ownership, conflicts, fees, complaint outcomes, and continuity reserves. A serious breach may trigger corrective action, suspension of transfers, or loss of recognition. Clients need sufficient notice and a provider-of-last-resort plan.
The losing provider must not hold the record hostage
Portability fails if the incumbent provider can delay every request, demand fabricated documents, or degrade service during departure. Rules need objective reasons for refusal and firm deadlines. A provider may reject an unauthorised request, a resource subject to a valid dispute, or a transfer blocked by a narrowly defined security hold. It should not refuse because the client 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 have 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 met, 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 be subject to 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 refusals. A departing client should receive an export of relevant records and history in a common format, while the official transition occurs through the shared layer rather than private file transfer.
Fraud is the strongest argument against careless portability
An attacker who transfers a registry relationship could modify contacts, reverse delegation, or routing security material and make a hijacking appear legitimate. The harm could exceed an ordinary account takeover because many dependent systems may trust the new provider. Security cannot be an afterthought added after competition goals.
High-risk actions should use strong multi-factor authentication, verified organisational authority, and out-of-band confirmation. Resource holders can pre-register recovery agents or require multiple approvers. Large or critical resource sets may require longer advance notice and a pending public state. Providers should support hardware-based 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 allow emergency restoration when fraud is proven. The reversal authority must be narrow and logged so it does not become political interference.
Historical records help detect anomalies. A sudden provider change accompanied by contact and routing-authorisation changes merits heightened review. Risk scoring can prioritise human review, but opaque automation should not deny legitimate exit. Hold grounds and appeal routes remain necessary.
Security comparisons should be public. Providers can report fraudulent port attempts, holds, confirmed incidents, and response times in aggregate. A portability regime wins 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 allow a holder to circumvent legitimate number-resource policy. Otherwise, organisations would seek the provider with the weakest needs assessment, laxest transfer controls, contact accuracy or least rigorous abuse response. Portability would become regulatory arbitrage rather than accountability.
A common baseline policy should attach to the record and the applicable recognised framework. Providers can compete on service, support, tools, language, assurance, and price. They must not contradict the official allocation history or invent property rights. When regional policy legitimately differs, the design must indicate which rules follow the service region, the holder, the resource origin, or the provider.
This is one of the hardest questions. A provider operating in multiple regions could offer consistent service while resources remained subject to home-region obligations. Inter-regional portability could weaken the link between affected communities and policy. An initial design may therefore allow provider choice only among recognised providers committed to the same regional policy, then expand it after evidence.
Policy disputes should use existing or jointly designed appeals, not provider discretion. A provider can help a client navigate rules but cannot promise an exemption. Public enforcement data can reveal whether a provider interprets requirements unusually leniently or severely.
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 can transfer service rather than remain captive.
This threat can discipline boards. Fee increases, poor support, or opaque security decisions can trigger measurable departures. Directors can no longer assume that every resource holder in a service region must maintain the same relationship with the provider. Performance now becomes part of the electoral debate.
Exit can also weaken voice. The most discontented members may leave, reducing pressure for reform and leaving behind less mobile members. Well-endowed 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 its association membership even if a different provider handles registration, or a separate regional public-interest membership could exist. Voting eligibility should not be manipulated to punish exit. The design must decide whether entity membership finances 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 requires an automatic response
A provider may become insolvent, lose accreditation, suffer an attack, or abandon service. Portability must work when the client cannot obtain cooperation. The trust anchor should support emergency bulk transfer to a provider of last resort, with records and cryptographic material preserved under predetermined controls.
Continuity reserves or insurance could finance the transition. Providers should maintain a 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 clients permanently. Fees and governance should be transparent.
Decisions to withdraw recognition require due process but cannot wait while official data deteriorates. Provisional restrictions can block risky changes while allowing read access and urgent security maintenance. Independent oversight should review both the intervention and the restoration.
This continuity architecture could be portability's greatest public benefit. Current regional concentration can make institutional failure a systemic event. Multiple providers with a common recovery layer create redundancy, provided that concentration does not simply reappear among two global firms.
Competition can also concentrate
Choice does not guarantee diversity. Large providers can use scale, low prices, and integrated services to dominate. Operators may choose the same provider because their peers do, creating a new single point of failure. Private equity or state-linked ownership may consolidate nominal competitors.
Recognition should require ownership disclosure and monitor market share. Merger review can consider systemic resilience, not just price. The trust anchor can publish provider concentration by resource count and criticality without exposing sensitive customer details. Large network procurement should consider diversity.
Interoperability reduces proprietary lock-in. Common exports, standard authentication, and maximum transfer times prevent 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 can serve small operators and maintain competitive pressure. Incumbent RIRs could become providers in the new regime, using their expertise and membership governance. Portability should not destroy regional institutions; it can require them to earn service relationships while continuing their defined coordination functions.
NRS illustrates demand, not accomplished authority
The Number Resource Society presents membership and representation offerings on its public pages. Its terms describe individual and corporate membership, and its network-members page describes organisations that have designated it in relation to RIR governance. These activities show a demand for assistance and collective voice outside ordinary direct participation.
They do not establish that NRS is a recognised alternative RIR, that it operates a globally interoperable registry-service port, or that it can change the official record chain. A proxy for governance matters is not portability. Membership in an advocacy or service organisation is not a transfer of registry responsibility.
This limitation is essential because future design should not be marketed as present fact. NRS can advocate a model, organise members, or offer support within its legal authority. The operational proposition evaluated here would require recognition, shared technical controls, provider obligations, and acceptance throughout the number registry system.
The gap is analytically useful. It shows that an organisation can aggregate discontent without yet providing exit. Elections remain existential when representation by another body cannot change the service relationship. A credible reform programme must move from rhetoric about choice to testable institutional architecture.
A gradual experiment would be safer than revolution
Portability should start with a limited pilot. Entities could volunteer with low-risk records, remain under the same regional policy, and choose from a small set of independently evaluated providers. The trust anchor would record provider changes while incumbent records remained synchronised for observation. Routing and holder identity would not change.
The pilot should test authentication, transfer time, refusal, 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 is transferred. A constrained 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 committee should include operators, incumbents, potential providers, security specialists, and affected non-members. Conflicts and decisions should be published. An appeal body should exist before the first contested request.
Expansion would depend on evidence: low fraud, accurate records, acceptable continuity, real provider choice, and no policy circumvention. Failure could justify redesign or abandonment. Portability is a means to accountability, not an article of faith.
Measuring whether exit improves accountability
Success is not measured by the number of ports. A healthy market may have a low change rate because providers perform well. Important metrics include transfer completion time, abusive refusals, fraud, service continuity, correction quality, provider concentration, cost, and user confidence.
Governance metrics 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 a political voice? Are small networks left behind? Does the provider of last resort become a neglected warehouse?
Reasons for change can be collected voluntarily in broad categories: price, support, security, language, governance, consolidation, or organisational change. Confidential surveys can complement public totals. Providers should not receive individual political profiles.
The trust anchor and recognition body must also be scrutinised. If every dispute escalates to the central level, portability may have added bureaucracy without distributing power. If the central body systematically favours incumbents, competition is cosmetic. Appeals, audit, and stakeholder participation should measure this 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 present a record that looks complete while silently changing its legal or operational meaning.
The common layer should define mandatory fields, proof classes, timestamps, and provenance. It should distinguish a fact provided 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 cannot rewrite the durable record to ease migration.
Data quality disputes must be handled separately from provider change. A holder should not be forced to accept an inaccurate record before leaving, but portability must not become a means to erase a legitimate restriction. The trust anchor can mark contested fields, preserve both claims, and allow the new provider to perform unaffected functions while an independent examiner decides.
Language and transliteration also matter. Legal names may appear in multiple scripts; corporate forms differ; contacts change. Common meaning does not require public records only in English. It requires stable identifiers, faithful display, and a clear official form. Privacy controls should define which data is public, limited to providers, or available only to examiners.
Interoperability testing should include meaning, not just file transfer. Auditors can port standard records between every provider pair, compare resulting authority, and verify that no field gains or loses effect. Published compliance results allow operators to choose providers based on demonstrated compatibility.
Fees must not recreate captivity
Competition among providers can lower prices, but shared functions still need funding. The trust anchor, recognition body, appeals, security coordination, and last-resort service produce collective benefits. If entirely funded by port fees, they may discourage exit. If funded by a single incumbent, independence becomes doubtful.
A transparent common levy based on resource service categories, provider market share, or a mixed formula could fund shared functions. The amount and budget should be governed separately from individual providers. Operators should see which charge pays their provider and which supports the collective infrastructure. Cross-subsidies for small networks can be explicit rather than hidden.
Losing providers should not impose early-termination penalties unrelated to disclosed unrecovered costs. Unpaid and uncontested service fees may remain recoverable through ordinary means without indefinitely freezing official records. Contested invoices should be subject to fast-track procedure. Essential record accuracy should not become collateral for a commercial claim.
Gaining providers may offer discounts, but incentives should not encourage unsafe bulk ports or distort policy. Contracts must include clear terms for renewal, data export, and failure. Providers should publish total prices in comparable categories so that low display fees do not hide charges for RPKI, reverse delegation, support, or exit.
Affordability is a governance metric. If only large holders can move, portability will increase inequality. A low-cost standard port, fee waivers in case of 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 be faster than operational harm
Disputes about a port can affect security and service within hours, while ordinary corporate or court review can take months. The system needs a fast-track, specialised appeal with the power to suspend, complete, or temporarily reverse a transaction. Its scope should be narrow enough to avoid becoming a shadow policy-maker.
The first tier can handle documentary questions: applicant authority, valid lock, provider deadline, and notice. A second independent panel can review contested fraud, ownership, or policy restrictions. Courts remain available where law requires, but the operational state should not drift while parties wait.
Each interim order should identify the safest state. Sometimes that means preserving the old provider; sometimes the old provider has defaulted and the new one must maintain service under restriction. The decision should protect routing security and contact continuity without prematurely deciding final registration rights.
Appeal statistics should show who succeeds, timeframes, reasons, and provider trends. A provider with repeated unjustified refusals needs oversight. A gaining provider submitting weak authorisations needs corrective action. Publication can omit holder identities while exposing institutional behaviour.
Costs should not discourage legitimate challenges. 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 good
Incumbent RIRs hold decades of knowledge about local law, member practices, network development, language, and operational history. Portability should not scatter this capability into private firms or make it accessible only to the largest provider's customers. 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 require collective funding and governance. An operator who chooses a different service provider should still benefit from accurate regional data and participate in open policy. Providers can contribute through fees and expertise without controlling the forum proportionally to their market share.
Historical records require stewardship that goes 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 disappear. An RIR could operate the trust anchor under independent oversight, serve as a provider, facilitate policy, and maintain last-resort capacity through separate accounts and decision bodies. Separation would prevent the incumbent provider from using trust-anchor control against its competitors.
The goal is not to replace public-interest associations with vendors. It is to distinguish contestable service from shared stewardship. Regional knowledge remains answerable to the wider community, while operators gain choice over the organisation that handles their day-to-day registration relationship.
Exit does not replace duty
Markets often respond to poor service with 'leave'. That response is limited public evidence when 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 fulfil their duties regardless of customer mobility.
Portability also cannot justify neglecting elections. Boards set provider strategy and influence collective institutions. Members need fair voting, candidate transparency, conflict checks, and remedies. Exit works best as a lever behind voice, not an invitation to abandon it.
Some decisions must remain common. Resource record uniqueness, basic security, authority policy, and crisis coordination cannot fragment into consumer preferences. The design challenge is to locate these functions in accountable shared institutions while opening contestable service functions to choice.
Public-interest obligations should follow every recognised provider. Contact accuracy, confidentiality, security cooperation, non-discrimination, and continuity are not optional premium features. A holder should not be allowed to choose a provider that hides abuse or fabricates registration history.
The election after portability
Imagine a board election where members assess fees, security and leadership knowing they can move the registry service under common rules. Candidates could no longer present every criticism as a threat to regional continuity. Challengers could promise better service while the trust anchor protects the durable record. Incumbents could defend their performance with measurable retention and quality.
The campaign would still matter. The provider might serve a large portion of the region, run important systems, and contribute to policy coordination. A bad board could cause real harm. But the consequence of losing for discontented operators would not be absolute dependence for another term.
Exit data would sharpen the 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 ignore than silence in surveys. Providers could win back members through verifiable improvements.
Portability could also expose the value of incumbent RIRs. Many operators might stay because regional expertise, trust, and member control outweigh alternatives. Choice would transform this loyalty from necessity into evidence. A strong RIR does not need to fear a right to exit designed with common safeguards.
Exit should be possible without a political statement
A holder should not have to accuse a board of failure before changing provider. Portability works best as an ordinary administrative right exercised for reasons of service, language, price, security, or organisational preference. Requiring a statement of grievances would discourage exit, invite retaliation, and turn every transfer into a referendum on leadership.
Providers and the coordination body can voluntarily collect reasons in broad categories for accountability analysis. Individual responses should remain confidential and never affect transfer approval. Aggregate trends can inform elections: a sustained increase in departures over delayed support or weak security merits attention. No director should receive a list of political opponents disguised as a customer study.
Ordinary exit also protects the legitimacy of sanctions against abuse. If all ports are treated as hostile, a valid security hold seems punitive. 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 motives.
Providers should be prohibited from degrading service, changing support priority, or restricting member participation after departure notice. The relationship with the losing provider continues until the official change completes. Data exports, final invoices, and security notifications should follow a standard timetable. A withdrawal offer may be allowed, but it must not delay the port or exploit confidential dispute information.
Depoliticised exit does not eliminate 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 precisely how it can discipline governance without destabilising every election.
Separating the register from the director
The central proposition is constitutional rather than commercial. A durable Internet number record should not depend entirely on trust in a single board. The official record can remain coordinated while the service relationship becomes portable. Elections can govern providers without making every ballot a referendum on whether operators retain usable institutional continuity.
This separation requires more governance, not less: recognition, neutral anchor, common policy, authentication, locks, appeals, security reporting, concentration controls, and provider of last resort. Bad design could enable hijacking or arbitrage. Good intentions are not enough.
Comparisons show a possibility, not equivalence. Domain transfers preserve names between registrars. Telephone portability preserves numbers between operators. Existing RIR transfers preserve controlled holder changes. A future registry-service port would need its own rules because Internet number resources link registration, routing and public coordination in distinct ways.
Advocacy in the style of NRS helps put exit on the agenda, but authority must be demonstrated through recognised operation. Until then, the proposal should be evaluated as a future institutional choice. Its greatest promise is not convenience. It is proportionality: no single board election should carry all service, record and accountability consequences for an operator that has no safe alternative.
Voice without exit can become supplication. Exit without shared duty can become fragmentation. Portable registries would be worthwhile only if they unite both: 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 adoption threshold should therefore be demanding and public. Proponents should demonstrate stronger 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 fate. A gradual trial can then produce evidence capable of changing each side's mind. The final measure is not whether portability looks competitive, but whether it preserves the common number registry while giving operators a credible, reversible, non-punitive choice of manager.