[ippm] IETF Chairing Pipeline…
Warren Kumari <warren@kumari.net> Sun, 20 October 2024 20:21 UTC
Return-Path: <warren@kumari.net>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98334C1519B6 for <ippm@ietfa.amsl.com>; Sun, 20 Oct 2024 13:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 EC0X9KNcxn-3 for <ippm@ietfa.amsl.com>; Sun, 20 Oct 2024 13:21:14 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 5D7A1C15792A for <ippm@ietf.org>; Sun, 20 Oct 2024 13:21:14 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5c40aea5c40so6763930a12.0 for <ippm@ietf.org>; Sun, 20 Oct 2024 13:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; t=1729455671; x=1730060471; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=bY7EGUt1uoUTBT7Y+adHaa/tp37CemciTD4bE+IAcug=; b=AT/A05WZRVAaMEsO2PkWXOSW7l3hdIYodwNMViRVkrtSaqCaByORP4sDQvzDlpXJV0 M1lfuVnQxrPYtp4Eo5khszLn5pCRVXrim2R3CNk2hd1ZCgtR2GhyZLjBUCkS/xuJPw0r 0nD+8TyppEZ2xtLw1P3u8ceewuX57yukP0rkQuNlmLYqF5xXXrFMfiXGzmGaUudV3wv1 vQ2A9BmIZ8i1fNLvAXiNgnOkaX+o8SvLvmnhaAQvCykeeBpRRg2kKFYPyLkytPYKRtiM HXnIrI3Z6b/u3NyreUnuu3W4/IcZ+8VaCjFFuPHrlEFyhI9u3NdGkxOpo1Si2X4Z2Oh1 uOQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729455671; x=1730060471; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bY7EGUt1uoUTBT7Y+adHaa/tp37CemciTD4bE+IAcug=; b=Wo9WfcIi5D9QAxIrMF9nbCHrbFFaTpdw2dCOdgU9T11lr6Uz6fmdqoqc0uWYMya/i6 YXcDnsMPAAOBcbg1KdAt9Zt8SO6ODgEQMjWgZhMoZ191NUGjO1qKd1SjcgctLqaflpC+ 81Vf8DNcJRvvAx2DDkg5UCc1mpDkct/N/41gDVwuWpAxX0kDljcSPJkjaozg+6gHkUPY bR0oTFh1tY+gkD/kazMTPffBvfyhP6XP2mQ1lnnX0yez9rUzCZnohueEB3I7AeWO/D2m t1Eh04wPzm0oRNVxpNadTz0fUT6OM/Y97i5kUNbw9zDggsV8vI0sM+M/Vdh/A6BPfH9+ Zzvw==
X-Gm-Message-State: AOJu0Yzk/9igNhzS26sppeil8BjuOnz73N9DKqPCb70WvV+Zs/dtrgm6 s/RGgFDuEgJGD3lcxn7FbIaoDxuxbGBuCadaJDgfevlfCwCTNWWYWE6MSfjGhDfrkQCDYAGIgXd W4CGoJ1fvm3KvtJX4XaJ8dYkXmUWD/fmOBHe5wID+lvI9QbPN
X-Google-Smtp-Source: AGHT+IEY3cPow8mmSFv7rIOZ1KIWaukaNAX16f0uML2LTH+p8YZsFt06GAWriyJaz9CN617hvRoAcRYNmLCs58n16co=
X-Received: by 2002:a05:6402:5021:b0:5c8:df99:a6ec with SMTP id 4fb4d7f45d1cf-5ca0b0f4b83mr10338299a12.14.1729455671404; Sun, 20 Oct 2024 13:21:11 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Sun, 20 Oct 2024 13:21:11 -0700
Mime-Version: 1.0
X-Mailer: Superhuman Desktop (2024-10-18T19:06:04Z)
X-Superhuman-Draft-ID: draft006fd4ce4e419210
X-Superhuman-Thread-ID: draft00adb5b377dbe52c
From: Warren Kumari <warren@kumari.net>
X-Superhuman-ID: m2i18o27.17aa3d73-4bb0-41c4-aa49-29143c162dba
Date: Sun, 20 Oct 2024 13:21:11 -0700
Message-ID: <CAHw9_iL-a2qRLE_XQhp_hwagBffpGuv8zzq8RKyEOCJG=9QNTQ@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f30f520624ee46b5"
Message-ID-Hash: TBN3L75PYTBTNH2KKX7AZUMHY7NM4BYB
X-Message-ID-Hash: TBN3L75PYTBTNH2KKX7AZUMHY7NM4BYB
X-MailFrom: warren@kumari.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.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: [ippm] IETF Chairing Pipeline…
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/PqxOQ5pY5IBUqMGfffBKf6z9L4U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>
Hi there P Performance Measurementers, 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.
- [ippm] IETF Chairing Pipeline… Warren Kumari