IETF Logo Mail Archive

Re: [Eligibility-discuss] don't repeat what's not changing in 8713: Ineligibility by being a board/group member.

Lars Eggert <lars@eggert.org> Thu, 22 September 2022 06:37 UTC

Return-Path: <lars@eggert.org>
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 54541C14CE22 for <eligibility-discuss@ietfa.amsl.com>; Wed, 21 Sep 2022 23:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_HI=-5, 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 (1024-bit key) header.d=eggert.org
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 5JH105TzpVF1 for <eligibility-discuss@ietfa.amsl.com>; Wed, 21 Sep 2022 23:37:09 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 762BAC14CF1F for <eligibility-discuss@ietf.org>; Wed, 21 Sep 2022 23:37:09 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:90d8:1982:a231:fd6d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 66DEA1D34B4; Thu, 22 Sep 2022 09:36:54 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1663828614; bh=BlzwkSn6yls0iUfRNnezfcJNoeL5e1HzhjD0A8NsW9g=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=C104o4DeTzX8kRCuDHrl6MBCgp22rV/rxsZKhuKV+0ECXoav2T60QnpvBiEaChm9p I/zuJj4UkpKSpE4xBQymkUDz4j177wrN58wEK3Q1zAngxKk0CMLiTW4h+V+YhcrByh PaQ1SuCCmiPRs+gzgQKYGS96gUwoMcB4J3Dk08Sg=
Content-Type: multipart/signed; boundary="Apple-Mail=_72AC7A25-940D-4AF8-891F-A4A59B5665F6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <67C640F419A6D42216A93B56@PSB>
Date: Thu, 22 Sep 2022 09:36:43 +0300
Cc: Barry Leiba <barryleiba@computer.org>, Martin Duke <martin.h.duke@gmail.com>, Robert Sparks <rjsparks@nostrum.com>, eligibility-discuss@ietf.org
Message-Id: <C3835739-DA56-40BA-9396-3F0E37ED5696@eggert.org>
References: <CAM4esxSNzWQ1+0ppjTeOqnUvju09-Nshm7sWq_Yx=u5YikJT=g@mail.gmail.com> <75c01ef9-8384-2784-c14d-7781ff51657c@nostrum.com> <CAM4esxRXAcB6Q8Ea36nPUX9AzjmiemA=1+_UAa=wMN=JsaAVuw@mail.gmail.com> <CALaySJJQOXF8uQoWDKTt-0Xpin1C14E0D=m3HWZY5dOgO2xTLA@mail.gmail.c om> <67C640F419A6D42216A93B56@PSB>
To: John C Klensin <john-ietf@jck.com>
X-MailScanner-ID: 66DEA1D34B4.A4D2A
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/zDISAqNOkPQ8k4J8hdiksydWciE>
Subject: Re: [Eligibility-discuss] don't repeat what's not changing in 8713: Ineligibility by being a board/group member.
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: Thu, 22 Sep 2022 06:37:14 -0000

Hi,

AD hat on.

On 2022-9-21, at 21:31, John C Klensin <john-ietf@jck.com> wrote:
> FWIW, there is an argument for completely replacing 8713 rather
> than adjusting things where needed but relying on it for
> everything else.

There is that argument, and it was brought up in discussion, but:

> While I suspect it would be impractical given the schedule,

This. We need to have a specific fix in place by the time the next NomCom cycle starts, and I believe this will not be possible if we open up all of 8713.

> If we cannot do that,
> the second-best (and more practical) option would be to make it
> extremely clear that one looks in this document for a complete
> replacement for Section 4.14 (and maybe 4.15, see below) of RFC
> 8713 and that 8713 is authoritative for everything else.

That seems like an actionable suggestion, and your text suggestion (which I cut) looks reasonable to me.

I'm open to discussing a rechartering of the WG to do other changes to the NomCom eligibility criteria after it has delivered its chartered work item, but not before.

Thanks,
Lars

v2.28.0 | Report a Bug | By Email | System Status