Summary

  • The PNODI’s 2 September meeting report says consultant onboarding compressed the start of work by about three weeks; a second draft was expected around mid-October and a one-month public comment period was planned for roughly 20 October–20 November.
  • The consultant can research and shape the draft, but the network retains responsibility for its final content. The consequential evidence will be whether participants can inspect the draft and trace their input into the final report.

The Internet Governance Forum’s Policy Network on Open Digital Infrastructure (PNODI) is approaching a month in which its broadest promise—open participation—will have to meet a specific document and a clock. The network’s 2 September meeting report says the consultant expected in early-to-mid August had not yet been onboarded. Recruitment was then imminent; the work plan had already been compressed by approximately three weeks. The revised schedule anticipated a second draft around mid-October and a public comment period of approximately one month, around 20 October to 20 November. Those are planned dates, not a guarantee that a finished draft will be ready on day one. (Meeting II report)

That distinction matters because the report’s subject is not settled. Contributions gathered before the second meeting raised what should count as infrastructure, how openness should be defined, which technologies belong in scope, and how case studies, the public sector’s role and governance should be handled. The meeting introduced these inputs but did not debate them substantively. A draft can therefore do more than summarize known positions: its boundaries and classification choices will determine what the network treats as a comparable system and what falls outside the frame.

The consultant’s role is unusually clear in one respect. The report says the consultant will review the mailing-list archive and community contributions, conduct research and offer suggestions, not merely assemble submissions. Yet the network keeps responsibility for the report’s final content. This creates a useful division of labor, but it also makes the transition between authoring and accountability important. Readers need to know which claims come from research, which reflect submitted experience, and which remain the network’s judgment. The meeting report says one or two questions might focus public feedback; it does not specify them.

The public-facing PNODI page now advertises a 28 October webinar. It proposes asking what makes a technology or service infrastructure and whether openness should mean interoperability alone or also accessibility, governance, transparency, competition, sustainability and participation. DNS, Internet Exchange Points, encryption and certification services, and AI infrastructure are examples for discussion. That range is promising, but it raises a practical question: can the draft show how those different layers will be assessed with a common framework, rather than treating “open” as one property? (PNODI page)

The IGF’s general policy-network model offers access through open mailing lists, meetings and community consultations. MAG members facilitate, while the Secretariat coordinates and supports the final outputs. These mechanisms can broaden evidence and surface disagreement. They do not, by themselves, establish who participated, whether comments changed the text, or whether a report’s recommendations will be adopted by operators, regulators or standards bodies. The output is a contribution to policy discussion, not a rule imposed on the systems named in it. (Policy Networks)

A stale block on the PNODI landing page still says the work plan and consultation process will be defined soon, even as it lists the September planning meeting and the October webinar. That inconsistency is small but relevant: an open process depends on a reader being able to find the current work plan, draft, questions, deadline and record of responses without joining a private document thread. The published meeting report and webinar notice provide some of that trail, but not yet the draft itself.

The test is not whether a month is inherently enough. It is whether the second draft appears in time to make the advertised period usable, whether feedback questions point to genuine choices, and whether the final report records how evidence altered its conclusions. If the draft arrives late or comments cannot be followed through, participation risks becoming a count of submissions. If the network publishes a usable draft, explains the consultant’s role and shows how it resolved competing input, the delay may still yield a disciplined stocktake.

The distinction between an invitation to speak and a visible route from evidence to final judgment is what will determine the consultation’s value.