Re: Diversity of candidates was Re: NomCom 2020 Announcement of Selections

Keith Moore <> Mon, 25 January 2021 23:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A6AB73A19EA for <>; Mon, 25 Jan 2021 15:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.018
X-Spam-Status: No, score=-0.018 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7EUjNaxSze58 for <>; Mon, 25 Jan 2021 15:11:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 64E633A19E8 for <>; Mon, 25 Jan 2021 15:11:32 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id C182C5C0161 for <>; Mon, 25 Jan 2021 18:11:31 -0500 (EST)
Received: from mailfrontend1 ([]) by compute3.internal (MEProxy); Mon, 25 Jan 2021 18:11:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=asavp6ssjP6tjhk1udr0WBMMw54DM6IsoSET8ET7E j4=; b=UzDV2ZcZ8xJcH8EeXet6CvRjwlBCNUlXTzSA7j/w4Dd/P93LKPs7T9QSB Wm6tOBoj2lEp+MzWOrp/pLfrFCI3/Et8D4KaspNCJTuoXKfa9Rgu5xl6qWBCSU59 WBkfm5kl4UDxLeNHMQd5i+F4CybTZa1J0em+3cfv6uGfg9Xhimro4NQRRQm+YSel 8kl0+SYbNc60qk5acK9GNIeOxd3dfhO3LqfmCvDSqpURKfuo3XAawOH6x4y9vM5L +PNcNPwQhRRAJZQfeJUGzHjrNMqzm3XRubUhf3HCP331mCU0T48y4y/x+7z4hA8X WI01IdChqob0TcJ3WTwaYsSYlYHeQ==
X-ME-Sender: <xms:I1APYOi5_9_3ZWPKG3aMZudiRJmOLyzbAjj7fyA-Nrm_CMpde7ZVMA> <xme:I1APYPCzvvobfa9wdMfNKGvCysmhfrJ8fdzC70kXug-Yz-qiab3tCUzG37L5whNX- jxWpAezpEgVEA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeggddthecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedtheefgf efgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:I1APYGGVfBHgrymXG3u1qSI4AtOHs9VhyXJfZZjr5MxjIviPFG1DPw> <xmx:I1APYHQskHg0HyqcQFQ_EcKpusUYhlRho_SVwTwuQ3jJv2D6PgZRxw> <xmx:I1APYLzphqyxFSkE2Bvgd_e43I_maKpgvLNOjFm3zsOKxWh_opPgJg> <xmx:I1APYHiqLh1O4TOvTQan00YAN17WFoQpeFbdr38oho8eX5RLKXSh_g>
Received: from [] ( []) by (Postfix) with ESMTPA id 3EA5D240066 for <>; Mon, 25 Jan 2021 18:11:30 -0500 (EST)
Subject: Re: Diversity of candidates was Re: NomCom 2020 Announcement of Selections
References: <> <> <BA07FAFAE7BBE5C47BCB7F58@PSB> <> <28656DF8FE9CF8FD65A91C6E@PSB> <00bd01d6f2a8$9d454b40$d7cfe1c0$> <> <> <> <>
From: Keith Moore <>
Message-ID: <>
Date: Mon, 25 Jan 2021 18:11:29 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 25 Jan 2021 23:11:34 -0000

On 1/25/21 5:08 PM, Salz, Rich wrote:

> One idea about addressing this is that we change the AD job to not be so full-time.  Or add more AD's.

IESG is not embarrassingly parallel - adding more processing elements 
(ADs) creates more overhead for everyone.    For that and other reasons, 
neither IESG nor IETF as a whole scales very well.

At a time when there was much more participation in IETF than there is 
now, I looked at what it would take to make IETF scale better, and 
didn't find any good answers.   If we could reliably separate the issues 
that require broad consensus from those which don't, that might 
help.     If we could reliably distinguish between issues that IETF 
needs to take on from those that don't, without making it really easy 
for competing organizations to circumvent IETF on the important issues, 
that might help.

But these are some of the problems for which the obvious solutions have 
a lot of potential to create worse problems.   (The cause of problems is 
solutions, after all.)   That doesn't mean don't look for solutions.   
It does mean don't presume that a "new" approach is better simply 
because it's new or different, and the problems therefore aren't as evident.