Summary

  • Bill Woodcock’s 2015 testimony opposed moving oversight of the IANA functions from stakeholder arrangements to an intergovernmental model, while defending contractual accountability for the operator of those functions.
  • PCH’s 2023 annual report says the organization completed a transition to intergovernmental treaty-organization status. That is a different institutional object from IANA oversight; the public record reviewed here does not establish the treaty’s exact powers, a universal mandate, or an operational effect.

The same word can conceal different control surfaces

Internet governance arguments often begin with institutional labels. A process is called multistakeholder, an organization calls itself intergovernmental, or a technical function is described as community-led. Those labels can be useful shorthand, but they answer only a small part of the practical question. To understand what has changed, a reader needs to know which function is at issue, who can make which decision, what binds the operator, and what evidence shows that the decision affected a running service.

Bill Woodcock’s public career offers an unusually clear test of that discipline. In 2015, as executive director of Packet Clearing House (PCH) and a participant in the process representing the Internet numbers community, he testified to a U.S. House committee about the transition of the Internet Assigned Numbers Authority (IANA) functions. His oral statement supported moving the protocols and numbers functions on schedule, but warned against shifting their oversight to an intergovernmental model. He argued for stakeholder oversight backed by contractual accountability.

Eight years later, PCH’s 2023 annual report said the organization had completed a transition to intergovernmental treaty-organization status. Woodcock signed the report as PCH’s Secretary General. Read quickly, those facts can look contradictory: how could a person who warned against an intergovernmental model later lead an organization that adopted a treaty-based form?

The comparison is tempting, and the distinction is more informative. The 2015 hearing concerned oversight of specific IANA functions: the registries and coordination work that support identifiers used across the Internet. The 2023 report concerns PCH’s own institutional status as an organization that says it supports Internet exchange points and Domain Name System infrastructure. The sources do not show that PCH became the IANA functions operator, took over IANA oversight, or acquired a general power to govern the Internet. They also do not include the founding treaty text needed to test the details of PCH’s new legal form.

That gap is not a verdict on PCH. It is a reason to keep the claims narrow. A change in the legal form of an organization may formalize relations with states. It does not, by itself, tell us who can configure a router, maintain an exchange point, publish a DNS service, make an operational decision, or represent every network and user affected by the system.

PCH began with an operational problem, not a constitution

Woodcock’s profile is easiest to understand from the work PCH describes itself as doing. An Internet exchange point (IXP) allows participating networks to exchange traffic directly at a shared facility rather than sending every packet through a distant transit provider. A well-placed exchange can shorten paths and reduce some costs, but its value depends on local networks choosing to connect, equipment being maintained, and the site having power, space and connectivity.

DNS anycast works through a different mechanism: the same service address can be announced from more than one location, allowing routing to direct queries toward a nearby available site. Neither service becomes real because a declaration has been adopted. It depends on installations, operators, and networks that carry the announcements and traffic.

An IEEE Spectrum profile published in 2005 described the early PCH as an alliance of West Coast Internet service providers. At that time, the article said, the United States had one commercial exchange point in Washington, D.C.; California networks had to carry traffic over leased lines to reach one another there. PCH’s initial group built an exchange in San Jose, then added sites in Los Angeles, Seattle and San Diego. The account describes a practical beginning: operators trying to solve an interconnection problem close to where their networks met.

The same profile says the early group had no formal organization or budget. Members contributed equipment and labor as requests for help arrived. That is a useful historical detail because it separates the origin story from later governance language. The original coordination was not presented as a vote that authorized PCH to bind all operators. It was a service arrangement built by a group of operators who chose to contribute resources and by other networks that chose whether to use it.

IEEE Spectrum reported that PCH incorporated as a nonprofit in 1999 and that Woodcock began working for it full time in 2001 as research director. The article places his early work in a hands-on setting: designing and installing exchanges, answering technical questions, preparing equipment configurations and working with local operators. It also describes international deployments in places including Nepal, Brazil, Mozambique, Vietnam, Tanzania and Afghanistan. That is a dated profile, not a complete history of the organization, but it records a transition from an informal operator alliance toward a staffed nonprofit.

The transition from ad hoc group to nonprofit addressed a different scale problem from the original exchange builds. A continuing organization needs to receive grants, buy or move equipment, employ people, enter agreements, maintain records, and keep services running between projects. Formal incorporation can make those actions legible to donors and counterparties. It can also concentrate administrative power in officers and a board. Both are normal consequences of formal organization; neither alone answers whether an institution has a mandate over parties who are not members, donors, partners or service users.

PCH’s own 2023 report describes its operating model in public-benefit terms. Woodcock’s message says PCH provided services free or at cost under a not-for-profit charter, supported by government grants and hundreds of private-sector donors. The report calls PCH an Internet “fire department,” a metaphor for operational support and security around critical infrastructure. The metaphor conveys a service posture: work that may be needed in places where ordinary commercial returns are thin. It does not specify who has the right to authorize each service or what remedies are available if an operational or governance dispute occurs.

Those distinctions matter in a sector where infrastructure depends on several layers at once. A nonprofit may deploy equipment; the IXP operator controls its local facility; participating networks decide to peer; a fiber provider supplies a path; a DNS operator chooses service settings; and governments exercise powers under public law. PCH may be an important contributor without being the principal for every actor in the chain. Conversely, an organization’s claim to public benefit does not make its contribution inconsequential.

The task is to map what each participant controls rather than to choose between romanticizing volunteers and assuming that a formal institution runs the whole system.

The 2015 question was who could hold an IANA operator accountable

The 2015 House hearing concerned a specific transition. The U.S. National Telecommunications and Information Administration had announced its intention to transition stewardship of the IANA functions, which had been performed under a U.S. government contract, to a model developed through the global Internet community. The functions were not all identical. Woodcock emphasized that the protocols and numbers functions were simpler and ready to move on schedule, while the names function required more work on accountability. That distinction was part of his testimony, not a claim that the same oversight design fit every function.

Woodcock introduced himself as PCH’s executive director and as a North American representative to the CRISP team, the numbers community’s process for developing its transition proposal. He supported a timely transition for the protocols and numbers functions. At the same time, he argued that the transition should preserve strong stakeholder oversight of the IANA function operator. In his account, contractual obligations and enforceable remedies provided a way for stakeholders to hold the operator to account within a legal jurisdiction.

The sentence most likely to be quoted from his oral testimony was a warning that a shift from a stakeholder model to an intergovernmental model for IANA oversight “would be disastrous.” The qualification is essential. The object of that warning was the balance of authority over IANA oversight, in the context of the 2015 transition proposal. He was not making a universal claim that treaties are unsuitable for every Internet-related organization, nor was he discussing PCH’s later treaty status. Treating the phrase as a general referendum on intergovernmental institutions would extend it beyond the hearing’s subject.

His testimony also made a distinction between timing and accountability. Woodcock argued that delaying the protocols and numbers transition would be counterproductive, while the names community should not be rushed into an incomplete compromise. He framed the question as how to move a function while retaining a credible mechanism to challenge an operator’s performance. The hearing transcript is evidence of what he argued in public. It is not evidence that his proposed account of contractual control was universally accepted, that it was the only possible solution, or that it would work equally well for every organization.

This narrower reading matters for another reason: IANA is not a synonym for all Internet infrastructure. The IANA functions include coordination work involving domain names, number resources and protocol parameters. They are part of a broader ecosystem of registries, operators, standards bodies, companies, exchanges and networks. A particular IANA oversight arrangement does not tell us who operates an IXP in a city, whose equipment sits in a data center, or who supplies power and fiber to a DNS deployment.

Woodcock was therefore speaking across layers even within the hearing itself. His role at PCH concerned an organization supporting infrastructure. His CRISP role concerned a community process for a transition proposal. His testimony addressed accountability for an IANA operator. The same individual could have a technical or operational perspective in one setting and a governance argument in another. None of these roles automatically made him a representative of every operator or user. What the transcript provides is a position that can be scrutinized, not a mandate that can be presumed.

A treaty transition is a real institutional claim

PCH’s 2023 annual report marks a major institutional change. It says that on 17 August 2023 PCH completed a transition from a California-headquartered non-governmental organization to an intergovernmental treaty organization. It describes the transition as the result of more than ten years of collaborative effort. The same report lists Rwanda, The Gambia, Guinea and Eswatini as governments that signed and ratified PCH’s founding treaty in 2023.

These are not trivial claims. A treaty can be a formal instrument through which governments agree to create or recognize an organization and set terms for their relations with it. A transition to an intergovernmental form could affect how an organization is established, funded, governed, recognized, staffed or held accountable. Those are plausible categories of change, not verified descriptions of this treaty’s clauses. Without the treaty text and the relevant domestic approval and ratification records, a reader should not infer the details.

PCH’s annual report offers its own account of the intended result. It says the new status would sustain achievements with “evolved governance,” strengthen relationships with government partners and open new opportunities to engage with the Internet community. It also says the transition gives equal representation to government stakeholders. The phrase raises a precise question: equal representation among which governments, in which body, for which decisions, and alongside which non-government participants? The annual report does not answer those questions in the passage describing the transition.

It states PCH’s institutional view; it is not a substitute for the instrument that defines the arrangement.

The Rwanda Cabinet’s official resolutions provide one independently published piece of the timeline. The notice for 1 August 2023 says Cabinet approved a convention concerning the Packet Clearing House organization. Cabinet approval is evidence of a Cabinet decision in Rwanda. It does not, by itself, establish that Rwanda subsequently ratified the treaty, when it entered into force, or what any other government did. Nor does it verify PCH’s full signatory list. The distinction between approval, signature, ratification and entry into force is not legal pedantry: each is a different act, usually made by different authorities and documented in different records.

The source packet reviewed for this profile did not locate the full founding treaty. That statement is limited to the research completed for this article; it is not a claim that no copy exists anywhere. In its absence, the article cannot responsibly specify voting weights, membership rights, privileges or immunities, dispute procedures, the route for admitting new governments, or the powers reserved to PCH’s officers and board. It cannot say whether government representation is equal across signatories, equal between governments and other constituencies, or equal in some narrower forum.

The report’s language may be accurate, but the mechanism remains unverified here.

This is where the institutional transition intersects with the analysis in Heng Lu’s Note 73, “The Multi-Stakeholder Mirage.” The note argues that participation should not be confused with authorization, and that one must ask who can bind the party that bears a decision’s costs. In this article, that is a method for reading claims, not evidence about PCH’s treaty. A person can be affected by infrastructure or participate in consultation without holding authority to make a binding decision.

The same applies in reverse: a government’s formal relationship with an organization may be legally important without proving that it speaks for every operator or user who depends on that organization’s services.

The relevant questions are not answered by counting names alone. A signatory list could establish which governments entered an agreement, once independently verified. It could not establish how non-signatory governments are affected, whether network operators participate in decision-making, whether users can challenge an outcome, or whether local partners have authority over equipment installed in their facilities. Those questions require different evidence.

The apparent reversal dissolves when the object is specified

The chronology can be written in one line: Woodcock warned in 2015 against an intergovernmental model for oversight of IANA; PCH later reported that it had taken on an intergovernmental treaty form. But chronology alone does not show a reversal in belief. To prove one, a writer would need evidence that the same question was answered differently under comparable conditions. The available records instead show different questions.

In 2015 the relevant control surface was the oversight arrangement for IANA functions and the ability to hold their operator accountable. Woodcock’s preferred tools included stakeholder oversight and contractual remedies. In PCH’s 2023 account, the relevant change was PCH’s own institutional status and relationship with governments. The annual report does not say that the treaty replaced stakeholder oversight of IANA, nor that PCH began operating the IANA functions. The public descriptions do not establish such a connection.

That does not mean the two questions can never intersect. Governments may finance infrastructure, enter contracts, regulate networks, approve facilities or participate in an organization’s governing body. A treaty organization may have operational programs. An operator may rely on a public-sector counterparty. The point is not that the layers are hermetically sealed; it is that each connection should be demonstrated rather than assumed from a common label.

Consider the practical chain for a DNS anycast service. A service operator selects a design and announces routes. A site partner may supply space, power and access. A transit or peering network carries traffic. The Domain Name System responds to queries. A government might sponsor a deployment, approve a local presence, or participate in an organization’s governance. Those are distinct relationships. A treaty’s existence could formalize one of them, but it cannot reveal which one without the treaty and implementation records.

The same discipline applies to IXPs. A support organization may supply equipment or expertise, while an exchange’s local operator runs the switching environment and member networks decide whether to connect. An agreement with a government could help secure a site, training or coordination, but participation by that government does not automatically make it the operator of the exchange or authorize it to speak for every connected network. Conversely, a local network’s technical participation does not make it a treaty party.

The question of mandate also has layers. A government can authorize its own representatives under its domestic law. A treaty can bind its parties according to its terms. A company can authorize employees to act within the company’s authority. An operator can make decisions about the network it runs, subject to laws and agreements. A public forum can collect expertise and objections. These forms of authority may cooperate or conflict, but they are not interchangeable. A meeting attendance count, a partnership list, and a treaty signature are different kinds of evidence.

By separating the objects, we can read Woodcock more accurately. His testimony shows that, in the IANA transition debate, he placed weight on contractual accountability and feared intergovernmental control over that function’s oversight. PCH’s report shows that the organization later presented a treaty-based institutional form as a way to evolve its governance and relationships. It does not show that the first argument was abandoned or that the second arrangement granted broad control over Internet operations.

Operational continuity is more than a legal label

PCH’s transition story sits alongside an operational model that remains dependent on people and organizations beyond the treaty itself. PCH’s 2023 report says it relied on government grants and hundreds of private-sector donors. It lists deployment partners and describes relationships with local exchange points. In its section on peering, it reports activity at 298 IXPs at the end of 2023, alongside counts of sessions and peer networks.

These are organizational figures, useful for understanding the scale PCH says it reached, but not an independent audit of uptime, resilience, traffic, security incidents or the share of Internet operations it controls.

Operational infrastructure is produced by repeated local decisions. Someone must host equipment. Someone must maintain it. Networks must configure peering or accept routes. Someone must carry traffic to and from the site. A DNS service must be monitored and updated. When a deployment depends on a government, a commercial facility, an exchange operator, a volunteer engineer and a donor, a new legal status may change the agreement with one participant while leaving other dependencies in place.

That is why legal form and operational control should be assessed separately. Legal form can define who may sign, own, sue, be sued, receive funds or participate in a governing body. Operational control concerns who can change a live system, who can stop a service, who has credentials, who maintains failover, and who bears the consequences of failure. The treaty could affect some of these matters. The sources reviewed do not establish which ones.

Outcome evidence is a further layer. A list of installed sites is an input or activity measure. It may be consistent with broader access, lower latency or improved redundancy. To establish those outcomes, a researcher would need evidence about service reach, query paths, network resilience, failure behavior, costs, incident rates, or the counterfactual of what would have happened without a deployment. A before-and-after comparison would need to account for simultaneous changes in traffic, connectivity, operators, equipment and upstream routes. The annual report’s deployment count alone cannot isolate the effect of a treaty transition.

The word “resilience” deserves the same care. DNS anycast can distribute service across multiple locations. That architecture can create redundancy and spread some traffic loads, as PCH’s report explains. But an architecture’s intended advantage is not the same as measured service performance. A network may still have common-mode failures, configuration errors, facility outages, route leaks, or dependencies concentrated in a small number of upstream providers. Resilience is an empirical property of a system under failure, not just a label on its topology.

There is also a distinction between service provision and public authority. A nonprofit can provide a valuable service in a market gap without becoming a public-law regulator. A government can fund a deployment without acquiring control over the participating networks. An international organization can convene partners without representing every member of the Internet community.

Those distinctions are especially important when an organization has both operational credibility and a new formal relationship with governments: the former can make the latter seem self-evidently legitimate, while the latter can make the former seem like public authority. Neither inference follows automatically.

PCH’s public descriptions leave a legal-map question

PCH’s present public pages do not all use the same institutional description. Its Careers page calls PCH an intergovernmental treaty organization. The 2023 annual report makes the same transition claim. Its Sponsors page describes Packet Clearing House as a U.S. 501(c)(3) tax-exempt educational nonprofit and non-governmental organization incorporated in the United States. The pages reviewed do not explain whether the sponsor-facing description refers to a separate nonprofit entity, an affiliate, a continuing legal person, a fundraising vehicle, or web copy that has not been updated.

This is not evidence that the transition failed or that any statement is false. Organizations that work across jurisdictions may use more than one legal entity for different activities. The pages alone are insufficient to determine whether that is the explanation here. Nor is a U.S. tax classification a complete map of a separate international treaty organization. It is a specific claim about a legal entity and its tax status.

The proper conclusion is limited: readers need a clear, authoritative entity map to understand which body employs people, receives donations, holds assets, signs government agreements, operates services, and is covered by the treaty.

Woodcock’s public titles underline why names should be tied to dates and documents. The 2015 transcript calls him PCH’s Executive Director. The 2023 annual report carries his signature as Secretary General. PCH’s current people page lists him as Secretary General and on its Board of Directors. These are evidence of how PCH described his role at different times. They do not let us infer which legal person employed him in each period, what powers his title carries under the treaty, or whether the Secretary General can make decisions reserved to a board or member governments.

In profile writing, titles often become a shortcut for authority. “Executive Director,” “Secretary General,” “trustee,” and “representative” can sound self-explanatory. Their meaning depends on constitutive documents, delegations and the decisions at issue. Woodcock’s designation as a CRISP representative in 2015 described his role in a particular transition process; it did not authorize him to bind every number-resource operator. His current title, as listed by PCH, is similarly a role label until the relevant authority and limits are documented.

The entity map is not an administrative side issue. If one legal person receives a grant, another signs the treaty, and a third operates equipment, accountability may travel through contracts between them. A public-service claim is stronger when readers can identify which entity owns the duty and where an affected party can seek remedy. An entity map would also help distinguish state-level accountability, board accountability, donor terms and operational procedures rather than treating them as one undifferentiated “governance” layer.

What the record does establish about Woodcock

The most solid portrait is not a psychological one. It is a sequence of documented roles and institutional choices. In 2005, IEEE Spectrum described Woodcock as working with PCH on Internet exchanges around the world, with hands-on design, equipment preparation and operator support. In 2015, he appeared before a U.S. House committee to argue for an IANA transition that separated ready functions from unresolved accountability questions. In 2023, PCH’s annual report bore his signature as Secretary General and described a treaty-based institutional transition after a long process.

The connective tissue is not a provable private motive; it is the recurring problem of how operational capacity becomes durable. An ad hoc group can get a local exchange started, but continuity may require staff and a budget. A nonprofit can receive grants and donations, but it may seek more formal relationships with governments. A treaty form may offer one route to that formalization, but the available sources do not establish whether it delivered more predictable funding, stronger operational independence, broader service coverage or a new accountability mechanism.

Woodcock’s testimony is also notable for its functional distinctions. He argued for moving the protocols and numbers portions of IANA on schedule while allowing more time for the names function. That is a case for differentiated governance according to the task, rather than a one-size-fits-all institutional design. It does not prove that his later view was identical in every context; the record does not provide that. But it cautions against flattening his 2015 statement into a slogan about all intergovernmental participation.

What can be said fairly is that Woodcock publicly defended one accountability arrangement for IANA oversight and that PCH later reported adopting a treaty-organization form for itself. Whether he personally saw those arrangements as compatible is not established by the sources here. The article does not fill that gap with imagined intention. It can instead show why the two arrangements need not be treated as equivalents: one is about how a function’s operator is supervised; the other is an organization’s stated legal relationship with governments.

This distinction also prevents biography from becoming a proxy verdict. A subject’s credibility should not substitute for evidence about an institution, but neither should an institutional change be retroactively made to disprove every earlier argument by one of its leaders. The question is not whether Woodcock “changed sides.” It is what each arrangement authorizes, who is accountable, and what the consequences are for people who depend on the services.

A practical test for claims of authority

The PCH transition can be evaluated more precisely if its public claims are separated into five tests.

First, identify the legal subject. Is “PCH” the same legal person in each document, or are several entities involved? Which one signed the treaty, receives contributions, employs staff and contracts for deployments? The pages reviewed do not supply that map.

Second, identify the source and scope of authorization. Which states approved, signed and ratified the treaty, and when did it enter into force? What powers does the instrument grant? Which decisions are reserved to governments, officers, a board, local operators or service partners? A source saying “equal representation” needs to name the represented group, body, decisions and voting mechanism before it can be evaluated as a governance fact.

Third, distinguish representation from participation. Governments may be signatories or stakeholders, while operators, companies, civil-society groups, technical staff and users may participate through other channels. The article cannot infer a universal mandate from a short signatory list or from the institutional phrase “the Internet community.” It must ask who is absent, who can object, and whether any participant can bind others.

Fourth, follow the operational chain. For each service, identify who owns or hosts the equipment, controls credentials, announces routes, maintains power and fiber, pays recurring costs, changes configurations, and responds when something breaks. If the treaty affects one link, the corresponding contract or operational record should show how. A legal title alone does not reveal the running system’s control plane.

Fifth, measure outcomes rather than intentions. If PCH says a transition improves stability or lets it serve more countries, the test is not just the number of signatories or deployed sites. It is whether availability, recovery time, route or DNS performance, costs, incident rates, or service access changed, compared with a credible baseline. Institutional reports can be a starting point for that audit, not its independent conclusion.

These tests are not a demand that every small infrastructure group produce a constitutional dossier before plugging in a switch. They are a way to match the scale of the claim to the evidence. A local deployment may need a simple agreement and a clear technical owner. A treaty claim that invokes government representation and long-term governance deserves a documentary record commensurate with those claims.

Nor does a missing public document prove that the underlying work is unsound. It means that the public cannot verify the corresponding claim from the material reviewed. That distinction matters because infrastructural services can be valuable even when their institutional story is incomplete. The remedy for incomplete evidence is to publish the instrument, clarify the entity structure and report outcomes—not to assume either legitimacy or illegitimacy.

The broader lesson is about scope, not sides

There is a persistent temptation in Internet governance to collapse every institutional question into a contest between “the community” and “governments.” That framing hides important differences. A government can regulate, fund, sign a treaty, own a facility or join an advisory body. A technical community can develop standards, test implementations, advise a registry or oversee a service provider. An operator can deploy and maintain a network. An intergovernmental organization can have a treaty-defined mandate. These actions overlap but do not mean the same thing.

Woodcock’s 2015 testimony rejected one proposed location of authority: an intergovernmental model for IANA oversight. Its argument centered on contractual accountability and preserving stakeholder oversight of the IANA operator. PCH’s 2023 report later presented treaty status as an evolution of PCH’s own governance and relations with governments. The records do not show that PCH’s change transferred IANA authority, gave it power over operators, or proved that governments represent all affected networks. They also do not prove that the new status had no operational consequence. The evidence supports neither extreme.

The question “Who governs the Internet?” is therefore too broad to be useful without a noun after “governs.” Who sets the conditions for a particular registry? Who decides whether a network peers at an exchange? Who operates a DNS node? Who can change an IANA registry entry? Who can remove a board member? Who can terminate a contract? Who bears the cost of a service outage? A person or institution may hold authority in one of these domains and not in another.

That is why the status change should be read with both respect and skepticism. Respect, because a treaty is a consequential formal act and the governments and PCH that pursued it deserve to have their stated aims accurately represented. Skepticism, because a label cannot answer the questions of scope, authorization, representation and effect. Neither is a posture of hostility. It is the minimum required to tell institutional history without overstating it.

For Woodcock’s profile, the fairest conclusion is also the most specific one. His public record shows a practitioner who moved from a loosely organized exchange-building effort into leadership of an organization that sought more durable forms. It shows him defending contractual accountability for the IANA functions in 2015. It shows PCH reporting a treaty transition eight years later, with Woodcock then signing as Secretary General. It does not show a personal reversal, a universal mandate, or a demonstrated change in operational outcomes.

The difference between an operator and a governing authority is not always easy to draw. In practice, the same organization can operate equipment, convene partners, advise governments and hold contracts. But every additional role should be described, authorized and audited on its own terms. An organization may support the Internet without governing all of it; a treaty may formalize state relations without replacing the voluntary cooperation of networks; and a person may argue for different mechanisms in different domains without contradiction.

The most important unanswered questions are documentary. What does the founding treaty actually authorize? How are PCH’s treaty organization and the U.S. nonprofit entity related? What does “equal representation” mean in the decision structure? Which decisions remain with local operators and service partners? What independent outcome measures changed after August 2023? These questions can be answered with published instruments and records, not by extrapolating from titles or institutional rhetoric.

Until then, the transition is a meaningful claim about PCH’s legal and governmental relationship, not proof of a general Internet mandate or a new operational command system. And Woodcock’s 2015 testimony remains a statement about accountability for IANA oversight, not a blanket rejection of every intergovernmental organization. Keeping those boundaries visible produces a more useful profile than choosing a side in an abstract governance debate.

Sources