Summary

  • IETF's 29 June and 8 July calls describe a six-week 2026 process but both end their milestone lists with 2027-07-27 - Confirmed candidate seated.
  • The 4 August result says Pete Resnick will serve the remainder through March 2027 and a following three-year term, taking effect as soon as possible; the current Board page lists him with a 2030 term end.
  • This is evidence of an unjoined public correction, not evidence that the appointment waited a year, was invalid or breached RFC 8713.

One line changes the year

The first public call is unusually specific. The IETF Nominating Committee, or NomCom, opened nominations on 29 June 2026 after Shauna Turner left the IETF Administration LLC Board. It named the IESG as the confirming body, identified the mid-term-vacancy rule and set out the intended sequence date by date.

Nominations would close on 13 July. The slate and request for community feedback would follow on 14 July. Interviews and deliberations would begin on 15 July, feedback would end on 21 July, and the selection would be sent for confirmation on 22 July. Confirmation, notification and announcement were placed between 23 and 27 July 2026.

Then the year changes. The final line reads 2027-07-27 - Confirmed candidate seated.

That line does not sit comfortably with the notice around it. The same notice calls the schedule “rather tight,” describes only six weeks from the vacancy announcement, and says the confirming body may reject within two weeks or the candidate is assumed confirmed. It says that confirmation window could run to 6 August 2026. A July 2027 seating date would therefore place almost a year between the stated confirmation mechanics and service, without explaining why.

This is not merely a difference between an archived email and a later retelling. The NomCom's second call, published on 8 July, reproduces the same sequence and the same 27 July 2027 line. Two official notices preserve it.

The vacancy was real and bounded

The Board announced on 12 June that Turner had resigned effective 9 June. It appointed Roman Danyliw as Treasurer and said it would notify the NomCom so the vacancy could be filled under RFC 8713. The Board would continue to meet its obligations. Where possible, it might defer decisions until the new member was selected and seated.

That last sentence matters, but only within its limits. It shows why a correct service state was operationally relevant: the Board itself distinguished continuing responsibility from the possible deferral of some decisions. It does not identify which decisions, if any, were deferred. It does not establish that the Board lacked quorum or that its actions were impaired. It should not be turned into a claim of institutional paralysis.

Turner's earlier selection also fixes the term context. A December 2023 NomCom announcement said she would join the Board in March 2024. By June 2026, less than one year remained in the ordinary term. That is why both 2026 calls invoked the branch that combines the remainder of the open term with the next standard three-year term.

RFC 8713 supplies the process logic

The published rule is clearer than the stray year. Section 3.5 of RFC 8713 assigns a vacancy occurring during the overlap of two NomComs to the prior year's committee. If that committee reconvenes, selection and confirmation are due within six weeks. The confirming body has two weeks to reject the candidate; without rejection, the candidate is deemed confirmed.

Term treatment depends on the time remaining. If at least one year remains, the successor serves the remainder. If less than one year remains, an IETF LLC Director receives the remainder plus the following three-year term. RFC 8713 defines that year by the interval between first IETF meetings, not simply by a calendar label.

The term-start rule is also direct. An ordinary confirmed LLC Director begins at the next appropriate Board meeting or as Board policy dictates. A candidate confirmed under the mid-term rule begins as soon as possible after confirmation.

RFC 8711 provides the institutional edge. The ordinary director term is three years, with an exception for vacancy appointments. The body that originally selected a departing director is responsible for the replacement; a NomCom-selected seat therefore returns to the NomCom under RFC 8713. The Board provides administrative strategy and oversight. Filling its seat does not confer IETF standards authority on the director and does not create technical consensus.

The later record points to 2030

The public process continued on the 2026 schedule. The 14 July notice opened feedback on the nominees until 21 July. It explained that named submissions would be visible to NomCom members and that a person seeking anonymity could use a trusted intermediary, with the feedback treated confidentially. A 20 July reminder kept the same deadline and said deliberations were scheduled for 22 July.

On 4 August, the NomCom announced that Pete Resnick had been selected. Its term description is precise: the remainder of the current term through March 2027, followed by a three-year term. It says the appointment will take effect as soon as possible under RFC 8713.

The current IETF Administration LLC Board page now lists five directors. Resnick appears as a NomCom appointee with a term ending in 2030. The page lists the 12 August meeting as canceled and the next meeting for 1 September, but those entries do not establish the day on which service legally or operationally began. No source in this package supplies that exact timestamp, so this article does not invent one.

The later materials make a one-year delay an implausible reading of the old line. They do not make the old notices self-correcting. A reader landing on either call still encounters 2027 as the declared seating date, with no correction note and no link beside that line explaining which later record controls.

A current page is not a correction trail

Institutions often maintain two kinds of public evidence. An announcement archive shows what was said at a moment. A roster shows the current state. Both are useful, but neither alone explains a change between them.

The archive should not be silently rewritten. Preserving the original notice protects the historical record. But preservation is different from leaving an error unqualified. A correction note can retain the original bytes, name the mistaken or superseded field, point to the authoritative later state and record when that relationship was added.

The roster has the opposite limitation. It tells a reader who is currently on the Board and when the listed term ends. It does not show the vacancy, the two calls, the confirmation state, the remainder-of-term boundary or the reason the visible public date changed. Current truth without lineage is difficult to audit; archival truth without a correction is easy to misread.

Daniel Kade's succession receipt

The smallest adequate remedy is not a larger biography or disclosure of confidential NomCom deliberations. It is a public succession receipt.

For this case, the receipt would bind the vacancy and effective resignation date; the seat's selecting and confirming bodies; the RFC branch that assigned the process; the published milestone and its source; a correction or supersession event; confirmation state; effective service date if that date is public; the March 2027 remainder boundary; the following three-year boundary; and the source that now controls the current state.

That structure keeps three things separate.

First, selection is not confirmation. The NomCom chooses; the IESG is the confirming body under the cited process. Second, confirmation is not necessarily a published exact service timestamp, even when the rule requires service as soon as possible. Third, a term-end year on a roster is a current state, not a complete history of how the seat arrived there.

The receipt would not publish nominee assessments, confidential feedback, unsuccessful candidates or personnel material. It would expose only the public authority chain and state transitions already necessary to understand the appointment.

This is Daniel Kade's proposed record design, not an announced IETF requirement. Its purpose is modest: make it possible for a reader to tell that a later source corrected the practical implication of an earlier line without deleting the line or manufacturing an exact date.

What should not be inferred

There is no evidence here that IETF intended to leave the seat empty until July 2027. There is no evidence that Resnick's selection was invalid, that the IESG failed its confirming role or that RFC 8713 was breached. The sources do not show bad faith or concealment. They do not identify an invalid Board decision.

Nor does the mismatch justify treating the roster as a legal instrument that cures every earlier record. The safe conclusion is narrower. Two official calls contain a date that conflicts with their own six-week frame and with the later public state. The outcome is visible; the correction link is not.

Sources

  1. https://mailarchive.ietf.org/arch/browse/static/ietf-announce/2026-08/
  2. https://mailarchive.ietf.org/arch/msg/ietf-announce/VMoqSwjeKiCLagLTZw3cF_AUva0/
  3. https://mailarchive.ietf.org/arch/msg/ietf-announce/IvpwLXlqltU62wEsD8bRI7FSVA8/
  4. https://datatracker.ietf.org/nomcom/ann/2691914/
  5. https://mailarchive.ietf.org/arch/msg/ietf-announce/-UhogKxvWA2xIUiT-ZFDnJsSSGE/
  6. https://datatracker.ietf.org/nomcom/ann/2723220/
  7. https://mailarchive.ietf.org/arch/msg/ietf-announce/qXNftRFCQzuU9TL26U_44niOXBk/
  8. https://www.ietf.org/administration/llc-board/
  9. https://datatracker.ietf.org/doc/html/rfc8713
  10. https://datatracker.ietf.org/doc/rfc8711/
  11. https://datatracker.ietf.org/nomcom/ann/903565/