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

Luc André Burdet <laburdet.ietf@gmail.com> Thu, 22 September 2022 13:22 UTC

Return-Path: <laburdet.ietf@gmail.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 89EA6C14CF05 for <eligibility-discuss@ietfa.amsl.com>; Thu, 22 Sep 2022 06:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Ssd6qlrscQbX for <eligibility-discuss@ietfa.amsl.com>; Thu, 22 Sep 2022 06:21:57 -0700 (PDT)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 B914FC14CF04 for <eligibility-discuss@ietf.org>; Thu, 22 Sep 2022 06:21:11 -0700 (PDT)
Received: by mail-il1-x12f.google.com with SMTP id y9so4846345ily.11 for <eligibility-discuss@ietf.org>; Thu, 22 Sep 2022 06:21:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:from:to:cc:subject:date; bh=gr9Sw72wGy5+nkN8Prt6y28aqoubDXdCzZu9IoSEWW4=; b=IUZeeILvN4fSWkeaYx4YuygBW7b4z1nfkKpCij0rxOS6J+WvH26QnCcR0u4hzkhCZQ mHl+0QJcdALKEL6TmyfIgEaPD10uzUul3KcNw2HSuE5VesojZwwTOZ/27uo8J+GjBmmQ FKbDUpX62MRldAthxLf5iJsQe9SeLQziwz98l0UtJrVS6XRSh5JMqoO3ThPGYdJ1Tb5Z /xwNdFHCRvETA1W7MqJ5E+M8NgsvW2/ARUfXwP8uLFqwKPdMQTN6OemVNtxfav6r9xZ0 HxtHizlPAr/qtDLSDAUyRQVluKp/RadCaKi5QyeIvBPqr6FFanLUOsuJ1rNjy2psA/Z+ XzTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date; bh=gr9Sw72wGy5+nkN8Prt6y28aqoubDXdCzZu9IoSEWW4=; b=Wy2jB3DN989SclrkzdFWwHpnLYGhZWey0xy6vp9awTlpPPUYfiFqDDQd520kIRC78K FTsQQ6r5BSlH8FtjsdA8gAqyoOjJu4dY3fBNTqHO/YBOWFoupGVSRWXYHjflvnX12KFh H6fdp19feWwyswmvnRJZkRcyEjWOwLy4cR/mgXvRmrZyggAOGd2oA2e49P8IrXLrLLxd flL0TQgxkpDaVcR2yuTSo4+lhXDKbVdfm1WrIebLWf9GE4xD1G3Il30a6sI0cU/Vj+3Y oGALsEyZdBWcdvYmYsbBWBScdN21p1stDgug9hS/yqpE3TdyrTQ56dLcFAw899ufMi4N 4dKw==
X-Gm-Message-State: ACrzQf20qQ5sdDwvUTKVf+UD/19ESy0si5uTmfzAl6owJzcsyAR/ojVb 22+YPgBla1nnQedoa+3dz/Y=
X-Google-Smtp-Source: AMsMyM6lVh70DgYXVGd2DA9GBjw2aBqOUHKuCc6W/mHGNmhBZ58RyDpvihnEEx7EJFd0Vax9uVh+Aw==
X-Received: by 2002:a05:6e02:1caf:b0:2f2:1639:63a0 with SMTP id x15-20020a056e021caf00b002f2163963a0mr1564344ill.5.1663852870657; Thu, 22 Sep 2022 06:21:10 -0700 (PDT)
Received: from DM8P221MB0454.NAMP221.PROD.OUTLOOK.COM ([2603:1036:301:2847::5]) by smtp.gmail.com with ESMTPSA id f15-20020a056602088f00b006896f36afecsm2317799ioz.15.2022.09.22.06.21.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2022 06:21:10 -0700 (PDT)
From: Luc André Burdet <laburdet.ietf@gmail.com>
To: Lars Eggert <lars@eggert.org>, John C Klensin <john-ietf@jck.com>
CC: Barry Leiba <barryleiba@computer.org>, Martin Duke <martin.h.duke@gmail.com>, Robert Sparks <rjsparks@nostrum.com>, "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
Thread-Topic: [Eligibility-discuss] don't repeat what's not changing in 8713: Ineligibility by being a board/group member.
Thread-Index: AQHYzP1ASaEmSkIbzkWXV9mTAFP2+K3pB1cAgACCGYCAAK1ggIAAypCAgABq/xA=
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Thu, 22 Sep 2022 13:21:09 +0000
Message-ID: <DM8P221MB045472AB03DC881646A07C81AF4E9@DM8P221MB0454.NAMP221.PROD.OUTLOOK.COM>
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> <C3835739-DA56-40BA-9396-3F0E37ED5696@eggert.org>
In-Reply-To: <C3835739-DA56-40BA-9396-3F0E37ED5696@eggert.org>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DM8P221MB045472AB03DC881646A07C81AF4E9DM8P221MB0454NAMP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/sJLg1A4TWuFcZSxlSAxhml5Upb4>
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 13:22:01 -0000

Just 2 cents on “replacing 4.14 in its entirety”,  4.14 has other portions that would need to be repeated else they would be ‘replaced’ by nothing ?

PR: https://github.com/ietf-wg-elegy/rfc8989bis/pull/2

NomCom eligibility, and makes recommendations on how the process of
qualification based on attendance should work.
This document replaces the attendance criteria in {{Section 4.14 of RFC8713}} with
criteria loosely based on those in {{!RFC8989}}.
The other paragraphs of {{Section 4.14 of RFC8713}}
remain intact.

Regards,
Luc André

Luc André Burdet |  Cisco  |  laburdet.ietf@gmail.com  |  Tel: +1 613 254 4814


From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> on behalf of Lars Eggert <lars@eggert.org>
Date: Thursday, September 22, 2022 at 02:37
To: John C Klensin <john-ietf@jck.com>
Cc: Barry Leiba <barryleiba@computer.org>, Martin Duke <martin.h.duke@gmail.com>, Robert Sparks <rjsparks@nostrum.com>, eligibility-discuss@ietf.org <eligibility-discuss@ietf.org>
Subject: Re: [Eligibility-discuss] don't repeat what's not changing in 8713: Ineligibility by being a board/group member.
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