Summary

  • The IETF Secretariat said on 25 September that revised Meeting Terms and Conditions had taken effect on 17 September. It named cancellation, promotion and enforcement as the areas clarified, but did not identify the recent issues that prompted the revision.
  • Promotion at an IETF meeting or aimed at its participants needs express prior written consent from IETF Administration LLC. The terms say this applies onsite and online, including to registrants and their affiliated organizations.
  • The same text covers promotional data collection through QR codes, links or forms, IETF-affiliation claims and possible exclusion from a meeting without a refund entitlement. It does not report that any such sanction has been imposed.

Imagine a participant leaving an IETF session and receiving a message inviting them to an outside event. The governance question is not where the sender stood. It is whether the invitation was promotional activity directed at meeting participants. The IETF’s newly announced terms put that activity behind an advance written-consent gate, even if the outreach occurs online. That is a wider operational perimeter than a rule concerned only with a booth, flyer or conversation in the meeting venue.

The Secretariat announced the update on 25 September and dated its effect to 17 September. It said unspecified issues encountered at recent meetings prompted clarification of cancellation provisions, rules for promotional activity and enforcement intended to protect meeting safety, security and integrity. Nothing in the announcement identifies a promoter, complaint or removal. Treating that explanation as evidence of a particular incident would add facts the record does not provide.

The operative terms are explicit about both the actor and the channel. Express prior written consent must come from the IETF Administration LLC, or IETF LLC. The restriction covers promotion at a meeting and promotion directed at participants; it names onsite and online activity, registered participants and affiliated organizations. A separate sentence requires the same consent before anyone suggests that a person, organization, event, product, service or technology is IETF-affiliated, sponsored, endorsed or hosted. The reach is tied to the meeting or its attendees.

It is not a published ban on all outside speech about a technology, and it should not be read as a test of whether a standards proposal is technically sound.

The terms define promotion by examples that make the data pathway important. Distributing materials and advertising products or events are unsurprising. Soliciting participants and collecting their personal data through a QR code, link, sign-up sheet or registration form for a promotional purpose bring digital capture into the same decision. Another clause tells registrants to supply personal data only through official IETF registration and other official channels; third-party registration or collection at or in connection with a meeting is not authorized without written consent.

The boundary therefore protects not just the visual environment of the meeting but also the trust a participant places in a request for details.

Enforcement gives the consent question practical force. The page encourages people to send reports of suspected unauthorized activity, including flyers or screenshots, to IETF LLC staff. It says the IETF may take steps it deems necessary, potentially denying entry or requiring someone to leave. Such action does not entitle the affected person to a refund. These are powers stated in the terms, not evidence that an exclusion has already happened.

The cancellation section separately sets a five-working-day request target and says refunds may face a 10% service charge, waived for visa denial; those conditions should not be flattened into an automatic penalty for every cancellation.

Registration also brings in policies summarized by the IETF’s Note Well, including intellectual-property and anti-harassment obligations. That cross-reference does not merge meeting administration with standards development. The LLC’s written-consent role concerns promotion and participation under these terms; technical arguments still have to be evaluated through the IETF’s own standards processes. A promotional claim of endorsement and a participant’s technical position are different objects of judgment.

The public record supports the rule and its stated rationale, but not a verdict on any particular application. The useful next document would be a narrow consent receipt: requestor, proposed audience and channel, whether attendee data will be collected, the decision owner, written scope and duration, and any later enforcement record. This is an editorial recommendation for accountability, not an IETF policy already adopted. It would let the organization protect participants while showing where event-management discretion begins and ends.

Sources