Summary

  • On 16 September, the IAB said one candidate had accepted nomination for the 2027–2029 IRTF Chair term: incumbent Dirk Kutscher. This is a count of accepted public candidacies, not a count of nominations received.
  • Feedback is due to two IAB addresses by 23:59 UTC on 7 October. A sender may request anonymization, but the notice does not define who first sees identity, when it is removed or what metadata remains.
  • The public record contains two timetable versions: the July call anticipated community input by 5 October and an announcement on 21 October; the later notice uses 7 October and selection by the end of October.
  • A privacy-safe appointment receipt could publish process states, applicable criteria, identity-access boundaries, decision authority and term dates without exposing feedback, candidate files or individual deliberation.

One visible name answers only one question

The IAB feedback notice uses exact but easily overextended language: “one candidate has accepted a nomination.” It names Dirk Kutscher and identifies him as the incumbent. The IETF announcement archive preserves the same notice.

That wording establishes one accepted candidacy and one public candidate. It does not disclose how many nomination messages arrived, how many distinct people were nominated, whether a person declined, whether multiple people nominated the same individual or whether any submission was withdrawn. The earlier call for nominations explains that candidate names would be published together after nominations closed, while information other than names would remain confidential to the IAB. A one-name publication is therefore the visible end of a confidentiality-preserving process, not a complete event log.

Nor is it an uncontested election. The community is not being asked to cast ballots between candidates. It is invited to send relevant feedback to the appointment authority. The number of public names cannot tell a reader how the IAB will assess the candidate, what feedback it will receive or what decision it will make.

This distinction matters most when an incumbent is the sole accepted public candidate. Familiarity can make several states collapse into one story: nominated, willing, consulted upon, selected and appointed. They remain separate. “Accepted” describes the candidate’s consent to enter the process. “Appointed” would describe a later exercise of IAB authority.

An anonymization request is not anonymous intake

The notice asks for comments to be sent to both IAB mailboxes listed in the announcement by 23:59 UTC on Wednesday, 7 October. It adds that a sender who wants feedback anonymized should say so in the response. This offers a valuable protection, especially in a small professional community where critical comments can affect working relationships.

But anonymization is a transformation, not a description of the intake channel. The notice does not say which mailbox recipients initially see the sender address, whether the IAB receives a redacted version or the original, when names are removed, how quotations are handled or which metadata is retained. It would be wrong to promise that the feedback is anonymous to the recipients or invisible to IAB members.

The public-interest gap is not a reason to expose correspondence. Personnel comments may include sensitive judgments, references to private interactions or information that cannot safely be separated from the speaker. A useful disclosure would instead define the identity-access boundary: initial recipients, the stage at which redaction occurs, who receives the redacted or original material, the treatment of quotations and the retention category. That describes the protection without publishing the protected material.

The same discipline applies to any later summary. A count of messages would not reveal the direction or weight of the feedback. Silence would not prove support. Multiple messages would not establish distinct senders. No public source identifies the volume, substance or composition of feedback, and this article does not infer any of them.

Two public calendars should remain visible

The July nomination call and the September feedback notice describe the same appointment cycle, but not with identical milestone dates. The call closed nominations on 8 September, sought community input by 5 October and anticipated announcing the selection on 21 October. It described a term beginning on 8 March 2027 and ending at IETF 134 in March 2029.

The later notice asks for feedback by 7 October and says the IAB expects to finalize its selection by the end of October. It states that the term begins at IETF 128 in March 2027. The later notice may function as an operational update, but it does not expressly say that it supersedes the earlier dates or explain why they changed.

This is not evidence that a deadline was missed or that the procedure failed. At the current freeze point, both public versions describe future milestones. The governance value lies in keeping their version history instead of silently merging them into a single reconstructed calendar. A dated correction or change note would tell later readers which schedule governed submissions and when.

The distinction is practical. A person relying on the July page could believe 5 October is the final day for input, while a person relying on the September notice sees 7 October. Preserving both dates with a clear effective version is a small act of procedural fairness.

Renewable terms still require a fresh decision

RFC 2850 assigns the IAB authority to appoint and remove the IRTF Chair. It describes a two-year term that is renewable. The IAB’s appointments page lists Dirk Kutscher for 2025–2027 and says a nomination call is issued for every new term, whether or not the incumbent is willing to continue.

The feedback notice says there is no limit on length of service. Read together, these statements draw a precise boundary. There is no cumulative cap on how many terms a person may serve, but each term remains bounded and each new term requires another appointment process. “No service limit” is not an indefinite appointment. Renewability is not automatic renewal.

The office justifies this care. RFC 2014 places management of the IRTF with the Chair in consultation with the Internet Research Steering Group. RFC 7827 describes an operating surface that includes Research Group chartering and closure, appointment and management of chairs and the IRSG, publication work, reporting, IAB participation and grievance handling. Administration may be delegated; responsibility remains with the Chair.

None of these duties demonstrates whether the incumbent has performed well or poorly. The Datatracker profile identifies the person and current roles; it is not a performance review. The appointment process should not be turned into one by implication.

Decision authority can be legible without exposing deliberation

RFC 2850 says the IAB tries to decide unanimously. If unanimity cannot be reached, its general fallback requires at least seven full members to concur and no more than two to dissent. It also permits personnel discussions to remain confidential and, with the consent of full members, allows liaison and ex-officio members to be excluded.

Those are governing rules, not case facts. The sources do not show which decision rule will be used here, who will participate, whether anyone will recuse or be excluded, or how any member will vote. The IRTF Chair is an ex-officio IAB member, so it is legitimate to ask the eventual record to identify the eligible decision body and any recusal or exclusion category. It is not legitimate to allege a conflict or a failed recusal without evidence.

This is where institutional legitimacy depends on accurate compression. A public appointment notice cannot reproduce private assessments, and should not. But “the IAB decided” compresses several facts that can safely be retained: which rule applied, when authority was exercised, whether the result was unanimous or used the fallback, whether a dissenting or minority view existed and whether it was published, summarized or lawfully withheld.

The IAB appointments wiki shows that appointment work is an established governance function, not an improvised announcement. A stable receipt format would make recurring processes easier to compare without making confidential cases public.

A single-candidate appointment receipt

The minimum useful artifact is a privacy-safe receipt, not a dossier. Its first line would preserve vocabulary: nominations received, distinct nominees, accepted candidacies and public candidates are different fields. A value that cannot be published should be marked non-public, not reverse-engineered from the one visible name.

The receipt would then record the versioned feedback window and addresses; the anonymization request and identity-access boundary; the qualification sources and high-level criteria; the eligible decision body and applicable rule; the decision date and outcome; the two-year term dates, renewability and absence of a cumulative service cap; and the handoff, later performance channel and correction history.

Limited reason categories could say whether the decision rested on continuity, research leadership, operational management, community trust or another published criterion without releasing scoring sheets or attributing comments. A recusal field could report “none”, a category of exclusion or “not disclosed under the personnel rule” without naming a private interest. The purpose is not maximal disclosure. It is to prevent different stages from being mistaken for each other.

This proposal is not an existing IAB requirement. It applies the Policy Mirror idea that a public institution should show which observable fact supports which claim, and the minimum-initial-specification principle that a small, versioned interface can preserve later choices without trying to settle every detail now.

What is known before the decision

As of this article’s evidence freeze, the public record supports a modest statement. Dirk Kutscher is the one publicly identified person who accepted nomination. The IAB has invited feedback and expects a decision by the end of October. The term is scheduled to begin in March 2027. No source reviewed here announces a result for this appointment cycle.

The record does not establish the number of nominations, the content or direction of feedback, the mechanics of anonymization, a case-specific scoring rubric, participation or recusal, a vote count, a selection rationale or a final decision. It does not show an automatic renewal, an election or an indefinite term.

Keeping those unknowns visible is not withholding analysis. It is the analysis. Before an institution creates authority in a named office, the public should be able to see where nomination ends, where confidential evaluation begins and which later act makes the appointment real.

Sources

  1. IAB — Feedback on IRTF Appointment
  2. IETF announcement archive — Feedback on IRTF Appointment
  3. IAB — Call for Nominations: IRTF Chair
  4. IAB — Appointments & Confirmations
  5. RFC 2850 — Charter of the Internet Architecture Board
  6. RFC 2014 — IRTF Guidelines and Procedures
  7. RFC 7827 — The Role of the IRTF Chair
  8. IAB Wiki — IAB Appointments
  9. IETF Datatracker — Dirk Kutscher
  10. Heng Lu — The Policy Mirror
  11. Heng Lu — Minimum Initial Specification, Localized Future Decision, Voluntary Adoption