Summary

  • Revision 05 of The IETF is for Everyone appeared on 11 August 2026. It is an active individual Internet-Draft with no RFC stream, intended status, Responsible Area Director or formal standing—not an adopted IETF plan.
  • The revision expands its account of awareness and participation, yet retains a roadmap that tells the IAOC to allocate at least 5% of the 2027 meeting budget to Global South participation support.
  • RFC 8711 eliminated the IAOC in 2020. Under IASA 2.0, the IETF LLC now handles administration and finance: the Executive Director develops and executes the budget, while the LLC Board approves and oversees it.
  • The draft also asks “IETF Leadership” to form an Inclusion Task Force by Q2 2026, then carries that date into an August revision without marking the action completed, unstarted, superseded, rebaselined or conditional on adoption.
  • A thin action-owner concordance would preserve the proposal’s ambition while naming current authority, adoption trigger, budget chain, deadline state, evidence and institutional handoff.

A live revision with an inherited operating map

The Datatracker record is unambiguous about status. draft-attoumani-ietf-inclusion-05 is an active individual submission, not a working-group document. It has no RFC stream, intended RFC status or Responsible Area Director, and its IESG state is “I-D Exists.” The page carries the standard warning that anyone may submit an Internet-Draft, that the document has no formal standing in the standards process and that it is not endorsed by the IETF.

That boundary matters twice. It prevents the draft’s proposals from being reported as policy. It also prevents the calendar inside the draft from being treated as an institutional commitment that the IETF has missed. Publication means a proposal is available for reading and discussion. It does not create a mandate, appropriate money or start a programme.

The document history records revision 05 on 11 August 2026 and revision 04 on 8 February. The announcement describes an 18-page document with an implementation roadmap, concrete proposals and metrics. The frozen revision 05 says it added awareness as a prerequisite, a participation-continuum model, more partnerships and an illustrative IGF 2026 pilot. Those are substantive editorial additions.

But the action machinery did not move with them. A comparison with revision 04 and the official 04-to-05 diff shows the roadmap’s institutional owner and near-term clock carried forward. The newer revision refreshed the argument while leaving the operating map in an earlier institutional and calendar state.

The owner was abolished six years ago

Section 9.9 proposes a 12-month Global Inclusion Working Group. Its governance line says the group would report directly to the IESG and the IAOC through monthly updates and a final report. Section 10 then calls on the IAOC to allocate a dedicated line equal to at least 5% of the meeting budget for Global South participation support in the 2027 budget cycle.

The percentage is precise; the addressee is not current. RFC 8711, published in February 2020, created the IETF Administrative Support Activity 2.0 arrangement. It explicitly eliminated the IETF Administrative Oversight Committee and transferred its oversight and advisory functions to the IETF LLC Board. A proposed 2027 allocation therefore cannot be made actionable merely by retaining the acronym of the former committee.

Substituting “LLC” everywhere would be too crude. RFC 8711 draws an authority map, not a single successor label. The IETF LLC is responsible for operations, finance, budgeting, fundraising and administrative compliance, but it has no authority over standards development. Within the annual budget process, the Executive Director develops, executes and reports on the budget. The LLC Board reviews and approves the budget and oversees significant financial matters. IETF community and standards leaders have their own remits; they are not a generic finance office.

The current IETF Administration overview describes the LLC as the legal and administrative home for the IETF’s finances and operations. Its financial statements and budget page is the public surface for annual plans and reports. At the reporting cutoff, that page exposed final annual budget material through 2026, not an adopted 2027 budget. That observation says nothing about whether preliminary 2027 planning exists behind the scenes.

The correction the draft needs is therefore a chain, not a find-and-replace: who proposes the programme, who decides whether the IETF should undertake it, who prepares a budget line, who approves it, who executes spending, and who reports the result? A recommendation can cross several institutions without making those institutions interchangeable.

Existing spending is part of the evidence

The stale IAOC reference must not be inflated into a claim that the IETF does nothing about access or inclusion. The IETF LLC 2026 final budget and its meetings budget contain current spending relevant to participation: diversity and inclusivity-supported services, travel grants, onsite childcare and remote-participation services appear among the budget lines.

Those entries do not prove that the individual draft’s proposed programme has been adopted or that its targets have been met. Nor do they settle whether a 5% share is appropriate. They establish a narrower and important fact: the administrative system already has live budget owners, categories and execution practices for at least some access-related work.

That makes the outdated owner more consequential, not less. A proposal intended to influence an actual budget should connect to the present budget process and explain whether it supplements, consolidates or redirects existing lines. Otherwise a reader cannot tell whether “5%” describes new money, a floor across existing services, a reclassification, or an aspiration awaiting a decision.

A date needs a start event and a state

The same problem appears in time. Section 10 asks “IETF Leadership” to establish an Inclusion Task Force by Q2 2026. The appendix places consultation, task-force formation and first translations in Q2, followed by the start of task-force work in Q3. Revision 05 was posted on 11 August, after Q2 ended and during Q3.

There is no contradiction if the dates are read as an early proposal later overtaken by events. The difficulty is that revision 05 does not tell the reader which event occurred. The Q2 items are not marked completed, not started, delayed, superseded, withdrawn or reset. Nor does the roadmap state that its clock begins only after community adoption. The calendar survives, while its baseline remains implicit.

This is not evidence that the IETF missed a deadline. An individual draft cannot impose one. It is evidence that the document no longer tells a future adopter how to interpret its own clock. If adopted in September, does “Q2 2026” mean immediately, retroactively, or in the second quarter after adoption? If related work already happened elsewhere, what counts as completion? If the proposal remains just a contribution, should the dates be examples rather than commitments?

A deadline becomes governable only when it has a trigger and a state transition. The trigger could be working-group adoption, an IESG or IAB decision within its remit, an LLC Board budget approval, an Executive Director instruction or a separately authorized programme launch. The state could be proposed, authorized, funded, in progress, completed, rebaselined or withdrawn. Without both, a date offers urgency without accountability.

The minimal concordance

The fix need not turn the draft into a project-management system. A compact action-owner concordance can sit beside the roadmap and contain only the fields required to coordinate authority:

  1. the proposed action and observable output;
  2. the exact proposal revision and source passage;
  3. separate proposal, adoption and implementation states;
  4. the current accountable office and a named role;
  5. the authority source and its limits;
  6. for money, the budget preparer, approver and executor;
  7. the triggering event and baseline date;
  8. the deadline, current state and reason for any rebaseline;
  9. dependencies, privacy or resource constraints and consultation owner;
  10. the evidence that would demonstrate delivery;
  11. a handoff record when an office is renamed, replaced or eliminated; and
  12. correction history and the next review date.

For the 2027 budget proposal, the concordance would not pre-approve the 5% figure. It would state that the draft proposes it, identify the current administrative roles that can prepare, approve and execute a line, identify whatever community or governance decision is required before budget work begins, and record the public evidence once a decision is made. For the task force, it would replace “IETF Leadership” with the specific body or role that can charter or sponsor the work and mark the old Q2 date with an honest state.

This is a thin interface between proposal and institution. It leaves programme design, regional priorities, selection rules and future adaptation open. It also makes correction cheap: when an institution changes, the owner field and handoff can be revised without pretending that the whole policy argument has changed.

Publication is not execution

Heng Lu’s governance frame is useful here because it separates participation from mandate and specification from adoption. More voices can improve the evidence, expose missing constraints and alter the choice. Their presence does not, by itself, identify the actor authorized to commit funds. In the same way, publishing a roadmap is valuable but does not turn text into running operations.

The distinction protects the proposal as much as the institution. If publication, adoption, appropriation and delivery are collapsed, critics can dismiss an unimplemented proposal as a failed programme, while supporters can describe a live draft as an institutional promise. A concordance prevents both errors. It shows what the text asks for, what has been authorized, what has been funded and what has actually happened.

The Internet-Draft process is designed for revision. That makes stale owner fields especially repairable. Revision 05 is not evidence of indifference or bad faith; it is an opportunity to update the document’s administrative references and reset its action clock before readers assign the text more authority than it possesses.

The strongest inclusion proposal is not the one with the largest number of targets. It is the one whose next action can survive contact with the current institution: a real owner, a bounded power, an observable handoff and a clock that starts from a named decision.

Sources

  1. IETF Datatracker: current document record
  2. IETF Datatracker: document history
  3. IETF archive: revision 05
  4. IETF archive: revision 04
  5. IETF Author Tools: revision 04-to-05 diff
  6. IETF Internet-Draft announcement
  7. RFC 8711: Structure of the IETF Administrative Support Activity, Version 2.0
  8. IETF Administration overview
  9. IETF LLC financial statements and budgets
  10. IETF LLC 2026 final budget
  11. IETF LLC 2026 meetings budget
  12. Heng Lu: Minimum Initial Specification, Localized Future Decision, and Voluntary Adoption