Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt

Robert Sparks <rjsparks@nostrum.com> Tue, 23 May 2023 14:30 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB80C151079 for <eligibility-discuss@ietfa.amsl.com>; Tue, 23 May 2023 07:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level:
X-Spam-Status: No, score=-2.078 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 (1024-bit key) header.d=nostrum.com
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 EZcxbWkQEESO for <eligibility-discuss@ietfa.amsl.com>; Tue, 23 May 2023 07:30:52 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E068FC151073 for <eligibility-discuss@ietf.org>; Tue, 23 May 2023 07:30:51 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 34NEUnGV047628 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <eligibility-discuss@ietf.org>; Tue, 23 May 2023 09:30:49 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1684852249; bh=IqDB4KAYCP1+qecrg5csGSiq7VeXOg70yizDHINH9ws=; h=Date:Subject:To:References:From:In-Reply-To; b=gDWupt5YSeWH3rrnPT0zEIn+IwVIG89OtO3D+uOg30IcIRdw9oJZ148zp0lcOEWWr yqpFTVplg/XS1f7ryJAfMkkyhcuMp1RRC5U7h7Z5dMiddEHt/XmvNsTxWfZxy+nMUM meFlSsFyZwvbE52OhINKgi9/5rKBys9qehagi5Lc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <4bd46dd8-bc23-fd22-ce55-274bc4f9095e@nostrum.com>
Date: Tue, 23 May 2023 09:30:44 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: eligibility-discuss@ietf.org
References: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org> <52d600e9-c5fd-a086-9690-d4ac4a6d6de2@nostrum.com> <e1715390-46c8-528f-ad12-254313e2267c@gmail.com> <18664.1684799255@localhost> <7d91e9ac-67a1-c3b1-6523-54e7b0fc151d@gmail.com> <CALaySJJOZOpBxmSrxSq8ki8dfHG1egdqm9c=WnmcGUCU0iuWHQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <CALaySJJOZOpBxmSrxSq8ki8dfHG1egdqm9c=WnmcGUCU0iuWHQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/dJBAt9e1eaPBbkVJmxvE3hNat9o>
Subject: Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2023 14:30:55 -0000

I _do_ see a reason to use a separate group.

If, in the lifetime of the effort that is working to change the 
selection process, we end up with another reason to change the 
eligibility criteria, and have to do so on a deadline, having the two 
groups with two different charters will help keep the different efforts 
on track.

Throwing it into one bucket will encourage scope creep across the 
efforts (and make it harder for people who are coming to the 
conversation freshly understand what the purpose of the bucket even is).

RjS

On 5/22/23 7:17 PM, Barry Leiba wrote:
> Personally:
> I don't see any reason not to keep the "elegy" working group with a
> new charter that's designed for the new work.  I don't really care if
> the WG nickname no longer directly refers to the work, and I'm happy
> to continue chairing.
>
> Barry
>
> On Mon, May 22, 2023 at 8:12 PM Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> On 23-May-23 11:47, Michael Richardson wrote:
>>> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>       > I concur with Robert, so I think the next stop is gendispatch.
>>>
>>> Okay, but is one of the gendispatch option to recharter ELEGY?
>>> Or is that already excluded from the list of options in your opinion?
>>>
>>> (Asking for information)
>> I actually don't care. If gendispatch decides that a full WG process is
>> need, it would a be a fairly profound recharter. The charter says
>> "No other aspect of NomCom selection or operation is in scope", and I
>> can't quite make up a suitable acronym, but I'm sure we can find one
>> if we have to.
>>
>>      Brian
>>
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss