Re: Comments on Composition and Comportment of the IETF Nominating Committee draft
Joel Halpern <jmh@joelhalpern.com> Tue, 07 July 2026 02:42 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F18E411187894 for <ietf@mail2.ietf.org>; Mon, 6 Jul 2026 19:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783392154; bh=bSIUS9bmMYTIQBUWaLLz6C9O3rHcg3VpYIuwA1P7bKc=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=eqNUC5tEX8ZzBxm2fVk3wgJQOuj6XmaqQNIF/ZW29DN8TtnVLMiPFPDqFfvr2vK/6 kV3ykcMYcNJiNcKDy+Lx0yTO+YFPQKj2EmlCeOSIJ/pcopw25sM4cEAuBrhGCsZUSZ VsoRuSqu7dolPVWIN2wtnlZI60t26hrxYMnnbxlY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUqQLhQ7mzaU for <ietf@mail2.ietf.org>; Mon, 6 Jul 2026 19:42:33 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B4C191118788A for <ietf@ietf.org>; Mon, 6 Jul 2026 19:42:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1783392153; bh=mWfE5SRvnPFCTFBfTUHeXTEUm8y0ZUhXJ8asOja+d0c=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=kLLuyCB/1GLD2OjUVvooO7HNBMWNp/MUgZTdI0V7fE07xDgZsM5tkhbBIJPepHLNO rY9PpN2ie5qgaadTPc5vEGPV8b6oODJEZVkcwCI5oZRmXC6c9nWvHh5vIKB3vkajRc 9DA8bi/km36PV4fx6AUtEWKjq1ziUaTikezp13CA=
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4gvQVx14Gvz1s2JR; Mon, 6 Jul 2026 19:42:33 -0700 (PDT)
X-Quarantine-ID: <gH49uZJ1IEe7>
X-Virus-Scanned: Debian amavis at b2.tigertech.net
Received: from [192.168.0.109] (ip68-100-242-223.dc.dc.cox.net [68.100.242.223]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4gvQVv4ZS1z1nsPH; Mon, 6 Jul 2026 19:42:31 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------gdPM3SYXub9YC6zG4hmjA4JE"
Message-ID: <d5b7fcf2-7c4b-4c93-bf8b-eb8e165345ee@joelhalpern.com>
Date: Mon, 06 Jul 2026 22:42:28 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Comments on Composition and Comportment of the IETF Nominating Committee draft
To: Mallory Knodel <mallory.knodel@nyu.edu>
References: <6.2.5.6.2.20260706031812.0b0262a8@elandnews.com> <CABMXHrEDcG8779iaPryrff30O6fxP6E41WMMaNdtqM9b5ZpGeg@mail.gmail.com> <6.2.5.6.2.20260706082341.1113f008@elandnews.com> <CABMXHrGRLUG_VN7ovz4x=GmeM6gXbuqMPb55iWe3yeHGfiHuRg@mail.gmail.com> <fc25bfb9-d5ca-404c-8975-470b3d8f569a@joelhalpern.com> <CABMXHrGvB3kmZ_u1_pdYUfre7Vv_PUAd2S4wXROf43ur9Sk8yA@mail.gmail.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CABMXHrGvB3kmZ_u1_pdYUfre7Vv_PUAd2S4wXROf43ur9Sk8yA@mail.gmail.com>
Message-ID-Hash: AXORETT2QNGBXODJ4KQBIMUBPTTIFAIS
X-Message-ID-Hash: AXORETT2QNGBXODJ4KQBIMUBPTTIFAIS
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mk6w_zoSo0OU6GoRZ2PBjTFFQ1A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
I think without violating the confidentiality requirements, I can make a couple of observations. Other past nomcom members / chairs / liaisons can provide comments as they feel appropriate. First, one of the difficulties is that the nomcom must treat the feedback as confidential. Great care is taken to not violate that. Nonetheless, committees do learn about issues with specific candidates from the feedback, and it is important to identify those issues. Whether they decide to ask the candidate about aspects of that ought, as far as I can tell, be left to the discretion of the committee. In my experience committee members are generally good at separating substantive feedback issues from feedback driven by attributes that shouldn't matter. There are many dimensions besides the ones you are focusing on that the committee needs to watch for and avoid. I don't think trying to prevent bias in the feedback is desirable or achievable. It is also worth noting that we are interviewing people for many different jobs. At the very least, even the structured part of the interview is likely to be different for the different positions. This then gets even more complicated when the committee may be evaluating person A based on strength X and weakness Y, and person B on strength Q and weakness R. The interview may well want to explore those specific qualities for that specific candidate. Even when we know the job, we know that people will do the job differently. And the selection process is even more complicated by the fact that the job itself changes over time. In fact, one of the tasks the nomcom undertakes is deciding what properties they think are important for which positions. I suspect that further analysis would reveal even more nuances in the interview and evaluation process. Yes, it is important to be clear that we avoid bias in our selection. I don't think tying the hands of the committee in terms of what they ask candidates is helpful. In some sense, the structured part of the interview presumably starts with the common questionnaire. I am not asking or suggesting that the questionnaire be tuned to the individual candidate. But that is only the starting point. Yours, Joel On 7/6/2026 10:25 PM, Mallory Knodel wrote: > Hi Joel, > > I think specific candidate questions, if not related follow ups to the > structured interview questions, can invite discrimination. > > OTOH, the US OPM goes to the other logical end: Employers should use > structured interviews in which all candidates are asked the same core, > job-related questions and are evaluated using the same criteria. Any > follow-up questions should be limited to clarifying a candidate’s > responses and should be used consistently to maintain fairness and > comparability across candidates. > > Probably there’s a middle ground. > > It would be worth interrogating the role of community feedback. > Obviously this is a unique element and guidance for most hiring > processes won’t have much to say about it. If we worry about > discrimination in nomcom decision making we should probably worry > about it in candidate feedback too. So what would be the fair > mitigation? Giving a candidate the chance to rebut a potentially > discriminatory feedback comment? Or not mentioning the comment during > the interview at all, and giving the nomcom discretion to > consider feedback in its own right to supplement its decision? > > Sorry I pointed the question back. But I’m genuinely not sure beyond > my own experiences and intuition, which I’ll keep to myself as an > author of this draft, which can hopefully encompass community > consensus on the topic. > > -Mallory > > On Tue, Jul 7, 2026 at 11:11 Joel Halpern <jmh@joelhalpern.com> wrote: > > With regard to the structured interview item in your draft, I was > unclear whether your documents intends to say that each interview > should include the structured questions or were you aiming to say > that the interviews MUST ONLY consist of the structured questions. > > As far as I know, the former is common practice, and a good idea. > The latter would unduly constrain the committee from asking about > things they think are important to the specific candidate, for > example based on the feedback they have received. > > Yours, > > Joel > > On 7/6/2026 10:03 PM, Mallory Knodel wrote: >> Hi, >> >> On Tue, Jul 7, 2026 at 01:11 S Moonesamy <sm+ietf@elandsys.com >> <mailto:sm%2Bietf@elandsys.com>> wrote: >> >> Hi Mallory, >> At 05:13 AM 06-07-2026, Mallory Knodel wrote: >> >> >> >I'm not sure I remember. Could you elaborate this comment >> please? >> >> It's in RFC 7704 (Page 4). >> >> >> Incredible. Thanks a lot for sharing this. I’ll cite it in the >> next version. >> >> >> >Disclosure of interest to the chair, who then decides if >> there's a >> >conflict. Simple recusal. >> >> It could be a bit more complicated than that. >> >> >> Certainly but I don’t know if the document can or should try to >> encompass the complexity or simply describe a process for >> addressing it. >> >> I am open to text suggestions that better elaborate this and any >> of the comportment sections. >> >> >> >It's here. I've edited the main copy. >> ><https://urldefense.proofpoint.com/v2/url?u=https-3A__hbr.org_2016_04_how-2Dto-2Dtake-2Dthe-2Dbias-2Dout-2Dof-2Dinterviews&d=DwIBAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=YIrtQwrRtb_e31ldkUQjV6tcWTEcpf5fCSgJN5EFLRkjqZ3pHWlqlpLKxKQuPKb-&s=MBhR2Q0q-JMD3j71Sm58-ZD61u61e_r2AQAlRgDPkEI&e= >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__hbr.org_2016_04_how-2Dto-2Dtake-2Dthe-2Dbias-2Dout-2Dof-2Dinterviews&d=DwIBAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=YIrtQwrRtb_e31ldkUQjV6tcWTEcpf5fCSgJN5EFLRkjqZ3pHWlqlpLKxKQuPKb-&s=MBhR2Q0q-JMD3j71Sm58-ZD61u61e_r2AQAlRgDPkEI&e=> >> >https://urldefense.proofpoint.com/v2/url?u=https-3A__hbr.org_2016_04_how-2Dto-2Dtake-2Dthe-2Dbias-2Dout-2Dof-2Dinterviews&d=DwIBAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=YIrtQwrRtb_e31ldkUQjV6tcWTEcpf5fCSgJN5EFLRkjqZ3pHWlqlpLKxKQuPKb-&s=MBhR2Q0q-JMD3j71Sm58-ZD61u61e_r2AQAlRgDPkEI&e= >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__hbr.org_2016_04_how-2Dto-2Dtake-2Dthe-2Dbias-2Dout-2Dof-2Dinterviews&d=DwIBAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=YIrtQwrRtb_e31ldkUQjV6tcWTEcpf5fCSgJN5EFLRkjqZ3pHWlqlpLKxKQuPKb-&s=MBhR2Q0q-JMD3j71Sm58-ZD61u61e_r2AQAlRgDPkEI&e=> >> >> >> Thanks. The answers to the questions would not be relevant >> in my opinion. >> >> >> Fair. My thinking was to provide some authoritative example of >> how industry thinks about this. I’m open to citing a better and >> more relevant publication. >> >> Thanks, >> -Mallory >
- Comments on Composition and Comportment of the IE… S Moonesamy
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… S Moonesamy
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Joel Halpern
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Joel Halpern
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Joel Halpern
- Re: Comments on Composition and Comportment of th… Vittorio Bertola
- Re: Comments on Composition and Comportment of th… S Moonesamy
- Re: Comments on Composition and Comportment of th… Brian E Carpenter
- Re: Comments on Composition and Comportment of th… S Moonesamy
- Re: Comments on Composition and Comportment of th… George Michaelson
- Re: Comments on Composition and Comportment of th… Vittorio Bertola
- Re: Comments on Composition and Comportment of th… S Moonesamy
- Re: Comments on Composition and Comportment of th… George Michaelson
- Re: Comments on Composition and Comportment of th… Brian E Carpenter
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Russ Housley
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Russ Housley
- Re: Comments on Composition and Comportment of th… Mallory Knodel
- Re: Comments on Composition and Comportment of th… Salz, Rich
- Re: Comments on Composition and Comportment of th… John Levine
- Re: Comments on Composition and Comportment of th… Brian E Carpenter
- Re: Comments on Composition and Comportment of th… George Michaelson
- Re: Comments on Composition and Comportment of th… S Moonesamy