RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (2)

RFC 8713, "IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees", February 2020

Source of RFC: iasa2 (gen)

Errata ID: 7092
Status: Reported
Type: Technical
Publication Format(s) : HTML

Reported By: Rich Salz
Date Reported: 2022-08-16

Section 4.17 says:

If the Chair is unable to contact a voting volunteer, the Chair must
repeat the random selection process in order to replace the unavailable
volunteer.  There should be at least one day between the announcement of
the iteration and the selection process.

It should say:



Historically, it appears that NomCom chairs treat "can't contact" as "ineligible" and just move down the list. This also appears to be IETF consensus.

Was the intent to really announce seed source, wait, pick them, re-run the process? If so, how long to wait for objections? This needs much more clarification. For example, a timeline of how long to take if following RFC 3797.

Errata ID: 7174
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Rich Salz
Date Reported: 2022-10-20

Section 3.7.3 says:

The sitting IAB members review the IESG candidates.

It should say:

The sitting IAB members review the IESG candidates
(including IETF Chair).


Sometimes IETF Chair is mentioned and sometimes Gen AD is mentioned;
the clarification avoids confusion.

Report New Errata

Advanced Search