Summary

  • RFC 5111 let an Exploratory Group use Working Group review, tools, openness rules, chairs' infrastructure and document tracking, but its charter had to exclude standards-track documents and protocol specifications.
  • Its basic outputs were a proposed Working Group charter and evidence that RFC 2418 formation criteria had been met; even then, a separate IESG vote decided whether a Working Group would exist.
  • Mailing-list traffic and optional documents could show engagement, but they could not substitute for resolving the gated questions within a short, bounded mandate.

A visitor opening the IETF's tools could have mistaken an Exploratory Group for a Working Group. It had a chair. Its name appeared in familiar infrastructure. Its participants followed the same openness and meeting rules. Documents moved through established tracking and PROTO shepherding. Its chair joined the WGCHAIRS list. Community review, IAB scrutiny and IESG review accompanied formation.

RFC 5111 made that resemblance deliberate. The experiment was not designed to create a weaker standards body. It was designed to give a stalled proposal a visible, accountable place to finish the work required before a standards body could be created.

The unresolved-admission problem

RFC 2418 asks whether proposed work is clear, relevant and achievable; whether it overlaps existing groups or other standards bodies; whether enough participants, expertise and users exist; whether the IETF has a proper role; whether intellectual-property issues are understood; and whether the effort is genuinely open rather than an attempt to bless work that meaningful IETF input cannot change.

A prospective group could have obvious interest and Internet relevance while still lacking answers to some of those questions. Before RFC 5111's experiment, the practical result could be delay: no BOF, no Working Group and no formal surface on which remaining concerns and next steps were visible. Participants could see activity without knowing its institutional status.

The Exploratory Group was a way to formalise that uncertainty. The IESG could propose one when relevance and interest had been shown but one or more formation criteria remained unmet. It could be the first step toward a Working Group or an intermediate step after a BOF. Formation after a second BOF was not recommended. None of those positions was a promise of conversion.

A charter for prerequisites, not a charter for protocol work

The core boundary appears in the permitted milestones. Every EG charter was expected to include two basic outputs:

  1. a proposed Working Group charter; and
  2. a document demonstrating fulfilment of the RFC 2418 formation criteria.

The IESG could add a problem statement, requirements document, literature review or review of current practice. Those were optional, and only acceptable if they did not compromise timely delivery of the basic milestones.

Then RFC 5111 drew the bright line: an EG charter must not include milestones for standards-track documents or protocol specifications.

That prohibition is the design, not a missing feature. If the unresolved question is whether a group should receive protocol-development authority, allowing it to exercise that authority while the question is open would turn the experiment into its own answer. A polished protocol draft could acquire momentum, adopters and political cost before anyone had decided whether the IETF should form the group, whether overlap was resolved or whether the charter was achievable.

The clock was part of the authority boundary

An EG should initially run for six to twelve months, with six months as the default. The IESG could extend the initial milestones by another six months; extensions beyond that were not recommended.

The short horizon protected both sides. Contributors received formal recognition, tools and a visible list of concerns. The institution received evidence without creating an indefinite quasi-Working Group. Expiry forced a decision: the prerequisites had been satisfied, they had not, or the original hypothesis needed to be reframed.

A long-lived exploratory body can accumulate the appearance of permanence. Meeting cadence becomes constituency. Document volume becomes presumed mandate. External observers begin treating names and drafts as settled institutional positions. RFC 5111's clock limited that conversion of activity into authority.

An experiment around the experiment

The process change was itself bounded. RFC 5111 described an RFC 3933 experiment lasting eighteen months from IESG approval, with no more than three Exploratory Groups. The IESG had to announce approved formations publicly. The experiment did not alter RFC 2418's Working Group criteria or RFC 2026's Internet Standards Process.

This double boundary matters. The EG tested whether formalised pre-formation work could accelerate resolution. RFC 5111 did not silently rewrite ordinary process for every future group. The process experiment needed its own scope, duration and evaluation, just as each EG needed a charter, milestones and expiry.

Familiar machinery, different authority

Operational equality did not mean constitutional equality. EGs used the same formation review path, community announcement, IAB and IESG review, open participation, meeting requirements, tracking tools and chair infrastructure as Working Groups. The name was supposed to contain “EG” precisely so that the distinction remained legible.

The tools proved that work was visible and reviewable. They did not prove that formation criteria were satisfied. A chair appointment proved accountable coordination, not a delegated protocol mandate. A tracked draft proved an object for comment, not an adopted standard. Access to WGCHAIRS proved integration with the process, not equality of authority.

What counted as success

RFC 5111 put the basic milestones ahead of incidental achievement. An EG that did not progress on them could not be judged successful merely because it produced a literature review or requirements document. Completion had to occur within the chartered time, and feedback from the IESG, IAB and community had to be positive enough to lead the IESG to vote on forming a Working Group.

Mailing-list activity was a potential measure of continuing engagement. Minimal traffic could make an extension unattractive. But the inverse did not follow: heavy traffic did not prove that the charter was clear, overlaps were resolved, expertise was sufficient or an IETF role existed.

The decisive receipt was not message count. It was a later IESG decision, made after the evidence had been reviewed.

The evidence ladder

The process separated records that are easy to collapse:

  • demonstrated interest did not prove readiness;
  • public EG formation did not create a Working Group;
  • a chair and tooling did not confer standards authority;
  • a problem statement did not complete the basic milestones;
  • completed milestones did not guarantee positive review;
  • positive review did not itself constitute the IESG vote;
  • a formed Working Group did not guarantee an RFC;
  • an RFC did not prove interoperability or deployment.

Each record answered a narrower question. Leadership lost control when it treated a familiar interface as evidence that the next authority transition had already occurred.

Sources