Summary

  • A proposed NMOP charter would permit AI experiments only in existing anomaly-detection and incident-management work, after a proposal states boundaries, exit criteria and an implementation commitment.
  • Working-group consensus and Area Director agreement would be required before a trial starts; chairs and the AD would cap the number running at once.

Analysis

An AI experiment can sound harmless until someone asks what it may touch, who has to act on its output, and when the trial ends. The Network Management Operations Working Group’s proposed charter starts with that last question. In version 01-01, the IETF has drafted a narrow permission slip for AI: anomaly detection and incident management, with a written exit route before work begins.

The document is still a draft. The IETF Datatracker marks version 01-01 “Draft Charter Rechartering”, last updated 26 October 2026. The current approved charter remains version 01. That status line matters: the proposed permission has not yet become the group’s operating scope.

The new paragraph ties four controls together. An experiment must sit inside existing NMOP work on anomalies or incidents. Its proposal must state boundaries, exit criteria and an implementation commitment. The working group must reach consensus, and the responsible Area Director must agree, before it starts. The chairs, consulting the AD, must keep concurrent experiments within the group’s capacity to support them. The draft bars NMOP from developing AI models, agent architectures or agent protocols; experiments in other areas would require another charter update.

This is more than a list of fashionable nouns. The approved charter already allows discussion of short-term experiments and gives operator presentations default priority at meetings. In July, NMOP’s IETF 126 minutes captured the awkward question behind the new clause: would the group become a major venue for AI-agent work, or merely a temporary home? The chairs said they were still deciding where AI drafts belonged and planned to ask their authors about scope, progress and open-source engagement. The goal was to gather enough evidence to consider a specific experimental focus in the charter.

The October draft is that conversation turned into a gate.

The gate has a sensible order. First define the patch of work: anomaly detection and incident management already sit inside NMOP’s remit. Then ask the group and its AD to approve a particular proposal. Finally limit the queue to experiments the chairs and AD can actually supervise. A working group is a volunteer standards forum with finite agenda time; multiplying trials does not multiply reviewer hours. The draft puts that arithmetic in the open.

The harder word is “exit”. A proposal must contain exit criteria, but the charter supplies no common yardstick for them. That leaves each experiment to specify what would count as success, failure or a reason to stop. A useful proposal would name the network or dataset under test, the operator responsible for the trial, the output that may reach a human, the evidence to be retained, and the event that ends the test. Those details are editorial tests for a serious proposal, not text the draft already requires.

The distinction matters because anomaly detection and incident management sit close to operational attention. A detector can move a signal into an operator’s queue; incident processes determine who sees it and what happens next. The standards group can set the terms of its own discussion and experiments. The operator still controls the live network and bears the cost of an alert that distracts, a missed signal that delays response, or a trial that outlives its usefulness. That is Running-Code Primacy in practical form: the meeting can shape a tool, but people operating the network carry the consequence.

The clause also keeps the permission deliberately small. It does not open an IETF workshop for model-building or agent protocols. A proposal that wants to explore another AI area must return to the charter process. RFC 2418 describes a working-group charter as the agreement that sets a group’s tasks and milestones; a substantive recharter follows the procedure for a new charter and goes to the IESG and IAB for approval. The boundary is therefore institutional as well as technical: scope changes have to come back into the open.

The weak point is the gap between an exit criterion on paper and an exit decision in practice. Who verifies that the criterion was met? Does the proposal name an operator who can stop the trial? Will the working group publish a result when the answer is “stop”, or only when a prototype works? The proposed text leaves those answers to the experiment proposal and the group’s process. That flexibility can fit very different trials; it can also make accountability hard to compare.

The test for this recharter is not whether “AI” appears in a charter. It is whether future proposals make permission, implementation and stopping conditions visible to the operators whose networks are involved. NMOP has drawn a line around the experiment. The next draft, and the first proposal submitted under it, will show whether the line has a gate that closes.

Sources