Andrew, Thank you for writing this down. It helps us all understand the work you do for us, and it clarifies the process. I particularly like the care you are applying to preventing familiarity bias. A few thoughts... --- 2.2 has The Internet Society President is strongly advised to require prior experience in a NomCom: experience indicates that there can be challenges for Chairs who have never participated in a NomCom in any capacity. I wonder why 8713 did not set this requirement. I do think that this is very useful experience for a NomCom chair, but I am not sure it is a requisite. There are many experienced IETFers who can read the RFCs, listen to the experience and advice of past chairs, and could do a passable job. (Let me suggest, without sucking-up, that it wouldn't be beyond your own capabilities.) So, maybe something for you to consider as an asset, but not a reason to discourage candidates from being suggested to you. --- 2.2 has The Call for Candidates is to be posted at least to the IETF general mailing list and the announcement list. Self-nomination will be encouraged. This is great, but it doesn't say that nomination of others is also encouraged (or discouraged). I hope it is your intention to allow one person to suggest the name of another person. --- I wonder whether a little more job description would go some way to encouraging (self-)nominations. I think you probably have experience of the type of questions that most people ask when you first approach them (for example, how many hours, what period of the year, requirement to be able to coordinate feline displacement...). If you were able to capture some of this, at a very high level, it might help scope the role and encourage nominations (while also reducing the nominations of people who would later decline when they found out the truth). Best and good luck, Adrian -----Original Message----- From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of Andrew Sullivan Sent: 14 February 2022 05:54 To: ietf@xxxxxxxx Subject: draft-sullivan-nomcom-chair-select-00 Dear colleagues, I write with my job hat on. I'm employed by the Internet Society. Part of my job here is to select the NomCom Chair. I've been uncomfortable about how that has worked in the past, and more than a year ago I said I'd write a new process. I failed at that goal, but it's a new year so I've finally written this. It's at https://datatracker.ietf.org/doc/draft-sullivan-nomcom-chair-select/. I am eagerly requesting feedback on that draft _for things under my control_. The procedures in RFC 8713 give me a lot of latitude in how to deal with this appointment. They give me no control whatsoever as to whether I _should_ be able to do this, who else should do it, and so on. Feedback of the form "Here's how NomCom should work for real," will be ignored, because they will not provide me guidance as to what I should do. Please also resist the temptation to tell me, "Tell someone else it's their thing and promise to follow what they promise." If the IETF wants to modify RFC 8713, including removing my own role in this selection, I don't imagine a universe in which I'd work to work to foil that. But similarly I am not willing to create an entirely new consultative body (or new job for an existing consultative body) without the community saying so. This document is merely an outline of how I plan to execute my duties as they're already defined. I hope this will be a modest contribution to the IETF, and I look forward to your suggestions. _Please_ send me feedback directly and not copied to the list. I won't be able to follow discussion about this on the list except sporadically, and I'm going to have to put this plan into action some time in the coming weeks. Thanks very much. Best regards, A -- Andrew Sullivan President & CEO, Internet Society sullivan@xxxxxxxx +1 416 731 1261
