Summary

  • IETF 126 put a USD 270 super-early price on a remote week pass, while RFC 9501 and the IETF’s operating rules preserved an unlimited, trust-based zero-dollar route with the same registered interactivity.
  • Payment, waiver, registration, attendance, contribution and rough consensus are separate facts. A privacy-safe price-to-access receipt can show whether the model remains open without turning who paid into a proxy for who matters.

One meeting displayed two legitimate numbers

The registration notice for IETF 126 Vienna opened with a conventional rate table. Before 1 June 2026, a remote week pass cost USD 270, a remote one-day pass USD 150 and a remote full-time-student pass USD 60. Later tiers rose to USD 335 and USD 390 for a remote week. The onsite super-early week pass was USD 950 before Austrian VAT.

The same notice then described a second route. Anyone who wanted to participate remotely but could not afford the fee could request a waiver. The number of waivers was unlimited. The system operated on trust, with no eligibility check, and the recipient list was confidential.

It is tempting to resolve that structure with a slogan: the meeting costs USD 270, or the meeting is free. Neither statement describes the control surface. USD 270 was the list price for one class at one deadline. Zero dollars was the operative charge for another remote registration route. Both led to interactive remote participation. Neither number describes the cost of a device, connectivity, electricity, English proficiency, time-zone disruption, unpaid time or the continuing work between plenary meetings.

The distinction matters because price language travels. A rate table can be copied into a travel budget, a manager’s approval form, a scholarship request or a story about who can join. If its free parallel route disappears in transit, an optional contribution to institutional sustainability begins to look like an admission toll.

The price has an attributable authority chain

The fee was not produced by a standards working group, a show of hands in a plenary or an automatic inflation formula. RFC 8711 gives the chain a precise shape. The IETF Executive Director sets meeting fees after consultation with other IETF LLC staff and the community, with approval by the LLC Board. Fee setting and projected participant numbers form part of the annual budget process.

On 21 October 2025, the Executive Director proposed the 2026 increases. The stated method was an average increase of about 2.5% against projected attendance and US inflation of 2.75%, while limiting changes to one-day prices. The proposed super-early remote week pass moved from USD 264 to USD 270. The consultation ran to 14 November.

The Board minutes of 17 December close the next state. They say the consultation had ended, the feedback was generally supportive and the new rates had been incorporated into the 2026 budget. Resolution 92-03 approved the fees for use from IETF 126. The minutes record a unanimous live roll-call vote.

That sequence is an administrative decision with community input and Board approval. It is not technical consensus about a protocol. The distinction protects both sides. The LLC can manage a real operating budget without pretending that a price table is an RFC. The community can ask whether a BCP has been respected without pretending that a microphone queue sets the budget.

The free route is a Best Current Practice, not a promotion

RFC 9501 gives the zero-dollar path its constitutional weight. Whenever the IETF provides remote participation, there must be a free option. At minimum, working-group sessions, BoFs and the administrative plenary are expected to be remotely available. The document leaves implementation to the LLC, and identifies a waiver request as the implementation in use when it was published.

Free must also mean functionally real. The BCP says the free registration must offer the same degree of interactivity and functionality as paid remote participation. A participant’s use of the free route must not be identifiable. The option must be prominent, any extra steps must be documented, and personal information collected in connection with it must remain confidential.

The current waiver page implements that rule with unusually little adjudication. Remote waivers are unlimited. An applicant is not asked to explain the need, and no eligibility check is made. A Datatracker account is required. The page asks people who can afford the fee not to take the waiver, but trust rather than an inquiry into income, employer support or prior participation performs the allocation.

That design is not an accidental discount code. It avoids creating a second institution whose job would be to decide which people deserve to enter an open standards meeting. The price asks a participant or sponsor to support the system when able. The waiver keeps inability to pay from becoming a dossier, a ranking or a visible status inside the meeting.

Remote and onsite waivers are different objects

The zero-price principle is bounded. RFC 9501 applies to remote participation. It does not require free onsite access, where the registration fee is only one part of travel, accommodation, visa, food and absence-from-work costs.

The IETF’s operating page makes the asymmetry explicit. Onsite waivers are limited, allocated at the IETF Chair’s discretion and require an explanation. The IRTF has separate travel-grant and support arrangements. Hackathon-only registration was also available without charge at IETF 126, but it did not become a week pass for every meeting session.

These routes should not be compressed into a single paid field. An unlimited remote waiver implements an open-participation BCP. A limited onsite waiver allocates scarce support. A travel grant addresses costs beyond the badge. A free Hackathon registration admits a different event scope. A public livestream, where offered without registration, supports observation but may not carry the identity, queue and interaction of registered remote participation.

The label “free participant” conceals all of those differences. It can also disclose something the BCP protects. Public reporting should describe route classes and aggregate use without marking an individual’s badge, participant entry, chat identity or intervention as fee-waived.

At Vienna, the waiver route was not marginal

The IETF 126 plenary slides contain a dated snapshot as of 22 July 2026. They report 1,902 registrations: 1,230 onsite and 672 remote. Of the remote total, 397 waivers had been used—59%—with a displayed face value of USD 124,420.

The same slide records 26 IETF onsite-waiver requests, 14 granted and one withdrawn. It reports ten IRTF requests and ten grants, plus four travel-grant awardees. The stated value of onsite fee waivers was USD 13,780, bringing the displayed total waived amount to USD 138,200.

Those figures demonstrate operation, not representation. A route used by 397 remote registrants at the snapshot was not merely a safety clause that no one found. Yet 397 is not a constituency. It does not reveal 397 common interests, 397 people without employer support or 397 views on a draft. It says nothing by itself about session attendance, microphone use, document review or rough consensus.

The denominator also has a clock. The plenary slide says final registration numbers would be published after the meeting. The later Past Meetings page records 1,224 onsite and 555 online participants, a total of 1,779. The two records use different dates and apparently different finalization states. The 59% figure belongs to the 22 July snapshot and must remain attached to its 672-remote denominator. Recalculating it against 555 would create a result no source reported.

This is exactly why access evidence needs a receipt rather than a floating percentage. A count must carry its class, timestamp, denominator, revision state and whether it measures registrations, unique participants or observed attendance.

The budget makes payment material without making it authority

The final 2026 meeting budget forecast USD 4.55 million in meeting revenue, of which USD 2.52 million would come from registration fees. For IETF 126, it projected USD 920,125 in registration-fee revenue and USD 1.60 million in total meeting revenue against USD 1.80 million in meeting expenses. The resulting projected meeting deficit was USD 198,401.

The budget separately allocated USD 77,000 to remote participation services for Vienna. That line is not a per-user cost. It does not include every staff, platform, network or organizational dependency that makes remote work possible. Nor does the USD 124,420 face value of waivers prove that the IETF lost that much cash: a waived registration is not necessarily a paid registration that would otherwise have occurred.

The figures support a narrower conclusion. Meeting fees are important revenue, and the meeting was still budgeted to cost more than it earned. Paid registration is therefore real financial support. But financial contribution does not enlarge standards authority. RFC 8711 says sponsorships and donations must not convey special oversight or direct influence over technical work. The same institutional logic applies to a meeting pass: paying more, paying later or buying for a larger team does not buy a larger share of rough consensus.

Likewise, the waiver is not charity evidence about a person. It is the mechanism by which the institution keeps its revenue model subordinate to its open-process commitment.

A price-to-access receipt

The public record is already strong in parts: a consultation notice, a Board resolution, a rate table, a waiver page, an RFC and a budget. What it lacks is a compact join that survives when any one page is quoted elsewhere.

The first block should identify the price version: meeting, currency, VAT treatment, rate class, tier deadline, effective date and correction history. It should distinguish week, one-day, student, onsite, remote and event-limited registration.

The second should identify authority: Executive Director proposal, consultation dates, published changes, Board resolution and budget version. Community feedback is evidence used by the authorized decision chain; it is not itself the legal act that changes the rate.

The third should list access routes. For each, record the charge, application step, capacity rule, eligibility rule, confidentiality rule and event scope. An unlimited remote waiver and a discretionary onsite waiver must remain separate rows.

The fourth should publish a parity statement. It should name the registered remote functions available to both paid and waived users—session audio and video, chat, queue, attendance tooling and any other ordinary facility—and disclose material incidents or differences. It must never make waiver status visible inside those services.

The fifth should carry aggregate use with proper denominators: paid and waived registrations by class, dated interim counts, later final unique participants and any defined attendance measure. Corrections should append, not silently replace the earlier state.

The final block should connect budget to actuals. Forecast fee revenue, total meeting revenue, meeting expense, remote-services expense and waived-fee face value should stay distinct from later compatible actual figures. A variance needs a definition before it gets a narrative.

This receipt is not a new gate. It collects no income proof, application text or participant dossier. It exists so that a manager seeing USD 270, a contributor taking a waiver and a Board member reviewing the budget can all see the same institutional structure.

What the evidence does not establish

Nothing in these sources proves that the 2026 increase excluded a particular person, reduced remote participation or altered a consensus result. The records do not show why any individual used a waiver. They do not establish that every remote registrant attended, spoke or contributed. The budget is a forecast, not an audited meeting actual.

Nor does the zero-dollar route make participation costless. Hardware, connectivity, time, care work, language, confidence and scheduling remain. The IETF’s meeting fee may be the sole monetary charge imposed by the institution on this path, but it is not the sole cost borne by a person.

The defensible conclusion is both smaller and more useful. IETF 126 displayed a paid remote price and operated a parallel free interactive route at scale. The price financed access. It did not define who was entitled to participate or whose technical judgment counted.

Sources

  1. IETF Executive Director — Feedback sought on proposed increases in IETF Meeting fees
  2. IETF Administration LLC Board — Minutes of 17 December 2025
  3. IETF Executive Director — Registration open for IETF 126 Vienna
  4. RFC 8711 — Structure of the IETF Administrative Support Activity, Version 2.0
  5. RFC 9501 — Open Participation Principle regarding Remote Registration Fee
  6. IETF — Meeting Registration Fee Waivers
  7. IETF 126 Plenary — All Slides
  8. IETF — Past meetings
  9. IETF Administration LLC — Meeting Related Budget 2026
  10. RFC 3935 — A Mission Statement for the IETF