Summary

  • In a public report prepared for the IETF LLC Board meeting scheduled for 1 September 2026, Executive Director Jay Daley says he appointed himself Managing Director, IETF Secretariat.
  • Daley says the post had been empty since the former postholder left the IETF contract and the Secretariat split in two, but that the vacancy had no practical effect because its functions were absorbed into wider LLC work.
  • The appointment does not rewrite an RFC or enlarge the LLC’s standards authority. It does show the need for a role-absorption and appointment receipt linking each inherited function to its current team, accountable officer, authority boundary and retirement trigger.

The appointment fills a title after the work moved on

The IETF Administration LLC’s public Executive Director report contains an unusually plain piece of institutional housekeeping. A role called “Managing Director, IETF Secretariat” remains defined in several RFCs. Alexa Morris was the last postholder. After she moved away from the IETF contract and the Secretariat was divided, no single person occupied the post. Jay Daley now reports that, as Executive Director, he appointed himself.

Daley also supplies the limiting facts. He says the decision was within the Executive Director’s authority, that all of the post’s specific functions had long ago been absorbed into the IETF LLC’s overall work, and that the vacancy had no practical effect. This is not a report of a new operating layer. It is an attempt to close a policy hole left by a title whose organisational setting disappeared before its standards references did.

Timing matters. The report was published for the LLC Board meeting scheduled for 1 September at 19:00 UTC. The agenda puts the Executive Director report in the public part of that meeting. At this Article’s cutoff, the meeting is still in the future. The report is public evidence of the appointment; it is not an approved minute and does not prove a Board vote.

The underlying service did not wait for the title. A July staffing update says that Meetings & Events and Community Support now form the Secretariat as two teams, with the restructuring fully effective from 1 August. The work therefore has named operating homes even though an RFC-defined person-shaped interface was vacant.

That distinction is the news. The IETF did not suddenly recover a missing capability. Its Executive Director put a person back into a formal role after the capability had already been distributed.

The standards record still expects a named person

The title is not merely an item in an old organisation chart. RFC 8717 introduced it in 2020 as part of IASA 2.0’s administrative terminology cleanup. The document updated a group of earlier RFCs—2028, 2418, 3710, 3929, 4633 and 6702—to use “Managing Director, IETF Secretariat.” In other places, it removed an obsolete administrative role instead of renaming it. That choice left a named individual as the compatibility point for some functions.

RFC 8713 defines the Managing Director as the person charged with operation of the Secretariat function. RFC 3710, read with RFC 8717’s update, makes the office an ex-officio member of the Internet Engineering Steering Group. The boundary inside that same charter is essential: all members may participate in discussion, while IESG decisions are made by the IETF Chair and the Area Directors.

The office therefore combines several things that are easy to blur in a short announcement. It is an operating responsibility. It is a named administrative interface in standards documents. It carries an ex-officio discussion position. None of those facts creates a general vote, a protocol mandate or ownership of the standards process.

The newer administrative constitution draws the wider perimeter. RFC 8711 assigns day-to-day IASA operation, hiring and staffing discretion to the IETF Executive Director. It also states directly that the LLC has no authority over the IETF standards-development process. Executive Director and Board decisions have a review path, and major changes to the IASA structure require community consensus followed by a new Best Current Practice document.

This makes the self-appointment less dramatic and more revealing. The Executive Director already has broad administrative responsibility; taking the residual Secretariat title can be a practical way to provide the person required by surviving text. But administrative authority to fill a role is not authority to change the standards that define it. An appointment can make the current state coherent. Only the standards process can repair the durable record.

The IETF already diagnosed the mismatch

The policy hole was not discovered in August 2026. The second IASA 2.0 retrospective, published in December 2024, examined the same role and reached a more structural conclusion. It said that delivery by teams had blurred the boundary between the LLC and Secretariat in a positive way and that the special Managing Director role appeared unnecessary. Its proposed remedy was an RFC replacing references to the Secretariat with IASA and removing individual support roles wherever a named person was not needed.

An Internet-Draft later attempted part of that repair. draft-rsalz-8717-update-01 described the Managing Director terminology as no longer relevant and proposed referring to the responsible job or entity instead of a particular staff title. The Datatracker now marks the draft expired and archived. It is useful evidence of an available design, not policy in force.

That unfinished sequence explains why the appointment is neither empty theatre nor a final solution. Leaving the post vacant did not interrupt the work, but it left standards-defined functions without an obvious current postholder. Filling it restores a formal endpoint, but it also concentrates several inherited references in the Executive Director without showing, in one place, which are performed personally, which are delegated to teams and which exist only as historical compatibility language.

The IETF’s disclosure deserves credit for naming the policy hole. Institutional transparency is not proved by avoiding awkward facts; it is proved by stating them with their limits. Yet the report is still a paragraph inside a management update. A future reader should not have to reconstruct the current authority map from several RFCs, a retrospective, an expired draft, a staffing post and one meeting report.

Publish a role-absorption and appointment receipt

The missing object is small enough to build. A role-absorption and appointment receipt would begin with the exact title, postholder, appointing office, authority source and effective time. It would then list every material function still assigned to that title by an active RFC and map it to the team that performs the work, the officer accountable for it and any delegated or substitute capacity.

The receipt should keep participation and decision rights in separate columns. For the IESG, it should state that the office is ex officio, identify the scope of discussion participation and show that decisions remain with the Chair and Area Directors. For the LLC, it should link the operational discretion in RFC 8711 and repeat the express absence of standards-development authority. A title should never be allowed to borrow powers from the meetings it attends.

The same record should show its review and retirement paths. The review field can point to the mechanism for challenging an Executive Director or Board decision. The retirement field can name the event that supersedes the legacy title: publication of a replacement BCP, an explicit RFC update or another community-approved change. If the cleanup draft is revived or replaced, the receipt can link the new standards action without pretending that an expired draft already governs.

Finally, the receipt needs a version history. A team reorganisation, delegation change, interim appointment or standards update should append a dated delta. The public does not need personnel files or internal correspondence. It needs a durable answer to four questions: what function exists, who performs it, by what authority and where does that authority stop?

That design follows the operational reality instead of the mythology of a title. The Secretariat’s function is real. Its continuity did not depend on keeping one person in one inherited office. The appointment repairs the formal interface for now; the receipt would show why that repair does not grant new power, and the RFC process can decide whether the interface should remain at all.

Sources

  1. Executive Director report for the 1 September 2026 IETF LLC Board meeting
  2. Agenda for the 1 September 2026 IETF LLC Board meeting
  3. IETF Administration LLC Board page
  4. RFC 8711 — Structure of IASA 2.0
  5. RFC 8717 — Consolidated Updates to IETF Administrative Terminology
  6. RFC 8713 — Nominating and Recall Committees
  7. RFC 3710 — IESG Charter
  8. Second IASA 2.0 retrospective
  9. Expired draft updating RFC 8717
  10. IETF LLC Secretariat restructuring and staffing update