Summary

  • The IETF Administration LLC says its recent Secretariat insourcing takes full effect on 1 August 2026, with Community Support and Meetings & Events becoming two distinct teams.
  • The route inside was not a simple change of logo. From 1 April, the Secretariat staff moved from a bundled vendor service to an employer-of-record arrangement designed to preserve the team while giving the LLC more control over people and resources.
  • RFC 8711 and RFC 8712 leave a hard boundary in place: the LLC administers operations, finance, fundraising and contracts, but it has no authority over the IETF standards-development process.

A support function changes its institutional address

The IETF’s newest organisation chart looks like a staffing announcement. It is better read as an accountability map.

On 30 July, Executive Director Jay Daley said the IETF Administration LLC had recently insourced the Secretariat and that a related restructuring would take full effect on 1 August. The old combined function is now presented as two teams. Community Support has four people and handles the machinery around the community and its leadership groups. Meetings & Events has five and runs the work needed to put meetings on. Together, they still constitute the IETF Secretariat.

The change has a longer procedural trail. July 2025 board minutes record discussion of the expiring Secretariat contract and an RFP. In October, the board reviewed sourcing options and asked the executive director to explore one option in depth while putting the RFP on hold. By March 2026, the board was asking about direct reports and the future management structure. The public decision arrived on 31 March: from 1 April, Secretariat staff would be provided through an employer-of-record, or EOR, arrangement rather than through the familiar bundled services contract.

Association Management Solutions did not vanish from the picture. The announcement said AMS would be paid by the LLC as employer of record for the Secretariat staff, and that most of the existing team would remain. The practical shift was from buying an integrated service from one supplier to managing a continuing group of people more directly, while using the EOR for the employment layer.

That distinction matters. “Insourcing” can sound as if every task, contract and employment relationship has been pulled into one corporate payroll. The published model is more specific. The LLC has drawn the Secretariat’s work and management line inward, but retains external dependencies. The Meetings & Events team is supported by Linespeed for the meeting network and Meetecho for remote participation. Other LLC teams also use contractors. The result is a mixed operating model, not a vendor-free institution.

The risk being removed was concentration

The March announcement named the problem unusually clearly. Community support and meeting operations had been bound into one contract and supplied by one vendor. The LLC judged that concentration to be a major strategic risk. It also concluded that people doing community-support work hold institutional knowledge that is better attached to individuals than buried inside a service specification.

The EOR arrangement was chosen to keep the team together, preserve accumulated knowledge and provide greater flexibility over staffing. The LLC also forecast savings over the five-year term of the contract. The July restructure then split the combined Secretariat into two accountable units, citing clearer responsibility, more focused roles, better distribution of work and vacancies left by two departures.

This is a plausible response to key-person and supplier risk. A service contract can state outputs, but it can make the institution’s actual capacity difficult to see: who knows the exception paths, who can reassign work, who owns the handover, and what happens if the vendor relationship ends? Bringing the management line closer makes those questions answerable inside the LLC.

It does not eliminate concentration; it relocates it. Institutional memory now depends more visibly on the LLC’s own management, documentation and succession practices. The executive director receives more direct organisational load. The board must oversee a larger operating surface. Specialist vendors remain critical at the edges. A successful insourcing therefore cannot be measured only by staff continuity on 1 August. It must also produce durable records, separable services and credible replacement paths.

The standards boundary did not move

The most important line on the new chart is the one that is absent from it. Neither Community Support nor Meetings & Events acquires authority to decide technical consensus, approve an Internet-Draft or change the standards process.

RFC 8711 created the current IETF administrative structure with that separation built in. The LLC provides the corporate legal home and administrative support. Its responsibilities include operations, finances, fundraising and compliance. The document expressly says the LLC has no authority over standards-development activities. Strategic oversight belongs to the LLC Board; day-to-day administration belongs to the executive director and staff. Standards work remains with the IETF’s community processes and bodies, including the IESG and IAB within their defined roles.

RFC 8712 reinforces the same allocation from the relationship with the Internet Society. The IETF is responsible for the development and quality of Internet standards. The LLC is solely responsible for administration, including negotiating, signing and overseeing the contracts needed to support that work.

This is not ceremonial drafting. Administrative actors control calendars, meeting access, tools, records, budgets, contracts and the continuity of support on which volunteer processes depend. Those are consequential levers. Yet consequential support is not the same as a mandate to choose technical outcomes. The legitimacy of the arrangement depends on keeping both facts visible at once: administration can shape the conditions of participation, and its formal authority is still bounded.

Publish the operating map, not only the headcount

Lu Heng’s reality-layer test is useful here. An institution acts through boards, staff, contracts and policies. Governance becomes legible when the public can see which actor holds which decision and where the appeal, audit or replacement path sits. The IETF’s two announcements improve that view, but the transition now needs an operating record.

For Community Support, readers should be able to distinguish scheduling, document handling and process assistance from decisions owned by chairs, the IESG, the IAB, the NomCom or the community. For Meetings & Events, the record should distinguish venue and logistics decisions, meeting-network delivery, remote-participation services and the policies that determine access. For both teams, vendor ownership, escalation routes and service-continuity plans should remain clear even when the work feels seamless to participants.

The governance success would be a Secretariat that is easier to manage without becoming harder to inspect. The warning sign would be the opposite: a change described as clearer responsibility while operational exceptions, vendor boundaries and service failures become visible only after something breaks.

The news, then, is narrower and more important than “the IETF hired its Secretariat.” A long-standing outsourced bundle has been decomposed into people, teams and specialist services under closer LLC management. That can reduce supplier concentration and preserve institutional knowledge. It can also expand the administrative centre’s practical influence. The safeguard is the same boundary the RFCs already provide: operational authority should be explicit, auditable and replaceable, while standards authority remains where the IETF’s technical process places it.

Sources