Re: Want to be on the IESG?

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 04 October 2021 15:33 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C1783A08FF for <ietf@ietfa.amsl.com>; Mon, 4 Oct 2021 08:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58-6QKvqBfei for <ietf@ietfa.amsl.com>; Mon, 4 Oct 2021 08:33:04 -0700 (PDT)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE3573A08DE for <ietf@ietf.org>; Mon, 4 Oct 2021 08:33:03 -0700 (PDT)
Received: by mail-vs1-xe32.google.com with SMTP id y28so6238035vsd.3 for <ietf@ietf.org>; Mon, 04 Oct 2021 08:33:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fts/+yROv8V/UZfAYHZdnKb4FFmt0y8VmFiEpl5m0C0=; b=CXPwcKgxu9wVjJT1HAG3APJ3kwcKhvWjhS5w+zTVSFRbfrPGL8z3Fy4JZH1tf1EYku 3Bh7K1guJdms4C2ZHnfNZvDdoc33H1UOYQzJmz3odUyztpDZHhrUeerWoZTH7WlWpO+3 aVIiM4LH+E6EGSDlZbOK0aob6ew+y9zzET4fI9h2bnnRkpUWDXsTnnBKojxJ/eDYHbPI JocOa9NkpK/n9HHDEW4WF8LXA4OGsuVWttiJDvyR+qBkyUr/0uv1NuKokEkEXjXUP/Hy lFfOR/DSMh07JFB94rMnJMuKcrRvZyHVC9crbQuL3nPDH/kvpj6Pnj1Sn8ZBAdN/s8R3 4Qeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fts/+yROv8V/UZfAYHZdnKb4FFmt0y8VmFiEpl5m0C0=; b=M8/89/h1RixW6zBxOVzmKfUk6GuOtUWMCZ2A/Bo0RMu1/+quZhx/8i3gETSqxzhc8K XA9levIa462/XujLRCO1zKU8I+vwGPl4OsnGUQulABwZQa7Fyzs3QyRCKFNDyXlsQXuF tQXlAcKe9akZYKviTsuZuS5EG0Muxjd9VSkszJB20FeYlVH9kmhQdCD/jBxYiKw5khTf MTH3oSEflILhXFcQFomuDjcigEmqedEiIM4R3hJ+6oOKfGcNYkwZ5uz7QvPjHG61gQDm 267FePnS2iMqUkmXWN53QgswsSmN3BRdeoGx9ftNQBKiKxX1TtunhkJ271mxX6SQZx2e a1lg==
X-Gm-Message-State: AOAM530cVvpREjm0fYsHv1zjE+wZdV0kfJN+AOad0RKh+QTK8rP6gw76 nyhOdaDEmOzj37c0ePz1fqDHy437r83bGGi0Nx4=
X-Google-Smtp-Source: ABdhPJxh6fJ+jLXFJIirThxhKpx/j9YvT0d4snQq3mOvLWHfUT+IeP4wPrKKn7LgR0Ce7P2IWqbwE7HIhZue3zvtOBc=
X-Received: by 2002:a67:1004:: with SMTP id 4mr14035464vsq.26.1633361582342; Mon, 04 Oct 2021 08:33:02 -0700 (PDT)
MIME-Version: 1.0
References: <2A8C8B98-CBA9-4BF0-82C5-594B0F309F07@akamai.com> <FA5A7C084BDEF72CE3FC510B@PSB> <CAF4+nEG1-isV2aKgrtFE=Yv2RNyv-XP=ysN3ZeE-H8bNTykx7g@mail.gmail.com> <9A7FD2DE22C1D2ED1AB9E21D@PSB> <6D74EDE3-0F73-4C97-B9CC-65624BF95FF9@akamai.com>
In-Reply-To: <6D74EDE3-0F73-4C97-B9CC-65624BF95FF9@akamai.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 04 Oct 2021 10:32:36 -0500
Message-ID: <CAKKJt-fv9NAK-XGwWYBSn1dU8KNn-mHc0i-9MNNXTwPG88itFg@mail.gmail.com>
Subject: Re: Want to be on the IESG?
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: John C Klensin <john-ietf@jck.com>, Donald Eastlake <d3e3e3@gmail.com>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e7e12605cd88a04c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B_E9n8KS3xuYdL3wxF4D1q8fIr4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2021 15:33:12 -0000

Hi, Rich,

On Mon, Oct 4, 2021 at 9:06 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>
wrote:

> >    then making a big deal about getting additional candidates for a
>     slot that will almost certainly be returned to the incumbent
>     (because they are completing their first term and have done a
>     competent job) may actually discourage candidacies for other
>     positions because, unless people clearly understand the
>     distinction between first-term and later incumbents -- a
>     distinction those public calls rarely make-- the impression is
>     that there is no point being a candidate against an incumbent
>     unless one is prepared to argue that incumbent has done a bad
>     job.
>
> When I was first asked to stand for Security AD, I was told that I should
> consider this a practice run for future because it was almost definite that
> the current incumbent was going to be re-selected. I don't know if that is,
> or was, still commonplace.


I certainly learned a lot, the first time I accepted a nomination for a
Nomcom-reviewed position, and I've made that observation to other people
more than once, when they asked me for advice about accepting a nomination.

But it's also worth noting that even the people on the Nomcom (who
shouldn't be telling anyone that) don't know for sure who will be selected
in advance, because that depends on a lot of factors, and not all of those
factors are under anyone's control.

Perhaps it should be. It has to be a negative impact on the nominee pool,
> however. Because it means that if you want to be an AD, you have to
> convince your employer that it will be a couple of years of
> nearly-full-time commitment, but not immediately. That means convincing
> them at least twice.
>

And if you told your boss "yeah, but this is really a practice run, because
I'm very unlikely to be selected this year", and then you ARE selected,
that's going to be an interesting conversation when the Nomcom contacts you
to confirm that you're still willing and able to serve.


> The public information about candidates should include all previous
> nomcom-selected positions they've had. It should be fairly simple to link
> the nominees to their "dt.ietf/org/person/Lars%20Eggert" page, for example.
>

Hmmm. You can see that information in
https://datatracker.ietf.org/person/Spencer%20Dawkins for me, but it's in
text that I wrote, which means that it may not be present for everyone. My
current roles are listed, but not previous roles. Mostly, my previous roles
don't matter, but for Nomcoms, they're more likely to matter.


> More importantly, I notice many of these same suggestions being made
> annually.  The only forum we have for preserving these things is the
> previous Chair's recommendations, which doesn't seem good enough.
>

I couldn't possibly comment. 🙂

Best,

Spencer