From nobody Wed Feb  9 10:19:23 2022
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 66E293A0B6D
 for <v6ops@ietfa.amsl.com>; Wed,  9 Feb 2022 10:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
 autolearn=ham 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 9GKRzRmQ1vDQ for <v6ops@ietfa.amsl.com>;
 Wed,  9 Feb 2022 10:19:16 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com
 [IPv6:2607:f8b0:4864:20::633])
 (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 CAE3D3A0969
 for <v6ops@ietf.org>; Wed,  9 Feb 2022 10:19:16 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id z17so2921216plb.9
 for <v6ops@ietf.org>; Wed, 09 Feb 2022 10:19:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; 
 h=mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=R+4NVwJiuyZEeCfnCp405adjm8RWG0fnqRIbOKQQmTA=;
 b=hgKvbff8/9/PIRR07J039bR68UtVSgS0kKmrVxRfcac/qu3ckeVvdGCW3hGHhfjads
 ySW0Rzz4hKxvQmb+JJ7fsqJhcH9peXIFKA4IibgUKjNu6cSUFdk1HwJe4fcTfD5jBh+4
 UgnS65QRE8QzqedFmUCW4awE2nloIUWBFoAS2CfGfSg/M1lbjr0NIqQXD2oKqMEdS9C3
 3CqoZu5SKtnSqta2BA22/VQfahy1rp6fkwFVFzjxqd/KmincFFAjiMckcJJLPDCucYFo
 tv2o5cbORhwX0MI4YpftwaYjG/k69XY8OCLGXcodpc8tdjQB/BThUOAPX83dQyUcdd43
 a1Yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=R+4NVwJiuyZEeCfnCp405adjm8RWG0fnqRIbOKQQmTA=;
 b=VqoOLC2DNkhphlV6y6z48fuRQ6blwgN5GcHJn3Rg9q7N39xSj7T/cNf/NFcPwtFxxy
 RfDgXMDptSAqyKp9T7Vlkb1NYeHcqzHSTbZbaeVgt1QXYpUgmcjpG9D7V12yqSOOma4h
 2lMIC3bZXkNkH8bHCZJn8Ab9bHPqunqmGd730Rr/rC94r5UEwmN8/A7ybaiVHuP9SUHw
 5rRwCcO3ItfJgXwIADZQvNjK/VuI43PMIaPBTmfn7GKNRs+r72pPv18pdojgeDBp+OJm
 aB88fADQrNhU1hXX205acgfQpHoC2AY7njWfA4dlKyJmhy57J/ksx4/M8zt1L06ksZj5
 W+HQ==
X-Gm-Message-State: AOAM532wC383BwKSkOA3d8b4epLFN1vVtX2m/5GaYidIDI1pPcvtSzGO
 jjv8Sq4Fqm3+StMuaPARMyF5snUM57g=
X-Google-Smtp-Source: ABdhPJy2OsPE8FbrwRaI6jNZn6PWHigah/67eRXb/Zr1mig6rAhyHF/MW04TcmQl/tzJRV8r0WTaRQ==
X-Received: by 2002:a17:90a:8904:: with SMTP id
 u4mr4742070pjn.137.1644430755411; 
 Wed, 09 Feb 2022 10:19:15 -0800 (PST)
Received: from smtpclient.apple ([2600:8801:d008:8c00:ecc3:38e1:458:2c7a])
 by smtp.gmail.com with ESMTPSA id u2sm21596686pfk.15.2022.02.09.10.19.14
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 09 Feb 2022 10:19:14 -0800 (PST)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.61.1.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <CAHw9_i+8d5ztWCQY_a7Ow5Bv7_sdKmWmVDNk+UU6K7c6Q3kwrw@mail.gmail.com>
Date: Wed, 9 Feb 2022 10:19:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <89D1C94D-4F03-4B16-8E71-4D61994970DD@gmail.com>
References: <CAHw9_i+8d5ztWCQY_a7Ow5Bv7_sdKmWmVDNk+UU6K7c6Q3kwrw@mail.gmail.com>
To: IPv6 Ops WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3696.80.61.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6LDoo2AJgvX7dqQgTlocRTiJ1IU>
Subject: Re: [v6ops] Heads up: Asking your WGs for future volunteer chairs...
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>,
 <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>,
 <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2022 18:19:22 -0000

A note from our illustrious AD. Please read and consider.

> On Feb 7, 2022, at 8:41 AM, Warren Kumari <warren@kumari.net> wrote:
> Hi there all,
> An ongoing topic in the IETF & IESG is how to grow the IETF =
"leadership pipeline", so that when we need new AD and / or chairs, we =
have good candidates.
>=20
> Currently when a new WG is being formed, or when a new chair needs to =
be appointed he process goes something like this (with some added =
hyperbole):
> The AD(s) thinks "Hmmm.. I need a chair for FOOWG, and so I need =
someone who understands FOO protocol. Erm.... Oh! Mary! Mary knows FOO, =
and she's sane and friendly and organized and will keep things moving. =
Everyone knows Mary, she's strong enough to push back on the crazy, =
she'll keep the meetings running along... She has the added advantage of =
not working for the same company as $other_chair, but gets on well with =
$other_chair.  Oh! She's also already chaired BARWG and BAZWG and that =
went OK... She's perfect, I'll appoint Mary!".=20
>=20
> (In practice there is usually also discussions with the other chair =
(if any), a mail to the WG asking for volunteers, some discussions with =
key WG participants to see if they have any suggestions, etc, but there =
is still a tendency / bias to appoint someone known to the AD / "the =
obvious" candidate / people who have already demonstrated competence.  =
Clearly this is suboptimal...)
>=20
> Often, when appointing a chair, there is a bit of a rush - a meeting =
is coming up, a new WG is being formed, etc, and people who would make =
good candidates are overlooked, or are not really confident enough to =
put themselves forward for a specific role.=20
>=20
> So, what I'd like to try is asking for volunteers who'd like to be =
considered when we are looking for chairs. In some cases it is important =
that the chair(s) are experts in the technology - but a lot of chairing =
also involves more general technical knowledge, =
"leadership"/diplomacy/mediation, organizational skills, babysitting, =
etc.=20
>=20
> I've created a Google form to record answers / help me keep track of =
volunteers: https://forms.gle/P8dZ8diT7Y5kFsNA7
>=20
> Don't worry, filling in the form isn't a commitment to serve, but =
rather a "Hey, I'm interested, please keep me in mind when choosing a =
new FOOWG chair".
> Information will be shared with the current (and future) Ops & Mgmt =
ADs, unless you tick the "Any WG in the IETF", in which case your =
interest will be shared with other IESG members.
>=20
> Obviously, if you are not comfortable filling in the form but still =
want to volunteer, just email Warren and/or Rob.
>=20
>  Also, as always, if you have any questions, comments, etc do the =
same....
> Warren and Rob
>=20
>=20
> --=20
> Perhaps they really do strive for incomprehensibility in their specs.
> After all, when the liturgy was in Latin, the laity knew their place.
> -- Michael Padlipsky

