Summary

  • ALLDISPATCH is an IETF-wide discussion and routing venue, distinct from the separately chartered DISPATCH working group.
  • A session recommendation can shape the next venue for a proposal, but formal standards authority remains with the relevant IETF process and responsible officials.

The key infrastructure question is not whether a proposal was discussed. It is whether the discussion produces a traceable handoff into a venue with a mandate, participants and a mechanism for resolving technical disagreement.

The official IETF Datatracker records describe ALLDISPATCH as a place to examine proposals that may require work in an IETF area or another standards-development path. The possible next steps include referral to an existing working group, creation of a new working group or Birds-of-a-Feather session, individual-stream publication, or another venue (ALLDISPATCH charter). That makes the session a coordination control surface: it can reduce duplicated effort and expose a proposal to the people who would have to maintain or deploy it, but it cannot by itself turn discussion into an approved standard.

That distinction matters operationally. A meeting agenda or recommendation records attention and direction; it does not prove adoption, implementation or running-network impact. The Datatracker meeting pages for IETF 118, IETF 119 and IETF 120 are therefore useful as records of what was placed before the forum, while any claim about a completed standards transition requires a later working-group, Area Director or RFC record (IETF 118 session materials; IETF 119 session materials; IETF 120 session materials).

ALLDISPATCH should also not be collapsed into the DISPATCH working group. The two have separate Datatracker identities and records. The distinction is more than naming: a wide forum can surface work that crosses areas or does not yet fit an existing charter, while a working group operates within a defined mandate (ALLDISPATCH group record; DISPATCH group record).

For operators and implementers, the practical test is the handoff. After a proposal appears in ALLDISPATCH, readers should look for a named destination, an accountable chair or Area Director, a document trail and evidence that the receiving venue accepted responsibility. Without those links, the process may have identified a coordination problem without yet reducing it.

The unresolved issue is measurable continuity. Public session records can show that a proposal was discussed and where participants suggested it should go. They do not, on their own, show that competing implementations converged or that deployment risk fell. That evidence appears later—in adopted documents, interoperable implementations, operational measurements and the durability of the resulting work.