Summary

  • PTI is a genuine California nonprofit public benefit corporation, not merely a trading name for an ICANN department. It can contract, keep records, employ people, maintain accounts, be audited and act through a five-member board with fiduciary duties.
  • Control remains concentrated in ICANN. ICANN is PTI's sole statutory member, elects all five directors, selects the PTI president, may remove directors without cause under the bylaws, provides complete funding, approves specified major corporate acts and receives PTI's budget and strategic plan within wider ICANN planning arrangements.
  • The five-seat board adds scrutiny but not control independence: three seats are held by ICANN or PTI employees, including the president, and two are nominated through ICANN's Nominating Committee before election by ICANN as member. Quorum and some major votes require participation or support across both groups, yet the parent retains the membership franchise.
  • Legal separation is best understood as functional ring-fencing. It improves operational visibility, accounting, contractual clarity and successor readiness. It does not create an arm's-length operator with its own revenue base, autonomous strategy, independent appointment authority or power to resist a duly approved ICANN separation decision.

The word "separate" carries too much weight

Institutional debates often turn on a word that sounds more decisive than the documents beneath it. Public Technical Identifiers is a "separate legal entity." That statement is true. It can also invite an inference that does not follow: because PTI is separate, it must be independent of ICANN. Corporate law does not work that way. A wholly controlled subsidiary can be legally distinct while remaining strategically, financially and electorally subordinate to its parent.

PTI was created in August 2016 as part of the settlement that allowed the United States government to leave its stewardship role over the IANA functions. The names community wanted the operational function identified and isolated from ICANN's wider policy and corporate activities. A dedicated corporation would hold a clearer mission, contract with ICANN for naming work, perform number and protocol parameter work through related arrangements, publish its own finances and maintain an organizational boundary that could support eventual separation if performance failed.

The design was never a declaration of sovereignty. The 2016 transition proposal said that ICANN would be PTI's sole member and that PTI would be a controlled affiliate. ICANN would fund it and provide administrative resources. The proposed board would remain small rather than reproduce the complexity of the ICANN Board, because primary accountability would continue at ICANN level. The objective was to make the function separable, not to build another supreme coordinator of identifiers.

This distinction should govern any assessment of independence. PTI can possess its own duties and exercise professional judgment in performing them. Its directors owe duties to PTI, and its records cannot simply be treated as nonexistent because the parent controls membership. But independence requires more than legal personality. It asks who appoints leadership, who can remove it, who provides money, who sets the strategic perimeter, who supplies people and systems, who owns essential rights, who enforces the main contract and who can decide that another operator should take over.

Across those questions, ICANN's position remains dominant. The separation is real, but shared control is the stronger description of how the institution operates.

Why a new corporation was created at all

Before 2016, IANA work was performed within ICANN under a federal contract and other long-standing community arrangements. The IANA department had a recognizable identity, specialised personnel and published services, yet it was not a legally separate corporation. If the naming community ever needed another operator, it would first have to distinguish transferable service responsibilities from the wider assets and obligations of ICANN.

PTI made that boundary more explicit. Its articles define a narrow public-benefit purpose: to carry out ICANN's purposes by performing the IANA functions on ICANN's behalf. Its bylaws create a board, officers, records, audits, budgets and planning requirements. The naming function sits under a written agreement between ICANN and PTI. The number and protocol parameter responsibilities sit under subcontracts linked to agreements between ICANN and the respective operational communities. Shared support is described in a separate Services Agreement.

This decomposition has practical value. It identifies which corporation performs the service, what that corporation must deliver, what support the parent provides, what costs belong to the work and what records should be available if responsibilities move. It creates a place for a dedicated audit and a public budget. It allows the Customer Standing Committee to monitor a defined operator against written service expectations. It makes a future replacement a transfer between legal providers rather than an attempt to extract an informal department from a much larger corporation.

Corporate form also imposes discipline. Directors must act through meetings, resolutions and recorded decisions. Officers have stated responsibilities. The corporation must maintain books and submit required filings. Related-party transactions can be identified. A separate audit can test whether accounts fairly present PTI's position. None of these guarantees good governance, but each creates evidence that would be harder to obtain if the function remained only a cost centre within ICANN.

The gain is therefore not imaginary. The mistake is to measure it against full autonomy rather than against the prior departmental structure. PTI is more visible, more transferable and more legally legible than an ordinary division. It is not independent in the sense that an external contractor, membership association or separately funded public institution would be.

Sole membership is the centre of control

The decisive fact appears in both ICANN's and PTI's governing documents: ICANN must at all times be PTI's sole member. In a California nonprofit public benefit corporation, a statutory member can possess powers comparable to a shareholder's franchise in a commercial corporation, subject to the articles, bylaws and applicable law. PTI has only one such member.

ICANN, acting in that capacity, elects every PTI director. Other institutions contribute to nominations for two seats, but no person or entity other than ICANN has the right to elect or designate a director. The member also selects the PTI president, who serves as general manager and sits on the board. The original bylaws allow the member to remove a director without cause. Major corporate acts such as merger, reorganization, dissolution and certain asset dispositions require both enhanced board approval and member approval.

These powers are not ceremonial. Election determines who exercises corporate authority. Removal shapes how securely directors can oppose the member. Approval rights allow the parent to stop structural choices even where a board majority supports them. The president's dual role connects daily management to the member's appointment power.

ICANN's sole-member authority is constrained by the wider post-transition settlement. ICANN cannot casually alter protected PTI governance terms, dispose of important assets, leave membership, reorganize the corporation or dissolve it without exposure to the Empowered Community's rejection rights and other bylaw requirements. Amendments to PTI's articles require community approval. These safeguards reduce the risk that ICANN leadership could silently dismantle the agreed structure.

Constraints on a controller do not transfer control to PTI. They make ICANN's exercise of membership powers accountable to the ICANN community. If the Empowered Community blocks a harmful action, PTI benefits from the restraint, but PTI has not acquired an independent electorate or a second member. The ultimate governance contest remains within ICANN's constitutional order.

This is why "shared control" is more accurate than either "ICANN department" or "independent operator." PTI's board controls its corporate affairs within the powers assigned to it. ICANN controls the membership franchise. The wider community can constrain specified ICANN actions. Different institutions hold different parts of authority, but PTI itself does not control the source of its board's mandate.

The five-seat board adds independence of judgment, not independence of control

PTI's board has five directors. Three are employees of ICANN or PTI and are nominated by ICANN as member; that group includes the PTI president. Two must not be employees of either corporation and are nominated through ICANN's Nominating Committee. ICANN then elects all five in its member capacity.

The two Nominating Committee directors are an important safeguard. Eligibility rules separate them from recent employment, consulting and board relationships with ICANN or PTI. The board as a whole is expected to combine operational, technical, financial and governance experience and to reflect diversity. These directors can ask questions from outside the management chain, serve on the audit committee and insist that PTI's own interests and public-benefit purpose be considered.

Board procedure gives their presence practical weight. A quorum requires at least one ICANN director and one Nominating Committee director. Election of the chair requires support that includes both groups, and the president cannot chair the board. Committees exercising delegated board authority must also include both an ICANN and a Nominating Committee director. Certain major actions require at least four of the five authorized directors as well as member approval. These rules prevent the three employee-linked seats from conducting all board business while excluding the two outside nominees.

Yet participation is not equivalent to a veto over ordinary decisions. At a duly constituted meeting, many acts can be approved by a majority of directors present unless a higher threshold applies. Nor do the two outside nominees control appointment of their successors: the Nominating Committee nominates, but ICANN as member formally elects. The member's removal power further limits tenure independence, even though community protections and reputational consequences would make arbitrary use consequential.

The board's composition was deliberately chosen to avoid recreating ICANN's broad multistakeholder legislature at operator level. That keeps PTI focused on execution rather than policy. A larger representative board could blur the boundary between implementing established rules and making them. The resulting board is suitable for oversight of a specialised service, but it should not be described as a counterweight capable of taking PTI onto a strategy that ICANN, as sole member and funder, rejects.

Directors still owe duties to the corporation. Employee status does not legally convert a director's vote into an instruction from an employer, and an outside director is not a delegate of every customer. Fiduciary judgment can create meaningful operational restraint. The correct conclusion is narrower: the board provides a distinct forum and some independent voices, while the design reserves electoral control to ICANN.

The president links management to both corporations

PTI's president is more than a chief technician. Under the bylaws, the president is general manager, supervises day-to-day affairs subject to board control, sits as one of the five directors and is selected annually by ICANN as sole member. The current structure also pairs the PTI presidency with senior responsibility for IANA services at ICANN.

This alignment can be efficient. One leader can connect service obligations, budgets, staff, customer expectations and the support ICANN must provide. It reduces the risk that parent and affiliate issue conflicting operational directions. During a security event or continuity exercise, a short chain of authority can matter more than corporate distance.

It also limits managerial independence. A president chosen by the parent, sitting among three employee-linked directors and relying on parent funding is unlikely to function like the chief executive of an arm's-length supplier. The president's responsibility to PTI and the PTI Board is real, but career, appointment and organizational relationships align the office closely with ICANN.

The distinction becomes important when interests diverge. Suppose PTI believes resilience requires expenditure that ICANN's wider financial plan does not support. Suppose a service concern traces to a shared ICANN resource. Suppose a future separation recommendation would move the naming function away from PTI. The president would have to serve PTI's lawful responsibilities while participating in a structure whose sole member controls funding and the eventual successor contract. Corporate form clarifies the duties; it does not eliminate the tension.

Strong governance therefore depends on recorded board deliberation, clear conflict handling and visible reasons. The public does not need to assume personal bad faith to ask whether PTI's position was separately considered. Where parent and affiliate interests differ, minutes, abstentions, audit evidence and explicit PTI resolutions matter. The separate board is most valuable precisely when it demonstrates that alignment was examined rather than presumed.

A dedicated budget without a separate revenue base

Financial autonomy is one of the clearest tests of institutional independence. PTI prepares an annual operating plan and budget, consults ICANN bodies and the operational communities, publishes a draft for comment, receives PTI Board approval and reports performance against the adopted plan. The process gives the IANA functions a visibility that a line buried in a larger corporate budget would not provide.

The dedicated budget is substantial and detailed. The adopted FY27 plan sets out a PTI budget of about $11.5 million. It distinguishes direct dedicated work, direct shared support and broader shared services. The accompanying IANA plan identifies 19 direct dedicated full-time-equivalent positions and 4.5 direct shared positions, with further shared-service costs. These categories reveal the operating surface and show that PTI's cost is not limited to employees working only on IANA tasks.

Visibility, however, is not an independent treasury. ICANN completely funds PTI. The Services Agreement uses intercompany charges: PTI invoices ICANN at cost for IANA services, while ICANN allocates to PTI the cost of support it provides. PTI cannot charge third parties for the naming function without ICANN's written consent. It does not possess a diverse customer-revenue base that could sustain a course opposed by its parent.

The budget also returns to ICANN's wider financial structure. After PTI Board approval, the PTI plan is submitted for inclusion in the IANA and ICANN planning arrangements. ICANN's Board adopts the IANA operating plan and budget, and the Empowered Community has protected powers concerning those budgets. A caretaker budget helps continuity if the ordinary annual plan is rejected or delayed.

This arrangement has accountability advantages. The community can see what the functions cost, comment before approval, compare spending with results and challenge an ICANN budget that threatens IANA performance. Full funding by ICANN also protects the operator from dependence on fees paid by individual registries seeking favorable treatment. A neutral identifier service should not have to sell access to those it serves.

But the funding model makes ICANN indispensable. If PTI's board requested resources beyond what ICANN would provide, PTI could not readily turn to another customer or capital provider. Its contract expressly links performance to ICANN's funding and services. Financial separateness is therefore accounting separateness: costs, plans and results are identifiable, while the source and final corporate setting of funds remain controlled by the parent.

Strategy is dedicated, but aligned by design

PTI's bylaws require a strategic plan. The IANA 2030 Strategy covers 2025 through 2030 and sets priorities around innovation, operational excellence and community engagement. It was developed with IANA staff, the PTI Board, ICANN and community input, published for comment, adopted by the PTI Board and submitted to the ICANN Board.

A dedicated strategy matters. The IANA functions have technical horizons, customer relationships and continuity risks that can disappear inside ICANN's broader debates over policy, contracting, meetings and institutional growth. A separate plan lets PTI describe how identifier services will remain secure, scalable, accurate and responsive. It gives the board criteria against which to assess performance over more than one budget year.

The plan is nonetheless explicitly aligned with ICANN's five-year strategy and is described as a subset of it. That is not an accidental overlap. PTI's articles say its specific purpose is to carry out ICANN's purposes by performing IANA functions on ICANN's behalf. A strategy that contradicted ICANN's mission or wider plan would raise a basic question about the affiliate relationship.

Alignment need not mean that PTI has no judgment. A subset can be deeper and more technically specific than the parent plan. PTI can choose priorities among reliability work, system renewal, customer engagement, documentation and resilience, subject to contracts and approved resources. The board can challenge whether a fashionable initiative serves the operator's narrow mission. Community comments on the IANA 2030 draft did exactly that by emphasizing reliable service over engagement for its own sake.

The limit is strategic exit. PTI cannot decide that it will serve a different mission, seek a separate membership, finance itself independently or retain the naming function against an approved separation decision. Its strategic autonomy concerns how to perform assigned IANA responsibilities well, not whether to remain part of the ICANN family or redefine the source of its mandate.

Staffing moved toward PTI while support remained shared

People reveal whether a corporate boundary exists in practice. At the transition, continuity took priority. Existing IANA personnel remained ICANN employees and were seconded to PTI. The Services Agreement required ICANN to help establish benefits, systems and policies that would allow PTI to employ the relevant workforce, after which PTI could offer employment and hire new personnel directly.

The move was meant to avoid two opposite failures. Immediate transfer could have caused staff loss, benefit disruption and confusion at the moment government stewardship ended. Permanent secondment could have left PTI as an empty shell whose supposed workforce answered entirely to ICANN. A staged approach preserved service while creating a route toward direct PTI employment.

PTI Board minutes in 2020 recorded 16 employees against a budgeted headcount of 18, evidence that the corporation developed a substantive workforce rather than remaining only a contract and a board. Current plans continue to identify direct dedicated positions. This is real organizational substance.

It is not complete personnel independence. The Services Agreement provides a wide range of ICANN support: finance, accounting, audit assistance, communications, compensation, facilities, procurement, legal and regulatory help, security, technology support, board administration, and the treasurer and secretary functions. Direct shared staff contribute time to IANA work without belonging wholly to the dedicated team. The FY27 cost categories continue to display that mixed model.

Shared support can be rational. A corporation with fewer than a large enterprise's workforce does not need to duplicate every specialist function. Buying services from its parent at cost may be safer and cheaper than building a complete legal, payroll, facilities and security organization. The agreement requires records that explain related charges and treats records created for PTI work as PTI property in specified circumstances.

Dependence becomes a governance issue when a shared resource controls a material service or when responsibility is unclear. ICANN may alter, suspend or end support in circumstances allowed by the agreement, provided the change does not create material risk to DNS security and stability. Its personnel remain under ICANN direction when providing shared services. PTI's remedy for deficient support is constrained by the intercompany agreement. A formally separate operator can therefore depend on parent-controlled people for functions essential to its performance.

The right measure is not the percentage of names on one payroll. It is whether PTI's board can identify critical roles, demand adequate support, preserve records, attribute failures and maintain a credible path to another provider if an ICANN service becomes unavailable. Staffing separation is strongest in the dedicated operational team and weakest in enterprise support.

The Services Agreement describes dependence rather than concealing it

The 2016 Services Agreement is one of the most revealing documents in PTI's architecture. It does not pretend that incorporation instantly produced a self-sufficient operator. It lists the facilities, personnel and specialist services ICANN would provide, sets an at-cost charging method, addresses records and allows an eventual employee transition.

That candour is a governance strength. Related corporations often share resources through informal practice, making cost and responsibility difficult to trace. A written agreement identifies obligations and provides a basis for PTI's board and auditors to ask whether the service was supplied and properly allocated. It also requires each corporation to maintain books that clearly disclose transactions between them.

The agreement nevertheless confirms the depth of integration. ICANN provides office space and can supply a long catalogue of support. Shared personnel remain ICANN employees or contractors under ICANN's direction. The original arrangement estimated the annual service scope at about $9 million and described PTI as fully and exclusively funded by ICANN. The agreement remains in force until ended under specified conditions rather than expiring on a short recurring term.

Its liability design also matters. Where ICANN fails to provide a service, PTI's stated remedy is essentially performance of that service under the agreement. That is less leverage than an outside customer might seek from a critical supplier. Termination is possible for material breach after notice and cure conditions, but ending parent support would not by itself give PTI another finance, facilities or enterprise-services provider.

The agreement therefore supports separation in an evidentiary sense while limiting it in an economic sense. It tells a future transition team which dependencies must be replaced. It does not remove those dependencies today. If PTI moved outside ICANN control, the successor arrangement would have to reproduce or substitute many services now obtained from the parent.

The naming contract is arm's-length in form, related-party in substance

ICANN and PTI signed the IANA Naming Function Contract as two corporations. It specifies performance, service expectations, security, reporting, customer complaints, inspection, reviews, continuity and transition. PTI cannot subcontract the whole responsibility. The term renews automatically in five-year periods unless the protected review and separation arrangements support a different result.

These provisions are enforceable corporate obligations. PTI's separate personality allows ICANN to direct a mitigation plan, inspect performance and require cooperation with a successor. The contract helps distinguish operator duties from ICANN's wider responsibilities. If PTI were only a department, many of those rights would be managerial expectations rather than obligations between legal persons.

At the same time, ICANN occupies nearly every surrounding position. It is the naming customer, PTI's sole member, the source of funding and shared services, owner of intellectual property created under the contract, and the corporation that would enter an agreement with a successor. PTI performance is expressly conditioned on ICANN providing necessary support. ICANN indemnifies PTI while the affiliate relationship continues.

The direct customers of naming services do not become third-party beneficiaries of the contract. They receive complaint, mediation and review routes, and the Customer Standing Committee has a formal monitoring role. Yet the ordinary right to enforce the bargain belongs to ICANN. If ICANN and PTI agreed in practice to tolerate a weakness, customers would need to rely on the protected accountability structure rather than step into ICANN's contractual shoes.

The ICANN bylaws require ICANN to enforce its naming-contract rights and protect material terms from easy alteration. That duty is crucial because it recognizes the parent-customer conflict. But a required act by the parent is not the same as an outside counterparty. The quality of enforcement depends on community observation, board accountability and willingness to distinguish PTI's interest from ICANN management convenience.

Formal contracting therefore creates real clarity without proving bargaining independence. It is a control instrument housed inside a controlled group.

Operational visibility is PTI's strongest independence gain

If independence is understood as the ability of outsiders to see and evaluate the operator apart from ICANN's other activities, PTI has achieved a great deal. It has its own board pages, minutes, resolutions, audit committee, financial statements, tax filings, annual budgets, management financial reports and strategic plans. The naming service publishes performance measures, while the Customer Standing Committee reviews service delivery regularly.

Separate reporting makes comparisons possible. Readers can identify dedicated costs and shared costs, examine whether actual spending follows the plan, see board approvals and assess whether strategy remains focused on IANA responsibilities. Independent auditors report on PTI financial statements. Tax filings confirm the corporation's nonprofit status and governance characteristics. Review teams can evaluate PTI against a defined contract rather than infer performance from ICANN's overall reputation.

Visibility is a form of power. A parent that controls appointments and funding can still be constrained when reasons, costs and outcomes are public. Two outside-nominated directors can ask more effective questions when the numbers and obligations are isolated. Customers can distinguish an operator failure from a policy disagreement. A future successor can study the operating perimeter.

The limits are equally important. Published minutes may summarize rather than reproduce every deliberation. Cost allocations rely partly on management estimates where specific usage is unavailable. Security and personnel matters can justify confidentiality. A separate set of accounts can show that a shared service cost exists without proving that the allocation method captures every dependency. Corporate visibility is therefore evidence, not complete transparency.

Still, this is where the separation should be credited most strongly. PTI made the IANA operating function more inspectable. The arrangement can be valuable even if it never creates autonomous control, because inspectability supports customer confidence, community review and eventual transferability.

The Customer Standing Committee constrains performance, not ownership

The Customer Standing Committee monitors PTI's naming performance against the contract and service expectations. It brings direct registry-customer experience into regular oversight and can pursue remedial steps for persistent or systemic problems. PTI must provide reports and act in good faith to resolve identified concerns.

This relationship gives PTI an accountability audience beyond its parent. Management cannot reasonably treat ICANN's satisfaction as the only measure when the CSC publishes assessments and can escalate unresolved deficiencies. In practical service delivery, that can produce a meaningful degree of independence from ICANN's non-IANA priorities: the operator must answer to documented customer expectations.

But the CSC does not own PTI, elect its board, approve its complete budget or direct its strategy. It cannot itself initiate a change of operator. Escalation travels through the ccNSO and GNSO and can lead to a special review, a separation examination and eventually a successor recommendation. The committee's influence is strongest in evidence and remediation, not corporate control.

This division preserves the operator-policy boundary. Direct customers should help define whether service is satisfactory, but no narrow customer group should be able to capture the corporation or use appointment rights to influence individual requests. The tradeoff is that PTI can remain under ICANN ownership even when customers are dissatisfied, unless the wider, high-threshold separation structure is activated.

Operational accountability therefore pluralizes PTI's audience without pluralizing its membership. The corporation listens to several communities while having one legal member.

Separate assets and records make replacement more credible

One reason to incorporate PTI was to make the IANA functions capable of moving if the community ever selected another provider. Separate records, accounts, contracts, personnel categories and plans help identify what a successor would need. The naming contract requires a transition plan and PTI cooperation. Records maintained for PTI under the Services Agreement are treated as PTI property in specified circumstances and must be transferred when that agreement ends.

This is more than administrative neatness. An operator can become irreplaceable when essential knowledge, rights and systems cannot be separated from its parent. PTI's corporate boundary provides a map. A separation group could identify dedicated work, shared support that needs substitution, customer contracts, staffing, facilities, records and intellectual property licences.

The map also exposes limits. Key intellectual property produced under the naming contract belongs to ICANN and is licensed to PTI for the term. Facilities come from ICANN. Many enterprise services are shared. Funding comes from ICANN. A successor might contract directly with ICANN and receive the necessary rights, but PTI could not simply depart as a self-contained firm with every resource already under independent control.

That may be intentional. Keeping essential rights with ICANN can prevent an incumbent affiliate from holding the global function hostage. If the approved separation route selects a new operator, ICANN can license or provide what the successor requires. From a continuity perspective, parent ownership may be safer than operator ownership.

It also confirms that PTI's separability is asymmetric. ICANN can separate the function from PTI under protected conditions; PTI cannot separate itself from ICANN and carry the function away. The boundary is designed for community-directed succession, not corporate emancipation.

High performance can coexist with weak autonomy

Governance analysis should not infer operational weakness from corporate dependence. PTI's published record shows sustained service, extensive reporting and strong review findings. The second IANA Naming Function Review concluded in 2025 that PTI operated reliably and efficiently and identified no performance deficiency or major operational improvement need. Its recommendations focused on clarity, transparency and review cadence rather than a failed service.

That evidence matters. The purpose of the structure is not to maximize formal independence as an abstract good; it is to provide secure, stable and accountable identifier services. Shared systems, aligned leadership and complete funding may contribute to good performance. Duplication undertaken merely to prove independence could increase cost and risk.

Success does not answer the control question. A wholly controlled affiliate can be excellent. Professional norms, technical community expectations, public measures and staff expertise can protect neutral service even where the parent appoints the board. Conversely, an independently funded operator can perform badly. Performance and autonomy are related but distinct variables.

The difficult test arises when PTI and ICANN interests diverge. Strong service in ordinary conditions does not show whether the PTI Board would oppose inadequate parent funding, publish a finding uncomfortable to ICANN leadership, attribute a failure to shared support or cooperate fully with a successor that ends PTI's naming role. The legal arrangements provide duties and visibility for those moments, but the record has not had to demonstrate every severe case.

This uncertainty should be stated without manufacturing suspicion. There is no need to claim that ICANN has improperly directed PTI or that the board has ignored its duties. The point is structural: current success proves operating capability, not arm's-length independence.

What real independence would require - and what it would cost

A more independent PTI would need changes across several dimensions. It could have more than one statutory member or an external designator with appointment rights. A majority of directors could be selected outside ICANN employment and election control. The president could be appointed solely by the PTI Board. Revenue could come through direct contracts with operational communities or a protected funding trust. Enterprise services could be independently procured. Strategic approval could end at the PTI Board rather than return to ICANN.

Each change carries cost and risk. Multiple members could turn technical operations into constituency bargaining. Direct customer fees could create unequal influence or incentives to favour large registries. An independently appointed board might drift from the policies the operator is meant only to implement. Separate facilities, security, legal, finance and technology teams would increase expense. A funding trust would need its own accountable governors. Greater autonomy could make a reluctant PTI harder to replace.

The transition settlement rejected many of those costs by keeping primary accountability at ICANN level. It used PTI as a narrow operator and relied on ICANN's wider multistakeholder constitution to constrain the parent. The two outside-nominated directors, special quorum rules, public budgets, audits, customer monitoring and protected separation route provide checks without transferring ultimate control.

The relevant question is therefore not whether maximum independence would look cleaner on an organizational chart. It is whether the chosen level of separation is sufficient for neutrality, evidence, continuity and replaceability. Complete independence may be neither necessary nor desirable. But calling the present arrangement independent obscures where decisions can ultimately be made.

A practical test of substantive separation

PTI's autonomy can be assessed through observed questions rather than labels. Can its board identify a service risk and obtain resources to address it? Can outside-nominated directors receive the information needed to challenge management? Can PTI distinguish dedicated costs from parent support and explain allocation methods? Can customers observe service degradation and obtain remediation? Can records and expertise move to a successor? Can the community stop ICANN from weakening protected governance?

The evidence supports qualified positive answers. Budgets and plans are public. Audits and quarterly reports exist. Board procedure requires participation from outside-nominated directors. The CSC receives performance evidence. Governing documents protect key terms. A transition plan exists. The 2025 review found reliable service.

Other questions produce clear limits. Can PTI choose its own member? No. Can it elect directors without ICANN? No. Can it choose the president independently of the member? No. Can it finance the naming service without ICANN approval or consent? Not under the present arrangement. Can it adopt a strategy unrelated to ICANN's purposes? No. Can it retain the naming function after a duly approved separation? No. Can direct customers enforce the entire naming contract as parties? No.

These answers define a corporation with operational substance and constitutional subordination. It is independent enough to be audited as an entity, governed through its own board and evaluated as an operator. It is not independent enough to determine who controls it, where its mandate comes from or whether it remains the operator.

Conclusion: separation as a tool, not a transfer of sovereignty

Did PTI's legal separation create real independence? It created real separateness. PTI is a corporation with duties, assets, records, people, a board, plans and accounts. That form improved visibility, preserved a narrow operational mission and made succession more imaginable. It gave the IANA functions an identifiable home that can be evaluated apart from ICANN's broader activities.

It did not create control independence. ICANN remains sole member, elects every director, selects the president, supplies the money and much support, receives the plans, incorporates the budget, owns essential work under the naming agreement and signs any successor contract. The board's two outside-nominated seats and special voting rules add independent judgment, not an independent franchise.

The arrangement should be understood as a ring fence inside a larger constitutional property. The fence marks responsibilities, costs and evidence. It does not change the owner of the land. Wider community powers can prevent ICANN from moving the fence arbitrarily, and customers can report when service inside it fails, but PTI cannot move beyond ICANN control by its own decision.

That may be the right bargain for a narrow, critical and presently high-performing technical operator. Shared control can preserve coherence and reduce duplication. The condition for legitimacy is honesty about the design. PTI's separate corporation was built to make IANA performance visible and replaceable, not to make the operator sovereign. Its success should be measured by neutral service, accountable use of parent support and credible transferability - not by a claim of independence its governing documents do not make.

Sources