Re: [Gendispatch] Session at IETF 117?

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 30 May 2023 14:21 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 944CFC151B24 for <gendispatch@ietfa.amsl.com>; Tue, 30 May 2023 07:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 QxB36-hQ-SQn for <gendispatch@ietfa.amsl.com>; Tue, 30 May 2023 07:21:14 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A89DC1516F3 for <gendispatch@ietf.org>; Tue, 30 May 2023 07:21:14 -0700 (PDT)
Received: from [10.32.60.195] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged)) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 34UEPvjB006519 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 May 2023 07:25:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged) claimed to be [10.32.60.195]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Martin Vigoureux <martin.vigoureux@nokia.com>, gendispatch@ietf.org
Date: Tue, 30 May 2023 07:21:09 -0700
X-Mailer: MailMate (1.14r5937)
Message-ID: <B854E05F-CFC4-4C12-850F-01143B137AD2@vpnc.org>
In-Reply-To: <8C969658-FBE1-4E58-9466-4DD9558DE022@akamai.com>
References: <2c2cff09-93c2-322a-e370-5373f43c27b5@nokia.com> <B73BA12C-B21C-42DA-B798-7A6489063F94@vpnc.org> <8C969658-FBE1-4E58-9466-4DD9558DE022@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/92Fn-vJVF1bIZlyKsut07uzttcI>
Subject: Re: [Gendispatch] Session at IETF 117?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 May 2023 14:21:14 -0000

On 30 May 2023, at 6:55, Salz, Rich wrote:

>> There was a discussion on eligibility-discuss about having a discussion in gendispatch about what to do with updating the NomCom procedure, RFC 3797. I support having such a discussion at IETF 117.
>
> You mean the random-number choosing algorithm.  The NomCom procedure is in RFC 8713.  I think that needs to be re-visited, but I don't think that's what you meant here.

It is actually what I meant here. On the eligibility-discuss list, Lars Eggert said:

> My current inclination is to leave ELEGY in its current (dormant) state until after GENDISPATCH at 117, for it to be available as one of the possible dispatch targets for Donald's I-D. If the I-D gets dispatched elsewhere (or not at all) I will close ELEGY after 117.

--Paul Hoffman