[netconf] IETF Chairing Pipeline…
Warren Kumari <warren@kumari.net> Tue, 22 October 2024 01:35 UTC
Return-Path: <warren@kumari.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AEDC1516E2 for <netconf@ietfa.amsl.com>; Mon, 21 Oct 2024 18:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PBz0uWBX0-K for <netconf@ietfa.amsl.com>; Mon, 21 Oct 2024 18:35:00 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3F7CC151091 for <netconf@ietf.org>; Mon, 21 Oct 2024 18:35:00 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-37d4a5ecc44so3774691f8f.2 for <netconf@ietf.org>; Mon, 21 Oct 2024 18:35:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; t=1729560898; x=1730165698; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=HHxEvFT7Au4wns8K4LdcbHywF6q9CxpdRh3DW1Aix00=; b=fZ81UI2eLincl6tOyNMFkYPwrtzsxJrCUvhj6gGCE9SGHtlaa8HL5XtC0pGT5lDM5j sAI3oPKMPq+/ZtpemaaMQdn4LWYjo1ipJOB+80hwnQLyMta3QFSinjPScKEkn+pN59ov E5pSelLv2CAZiaJMds7ZjzDYNj3qHu8m92P8no1DeHDcHquGqAcipJX972mpVe3+iFm0 rT1S1eyg9eQC6G7xJJHSW10tFGFr3kH/02dlTaAS3qYeutLhsg7ibxT8mIK46lx7KGf9 ozLJwXGX2V5WyvT5WzZI3CX0rayJTezwc1jzoqamlKNvlzY2JyvDrpXqKZEM843JBjtg 1kpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729560898; x=1730165698; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=HHxEvFT7Au4wns8K4LdcbHywF6q9CxpdRh3DW1Aix00=; b=eo+0IfyK8+6tm2UZZRg9uySJ2arRUBBR3LWFFuRfUitwTuZYrCTrrBU9+QQKXQ0fGz n9Mw7OZGzPveP8r7/Ou48Hgnhy1q3SUxbW5CIyG4wA9iJwizXL8NCAo4Pl5sr3qDZI/V vPUSbruuhDnDKoWBnt2ackDxb+ahbqgLt3EwMyZaSAqXLqeT0UYtIvanEeRT9G3yw8b5 L0WAnqRQ9F/1NI5QwrlIYc8ji4PaoMwI9zgBTS9tXOfcG3DSfOOHuFeKBIjzQVTdBmjk KK7Qh8G7yZwCXrp4TtaMOq3tuTD1mxfEynwRqLIizxwwD2Wnmgo9DLVXq8+S9uqtGQt+ aDjw==
X-Gm-Message-State: AOJu0YzRuj+OB3ZQ0sDJo5rxEKQ20VhlSQp+mTlyen5Jw5WX3Wh3YA6U Rq4bw0W+pGN29hCbGiVDrrpKmh2dQUmV/caI1w4rt73mg0btT+TTCVSbCpMNFlnTDgohBgfcpKn ANxH9fdt18Mi0XbVK0AsM+VmPTlpkRfTNk1rz//J6yJUJloUkpJ8=
X-Google-Smtp-Source: AGHT+IEDufRCaS/8++lzvT7a4gQAAXPtO4SAfBVclkQocR/KEUMMcdk3RcMtoQDWVsvY/kxqJvMPs0G+TSV2T/gqNXo=
X-Received: by 2002:adf:ef4a:0:b0:37d:5026:f787 with SMTP id ffacd0b85a97d-37eb66bfa8bmr8042559f8f.38.1729560897997; Mon, 21 Oct 2024 18:34:57 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Mon, 21 Oct 2024 18:34:57 -0700
Mime-Version: 1.0
X-Mailer: Superhuman Desktop (2024-10-21T19:05:50Z)
From: Warren Kumari <warren@kumari.net>
X-Superhuman-ID: m2jrw1d8.2a4bb339-d52a-4783-a75c-408b596f97dc
X-Superhuman-Draft-ID: draft0076ffdc5232d7eb
X-Superhuman-Thread-ID: draft00c4efab05e5cac7
Date: Mon, 21 Oct 2024 18:34:57 -0700
Message-ID: <CAHw9_i+s_b+HrosQ+HuWvnqgh7U6gZVJp_uNXNH1TSQQ5LFNBg@mail.gmail.com>
To: Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f16fc9062506c619"
Message-ID-Hash: PFW2LUELMTKG4I6HFTT3O5BUC4PWOAZI
X-Message-ID-Hash: PFW2LUELMTKG4I6HFTT3O5BUC4PWOAZI
X-MailFrom: warren@kumari.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] IETF Chairing Pipeline…
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/OXe2No-3vmj0HVhX-z2Ck6T2OuQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>
Hi there Netconfers, Apologies if this mail seems familiar - I sent it (or a variation on it) every few months. I also send it to most of my / Ops WGs, and so you might see multiple copies. I do think it is important though, so… An evergreen 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. Currently when a new chair needs to be appointed the process goes something like this (with much 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!". (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... If it is a new WG there is usually a BOF and additional discussions on BOF proponents and chairs, but the general principle holds) 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. 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. I've created a Google form to record answers / help me keep track of volunteers: https://forms.gle/JvnD6fwzfuVv6SqS6 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. Obviously, if you are not comfortable filling in the form but still want to volunteer, just email Warren and/or Mahesh. Also, as always, if you have any questions, comments, etc do the same.... Warren and Mahesh.
- [netconf] IETF Chairing Pipeline… Warren Kumari