Summary

  • On 3 September 2026, the IESG opened external review of proposed MOPS charter 01-02, said it had made no determination and invited comments by 13 September.
  • The approved 2019 charter calls MOPS experimental and promises a group-level decision after two years: continue through rechartering or close. The proposed text removes that paragraph.
  • A different sentence remains: a particular work item may be removed when it no longer attracts sufficient interest. That is an item-level exit, not a conclusion about whether the Working Group itself should remain.
  • The public group history marks the old continue/recharter/close milestone Done on 5 April 2022, but the proposed charter does not bind that state to the original question, evidence considered or reasons for normalizing the group.
  • A short experiment-closeout record would preserve that institutional memory without restoring a stale deadline, judging MOPS successful or failed, or limiting the IESG’s ordinary power to recharter or disband a group.

One paragraph is doing more than housekeeping

The visible edit looks easy. MOPS was formed in 2019 with a final paragraph saying the IESG was establishing the Working Group on an experimental basis and intended to review it after two years, either to continue it through rechartering or to close it. Proposed charter 01-02 omits that paragraph.

There is a sound reason to remove stale prospective language. The MOPS group history marks the corresponding continuation milestone Done on 5 April 2022. Minutes from IETF 126 in July 2026 describe the contemplated charter change as a light update that would remove a paragraph anticipating a review that had already occurred. Keeping a promise written in the future tense after the promised event has passed can mislead a reader about the current state.

But deletion has two meanings. It cleans up an expired instruction. It also removes the only sentence that identifies MOPS as an institutional experiment and asks for an explicit judgment about the group itself. The proposed charter records the first effect. It does not explain the second.

That is the narrow issue now before the community. The IESG notice says no determination has been made. Comments are due on 13 September, and the Datatracker page for version 01-02 lists an 8 October telechat. A proposed charter is not present authority, and a scheduled meeting is not a verdict.

The experiment answered a group-level question

The historical record shows why the sentence existed. During the 2019 charter review, an IESG ballot concern described MOPS as unlike many other groups and asked how the IETF would decide whether this experimental form was a success or should close. A milestone requiring the IESG to choose continuation, rechartering or closure was then added.

That origin matters. The question was not merely whether one draft still had authors. It concerned whether a standing venue that gathered operational experience from media companies, network operators and other standards bodies was a useful IETF form. MOPS can document requirements and operational information, publish informational work, redirect protocol questions and maintain liaison connections. Those functions cross document boundaries.

The public group history supplies an outcome state: Done. The current public page also displays the continuation decision among completed milestones. That is evidence that the review should not be described as forgotten or never held. Yet “Done” does not tell a later reader which criteria were applied, what evidence mattered, what the IESG decided about the experimental premise or why an ordinary continuing charter was the right next state.

This Article does not claim that no fuller explanation exists anywhere in the IETF’s archives. The verified point is narrower: the proposed charter and the public state pages reviewed here do not carry that explanation into the instrument that would retire the experimental clause.

A work item can leave while the venue stays

MOPS has another exit rule, and proposal 01-02 keeps it. A particular work item requires continuing interest; if enough interest disappears, the item may be removed from the Working Group’s list.

That is useful discipline. It helps prevent a draft from remaining on the agenda merely because it once entered the group. It also fits the July meeting’s distinction: the Area Director said the work items matter greatly as the contract between the IETF community and the group, while milestone dates can be updated and are not required in the same way.

But item exit and group exit answer different questions.

An item-level test asks whether participants still want to perform a specified task. A group-level test asks whether the venue, with its recurring intake, liaison and dispatch-like role, remains the right institutional container. Removing the only current item could leave the venue available for later input. Continuing one useful item could coexist with a weak reason for keeping the wider venue. Neither fact decides the other.

Ordinary IETF control remains. RFC 2418 says working groups are generally task-bounded, describes disbanding after completion and preserves recharter, chair change or disbanding when work or assumptions no longer support the charter. The experimental paragraph is therefore not the IESG’s only legal or procedural route to closure. Its distinctive value is evidentiary: it named an unusual institutional hypothesis and required a deliberate answer.

The draft changes more than one line

The proposed charter largely preserves the established MOPS remit. It continues to collect media-related operational experience, connect video-industry and Internet-engineering participants, document requirements and send protocol-specific work to more appropriate groups or areas.

There are smaller clarifications. Where the approved text spoke of seeking publication as RFCs, the proposal specifies informational RFCs. Where it said MOPS might dispatch a matter or document, the proposal says it may redirect it. It also adds two current milestones: a September 2026 last call and a November submission to the IESG for Network Overlay Impacts to Streaming Video.

The current documents page lists that draft as the group’s one active Internet-Draft and lists three informational RFCs. Those outputs belong in the evidence. They are not a mechanical score. Four publications would not prove that the experimental venue was legitimate; one active draft would not prove it was unnecessary. A serious conclusion would also consider whether operational issues found a useful home, whether protocol work was redirected cleanly, whether external updates improved IETF decisions, whether participation remained broad enough and whether another venue could have performed the same function with less institutional weight.

Close the experiment without inventing a new gate

The missing object can be small. Before approving deletion, the public record should join six things:

  • the exact 2019 experimental question and charter revision;
  • the review’s decision date and accountable IESG act;
  • the evidence classes considered, including outputs, participation, referrals and liaison value;
  • the conclusion about continuation, closure or modification, with a concise rationale;
  • the charter state that follows and the ordinary group-level exit route that remains; and
  • a link from the removed clause, the Done milestone and the approved successor charter to the same closeout record.

This is not a request for a retrospective performance score assembled to justify a predetermined answer. Private personnel discussion, individual participation histories and confidential liaison material need not be disclosed. The record can state categories, findings and limitations without turning volunteers into metrics.

Nor should the stale two-year sentence simply be copied forward. A calendar can force attention, but repeating an already-consumed promise would obscure rather than clarify the state. The right repair is to close the old experiment explicitly and state how future group-level review will occur under ordinary IETF process.

Heng Lu’s continuity distinction supplies a bounded question: what useful function needs to continue, and what institutional form follows from that need? MOPS is not a registry, and the note’s arguments about number assets, sovereignty and liability do not transfer here. The applicable point is only that continuity of work is not itself a complete reason for institutional continuity.

The IETF may reasonably conclude that MOPS has ceased to be experimental because the form proved useful, because its risks were manageable or because ordinary oversight is sufficient. It may conclude something else. The 2026 draft need not relitigate seven years of work. It should make the transition legible.

Sources

  1. IESG — WG Review: Media OPerationS (mops), 3 September 2026
  2. IETF Datatracker — proposed MOPS charter 01-02
  3. IETF Datatracker — approved MOPS charter 01
  4. IETF Datatracker — MOPS charter history
  5. IETF Datatracker — MOPS group history
  6. IETF 126 — MOPS meeting minutes
  7. MOPS mailing list — March 2026 charter discussion
  8. IETF Datatracker — MOPS documents
  9. RFC 2418 — IETF Working Group Guidelines and Procedures
  10. Heng Lu — The Registry Continuity Fallacy