Summary

  • The current IETF Administration LLC Board page says AI note-taking and AI transcription tools may not be used during Board meetings. It keeps the open observer section, advance agendas and official minutes after approval; it does not announce an IETF-wide ban.
  • The policy has a visible prehistory. A November 2024 report said the LLC routinely disabled AI assistants embedded in business applications to protect confidential discussions and data from model training. April and June 2025 minutes then listed a Noota Assistant as an observer, and the June record assigned the Board an action to discuss AI assistants as meeting participants.
  • Removing an external recorder reduces a second path for capture, storage, reuse and disclosure. It also concentrates public evidence in minutes drafted by a human, reviewed by Directors, released by the Chair and posted by the Secretariat. Those minutes are official, but they are not a verbatim or independent transcript.
  • A defensible rule needs two receipts: one for the capture policy and one for each material decision. Scope, definitions, exceptions, custody and removal belong in the first; resolution text, votes, conflicts, alternatives, reasons, action owners, approval time and corrections belong in the second.

The observer that was also a tool

The useful fact is not that artificial intelligence attended a meeting. It is that the public record could not treat the tool as ordinary background software.

The revised minutes for 16 April 2025 list Jean F. Queralt (+ AI Noota Assistant) under Observers/Guests. The document names Michelle Cotton separately as the scribe. The 11 June minutes repeat the pairing, this time as Jean F. Queralt (+Noota Assistant). Their final action list adds A87-04: the Board would discuss AI assistants as participants in Board meetings.

Those entries prove presence and institutional notice. They do not prove what the assistant heard, whether it produced a transcript, where data went, how long anything was retained, or whether any output was accurate. There is no published breach finding in the evidence set. Turning a named observer entry into an incident report would replace one record problem with an invented story.

Presence nevertheless changes the meeting's control surface. A human observer hears through a person whose later notes remain under that person's responsibility. A meeting assistant can create a reusable account under another service's technical and contractual custody. It may separate audio, transcript, summary and account metadata into different objects. Even when every participant consents, the organization must know who owns each object, who can retrieve it and what deletion means.

The current IETF LLC Board page now supplies a clear outcome. As a matter of Board policy, AI note-taking and AI transcription tools may not be used during IETF Administration LLC Board meetings. Official minutes will be published after approval. The page lists 1 September 2026 as the next meeting, making the statement an operative boundary rather than an abstract historical concern.

A prohibition with a narrow public scope

The scope is precise and should stay precise.

The Board page describes four sections in a regular meeting: Open to Observers, Board plus Senior Staff, Board plus the Executive Director, and an Executive Session for the Board alone. It says agendas are normally published in advance and that the open section normally ends with questions from observers. The AI-tool statement appears in that Board-meeting context. It does not close the first section to people.

Nor does it govern the IETF standards process. RFC 8711 gives the LLC responsibility for operations, finance, fundraising and compliance, while saying explicitly that it has no authority over standards development. A Board rule about the corporation's meetings is therefore an administrative control. It does not become an IETF consensus position merely because the corporation supports the IETF.

The public record supplies a useful canary. In the 3 September 2025 Executive Director report, one still-open question was whether working-group chairs should use AI transcription or summarization and whether those functions should be built into IETF tools. A June 2026 AIPREF meeting record even links an AI-generated summary. Whatever one thinks of that use, it shows why the Board statement cannot be stretched into a universal prohibition.

The same restraint applies inside the policy. The public sentence does not define AI note-taking, distinguish an external bot from locally controlled speech-to-text, state an accessibility route, describe an exception, or say how a host identifies and removes a tool. It does not publish the adoption date, motion or vote. The rule is real; its public specification is still thin.

The custody problem came first

The Board did not discover data custody only after a bot appeared on an observer list.

The public Executive Director report in the 20 November 2024 minutes said that Zoom, Slack, Trello and almost every other business application had acquired some form of AI assistant. Following informal consultation with the IESG and IAB, the LLC routinely opted out or switched those functions off. Its stated purpose was to prevent confidential discussions and data from being used to train a large language model.

That report establishes a policy instinct: minimize capture before negotiating downstream promises about reuse. It does not prove that Noota trained on Board content. The link between the documents is institutional, not forensic. The LLC had already identified embedded assistants as a class of custody risk; later minutes made a meeting assistant visible; the current page excludes that class from Board meetings.

The attraction of a blanket boundary is easy to understand. Vendor terms change. A bot may enter through one observer's account even though the host has no direct contract with the provider. Notice can be technically visible without being meaningfully understood. A summary can omit a qualification, while a full transcript can preserve sensitive material that ordinary minutes would properly exclude. Searchability magnifies both convenience and exposure.

A prohibition also avoids an authority error. The most detailed account is not automatically the official account. An AI transcript could contain every spoken word and still have no power to establish a resolution, assign an action or classify a Board-only discussion for publication. Detail is evidence. Authority comes from the institution's decision process and the rules that bind it.

Lu Heng's critique of participation as mandate applies here at document scale. Attendance, contribution and evidence are not the same as authorization. A bot in an observer list does not become a director. The inverse matters too: institutional authority to approve a record does not make every omission true or every summary complete.

What survives after the bot leaves

The public substitute is not an empty promise. IETF LLC has an explicit minutes process.

The Board Minutes Approval policy says draft minutes are made available to Directors for review and comment. The ordinary review window is one week. After it closes, the Chair is asked to approve release and must assess whether consensus has been reached. The Secretariat then posts the document on the LLC website.

This chain creates identifiable custody. A scribe prepares the first record. Directors can correct it. The Chair controls release under a consensus test. The Secretariat publishes. The process is not independent observation; it is institutional authentication. That is appropriate for resolutions, action assignments and the boundary between public and protected Board business.

The Records Retention and Management Policy adds the purpose. IETF LLC seeks reliable and accessible records of its actions and decisions while also complying with privacy, legal and regulatory duties. The accompanying retention schedule treats Board minutes and materials, policies and procedures, and Board email and Slack archives as separate record classes.

That separation matters. The public minute is not the only record that may exist, and a non-public record is not necessarily being hidden improperly. Personnel, contracting, legal advice and other bounded matters can justify confidentiality. RFC 8711 itself requires transparency subject to reasonable confidentiality and says material without a specific reason for confidentiality should be public.

The governance test is consequently not publish everything. It is whether the institution can show which record class carried the decision, what was withheld, why the withholding was legitimate, and how a later reviewer can reconstruct the act without receiving protected content.

Official does not mean verbatim

An approved minute compresses. That is its function and its risk.

The document normally identifies attendees, conflicts, agenda items, reports, resolutions and actions. It may summarize a discussion in a sentence. A transcript preserves sequence and wording; a minute preserves what the institution decided to record. Neither format is automatically better for every purpose. A transcript can flood the record with noise and sensitive speech. A thin minute can remove the alternatives and reasons needed to understand a decision.

The AI prohibition shifts the balance because it eliminates one source of detailed parallel recall. A Director can still keep lawful personal notes, and the LLC may retain internal materials, but an observer cannot assume that an external service will produce a searchable account. Public accountability rests more heavily on the approved artifact and its publication speed.

This is where the current public wording is incomplete. It says what cannot capture and what will eventually be published. It does not say what the official minute must contain. It also does not say how a reader should distinguish a correction from a silent replacement, or how the Board records a tool that attempted to join and was removed.

RFC 8711 offers an outer safeguard. Any IETF participant may ask the Board for a formal review of a Board or Executive Director decision believed to conflict with IETF BCPs or LLC procedures. The request and response or result are to be made public, normally within 90 days. That route works only when the disputed act can be identified. A minute that records outcome without reasons weakens the very review mechanism meant to test it.

The minimum decision receipt

The solution is not to sneak a recorder back through an exception labelled convenience. It is to make the authorized record strong enough to bear the weight placed on it.

Each material Board decision should leave a compact receipt. It should identify the meeting, date and section; the agenda version; whether observers were admitted; the human scribe; and any capture tool admitted, denied or removed. If a section or item is non-public, the receipt should name the confidentiality category and a bounded reason without exposing the protected substance.

For the decision itself, preserve the exact resolution or action, votes or consensus method, abstentions, recusals and declared conflicts. Record the material alternatives considered and why the selected path prevailed. Name the action owner and deadline. Add the dates of draft circulation, approval and publication, plus a versioned correction history and links to any formal review.

The policy needs its own receipt. Publish when the AI-tool rule was adopted, by which authority, what AI note-taking covers, whether local processing or accessibility tools are treated differently, who enforces removal, what notice the host gives, and what happens if prohibited capture is discovered after a meeting. State which artifacts become LLC records and which must be deleted.

These fields do not require a public audio archive. They create a chain from meeting access to official consequence. The bot can remain outside, confidential material can remain protected, and the public can still determine what the Board did, who was authorized to do it and how the record changed.

Sources