IETF Logo Mail Archive

Re: draft-sullivan-nomcom-chair-select-00

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 15 February 2022 17:52 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0B3743A0F44 for <ietf@ietfa.amsl.com>; Tue, 15 Feb 2022 09:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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, RCVD_IN_DNSWL_MED=-2.3, 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=sandelman.ca
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 m9cYhc42i2Nk for <ietf@ietfa.amsl.com>; Tue, 15 Feb 2022 09:52:17 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CAC33A0EE5 for <IETF@ietf.org>; Tue, 15 Feb 2022 09:52:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 05690389EF; Tue, 15 Feb 2022 13:00:18 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id irVg8ZAouIEz; Tue, 15 Feb 2022 13:00:15 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 96A8A389EE; Tue, 15 Feb 2022 13:00:15 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1644948015; bh=KcDNbNDWjnludkupq/CzW+PYQBJZv0EzVXkbH2ARn0Y=; h=From:To:Subject:In-Reply-To:References:Date:From; b=bGrBaWuXXRfrv6LqX2UVyKGtHGjnqN+RWvv19X0dPjDpFOpAsSuV5li7yWbh82qeS poZ8R9NxWhFf3wVtaGen6Lq/pCpiWvjopK9LQgnrIqXpYIt+5CaedpjB6e4XTJBCHu AWgkV9k0XZZtpJO/j0ugZF8nsdgZ2mLZ/e4QzbMvahttHLvcJP6HWXvFWZ4vsXM1S9 BacRYqD/P1ki4P7pNIZysxYsDpXihQjPwhwYyf0cFaMxilcW3IHAr7ckDpHMCVMctq kVa2C0AOIW6PFg+rbQATN3DBKPKXMGOLn4vXtHYgGbnSYEII10b3bJprglP/THX3s2 XREeEE6AXe66w==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 380CF754; Tue, 15 Feb 2022 12:52:11 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@lear.ch>, Andrew Sullivan <sullivan@isoc.org>, ietf <IETF@ietf.org>
Subject: Re: draft-sullivan-nomcom-chair-select-00
In-Reply-To: <c461ab52-8611-f3aa-357d-18d2539a3e0b@lear.ch>
References: <20220214055405.v7qujqp5lmqynga5@outlook.office365.com> <c461ab52-8611-f3aa-357d-18d2539a3e0b@lear.ch>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 15 Feb 2022 12:52:11 -0500
Message-ID: <31636.1644947531@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6H2p6Mk_JxHwvcuy76g1lyc164Y>
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: Tue, 15 Feb 2022 17:52:22 -0000

Eliot Lear <lear@lear.ch> wrote:
    > Is this something around which that the NOMCOM should simply self-organize? 
    > Perhaps that's a fallback mechanism?

The chair has to run the random selection process.
It's a rather important part.
So, we can't self-organize that part.

An alternate (RFC8713 changing part) process could be to have the nomcom
self-organize, and then, the previous year's chair could run the random
selection process.  That would require some non-trivial edits, but mostly it
would just be moving text around.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email