Summary

  • The IETF’s 27 August review links constrained hallway seating in Vienna to onsite attendance above the level anticipated when the venue was chosen.
  • Overall satisfaction remained high. The space score identifies a weakness, not a finding of unsafe occupancy or a contractual breach.
  • Current venue criteria require informal discussion and personal online-working space inside the facility. The governance question is when evolving attendance expectations are tested against usable space.

The extra chairs could not solve it

The usual response to a shortage of hallway seating is to bring in more chairs. At IETF 126 in Vienna, that response ran into a different limit: the space in which to put them. The post-meeting account published on 27 August says onsite participation was higher than anticipated when the venue was selected, leaving insufficient room for the supplemental seating normally provided.

That is a useful admission, and a narrow one. It joins an earlier planning assumption to a later operational constraint. It does not disclose the forecast, when the venue was chosen, or whether expectations were revised in between.

The meeting was not generally unpopular. Respondents gave it 4.34 out of five overall, and 94% were satisfied or very satisfied. Hallway seating and breakout space scored 3.32. Comments described crowding and difficulty finding workspace. A favourable overall result and an awkward place to open a laptop can coexist.

The official proceedings record 1,223 onsite participants and 556 online participants at the 18–24 July meeting. The latter did not occupy Vienna’s corridors. Neither the combined registration total nor a satisfaction score supplies a measurement of usable floor area.

The current rule is about space inside

This is more than a question of conference amenities. RFC 8718 makes an appropriate layout with enough space for expected participants, leadership and support staff a mandatory selection criterion. It also distinguishes important criteria from mandatory ones. Informal discussion and individual working space belong to the former group; a poor survey score cannot simply be relabelled a failed mandatory test.

The wording has changed since that RFC appeared. RFC 9712, published in January 2025, replaces the older formulation that included nearby external venues. Its updated criteria call for sufficient, easily accessible places for spontaneous discussion within the facility, and sufficient places there for people to work online on their own devices.

The update explains why. Earlier survey feedback favoured immediately accessible hallway seating over lightly used dedicated rooms or places several minutes away. It describes the practice of adding furniture when the venue’s own provision is inadequate. Vienna’s account therefore concerns the physical limit of a response already recognised in the policy discussion.

These are the current requirements, not proof about the rules attached to an unidentified historical booking decision. The reviewed sources do not establish Vienna’s selection date, contract terms or assessment history. They support a question about planning, not a retrospective verdict.

Forecasts have a useful life

The current venue-selection process runs through assessment, community input and detailed work that can take years. Costs, site visits and suitability feed a confidential decision pack for the IETF LLC Board before contracting. There are sound reasons to choose well ahead of registration.

But an expected headcount is an input, not a permanent property of a building. As registrations develop, the relevant comparison is with the space people can actually use: where small groups can pause, where laptops can be opened and how those places fit the meeting’s layout. Furniture inventory alone cannot answer that question.

This is Daniel Kade’s analytical inference, not a disclosed finding that staff failed to review demand. A later forecast might confirm the original choice, prompt a different arrangement or reveal that further flexibility is costly or unavailable. The public account does not say which reviews occurred.

Lu Heng’s Note 36 asks BTW to examine assumptions under pressure without inventing villains or campaigning for a preferred remedy. Here, the pressure is concrete. The practical value of a capacity assumption depends partly on when there is still time to act on its revision.

Nor does success mean maximising attendance. RFC 8718 expressly rejects that as an objective in itself. The purpose is productive work. Vienna’s positive result should remain in view while the weaker space result informs the next decision.

Sources and limits

This report uses the IETF’s published survey account and proceedings, RFCs 8718 and 9712, the current planning guide and Lu Heng’s attributed editorial note. It does not use respondent-level survey data, a measured floor plan, internal forecasts or private contracts. No safety violation, displaced standards outcome or failure to reconsider demand is established.