Summary

  • The IETF LLC’s public report for 1 September says the slot originally reserved for IETF 131 was given away and that previous venues in Asia are being contacted.
  • The same report says the venue originally reserved for IETF 131 is now under negotiation for IETF 134. That is a process relation, not evidence that a contract was transferred.
  • Public IETF 125 material still showed IETF 131 in Asia on 18–24 March 2028 with its venue TBA; earlier reports described site visits and negotiations, not a public selection.
  • IETF’s venue process puts LLC Board approval before final contracting and community notification after contracts are signed. The checked record proves none of those later states for the unnamed venue.
  • A meeting-state receipt should record pre-contract holds, expiry and replacement without naming a confidential candidate or turning community feedback into contracting authority.

A private planning state has entered the public record

The public Executive Director report prepared for the IETF LLC Board’s 1 September meeting gives future meetings one line each. IETF 129 Berlin and IETF 130 Vancouver are described as booked and announced. IETF 132 has a site visit planned. IETF 131 is different: because the “originally reserved slot” was given away, the organisation is speaking to previous venues in Asia.

The next line supplies an unusually useful link. IETF 134 is in negotiations with the venue originally reserved for IETF 131. The candidate has not disappeared from the planning system; it has moved into a different meeting’s possible future.

That is the full disclosed event. The report does not name the venue or city. It does not identify who gave the slot away, what was reserved, how long the hold lasted or whether money changed hands. It does not say the IETF LLC Board approved the venue, that a final contract existed, or that either party breached one. It does not cancel IETF 131.

The meeting reminder establishes that the report was a public pre-read for a Board meeting. It does not turn every sentence in the report into a Board resolution. That distinction is part of the same state discipline.

The public venue was not selected

The prior record describes motion without commitment. The IETF 125 LLC briefing listed IETF 131 for 18–24 March 2028 in Asia. The venue column said TBA.

In the IETF 125 session minutes, the Executive Director said site visits had been held in a relatively large country and negotiations were under way. The organisation hoped to announce the venue by IETF 126 Vienna if possible. A hope tied to an uncertain negotiation is a forecast, not an announcement deadline.

Two earlier records help define the sequence without explaining the loss. The 18 February report said an earlier IETF 131 site visit had been cancelled because of last-minute staff unavailability, and that backup coverage would be arranged for key site-visit roles. The 9 March report said a replacement visit was planned after IETF 125.

Those facts may be placed in chronological order. They may not be made causal. Nothing checked says the cancelled visit caused the venue to release the slot. Doing so would replace a missing explanation with a convenient story.

Seven published stages, but no word for the hold

The current IETF meeting-planning process is clearer than many procurement systems. A candidate begins with a recommendation, passes initial assessment and community feedback, then may undergo detailed assessment, site visits and cost discussion. If the published trigger applies, the IESG decides whether the city can meet the core purpose of an IETF meeting. The IETF LLC Board then approves a venue from a confidential detailed pack. Final contracts are agreed and signed. Only after the organisation is committed does it notify the community and update the upcoming-meetings page.

This sequence supports a bounded inference. A venue can be assessed, visited, negotiated and held before it is publicly announced. But the process page has no public label for a provisional inventory hold, an expiring option or a reservation that is not yet a signed venue commitment.

TBA hides all of those possibilities. It accurately says that no venue has been announced. It cannot tell a reader whether the team is still researching cities, awaiting Board approval, exchanging contract drafts or trying to extend a hold that expires tomorrow.

RFC 8718 asks the venue process to be as open as practicable so regular participants are not surprised. It also recognises that venue selection is an administrative function with mandatory criteria. RFC 8719 supplies the normal regional rotation under which IETF 131 belongs in Asia. Neither instrument gives a commenter the power to sign a hotel contract. Community feedback is evidence; LLC approval and signature are different acts.

The event is not a cancelled meeting

The distinction protects the organisation as much as the reader. If a publicly announced, signed venue had failed, the relevant record would need to address contract continuity, replacement, participant reliance and possibly cost. If an uncontracted commercial slot expired or was reallocated, the relevant event is earlier and narrower.

At the evidence cutoff, the checked public record still supports the IETF 131 meeting number, the March 2028 dates and the Asia region. It does not support a cancelled meeting, changed schedule or abandoned regional rotation. There is substantial planning time left. Returning to earlier venues may be a normal recovery route.

Nor does the report prove that a control failed. A venue may refuse to hold inventory indefinitely. The LLC may decide not to commit before assessment, feedback or Board review is complete. A competing customer may sign first. The private reservation may have contained an ordinary expiry. Each is possible. None is established.

A receipt can expose state without exposing the bid

The missing governance object is small. Give each future meeting a stable record with its number, dates and region. A confidential candidate can be represented by an opaque token until public notification. The record should name the current published process stage, the responsible IETF actor and the date the state began.

For any pre-contract hold, it should add the class of arrangement, its expiry or renewal trigger, and whether it is expressly non-binding. If the state ends, publish a reason class such as inventory released, criteria unmet, commercial terms unresolved, Board not asked, candidate withdrawn or superseded by another candidate. Protected price and negotiating detail can remain private.

The receipt should separately mark Board approval, contract signature and community notification. It should carry a replacement path and a next-update window. If a candidate venue moves from one meeting number to another, as the report says happened between IETF 131 and IETF 134 negotiations, preserve that link without calling it a transferred contract.

Finally, publish explicit non-conclusions. In this case they would read: public venue not selected; signed contract not established; IETF 131 not cancelled; published dates and region unchanged in the checked record. Those lines prevent an honest disclosure from being inflated into a scandal.

Sources