Re: [Eligibility-discuss] Discussion: do eligibility paths need to be monitored
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 26 August 2022 22:01 UTC
Return-Path: <brian.e.carpenter@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 49100C1524B8 for <eligibility-discuss@ietfa.amsl.com>; Fri, 26 Aug 2022 15:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 vcL7a9oZbEBg for <eligibility-discuss@ietfa.amsl.com>; Fri, 26 Aug 2022 15:01:39 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 86EF8C14CE36 for <eligibility-discuss@ietf.org>; Fri, 26 Aug 2022 15:01:39 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id x19so2704331plc.5 for <eligibility-discuss@ietf.org>; Fri, 26 Aug 2022 15:01:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=XvEWLdTP12+jkH31Qz1RIjtLoj5HzpXwR07Z3mSoUjM=; b=TIQgxHTDY4CBW7KZHB3cGXN2XsxjA4YNodbMY80rJXsWQ7U3sL88forYXWQCykhaO1 gQwN1ub0LaUs/B2nPtlMe162EkOZL7UsNxX2RjcUsrA6O7hTWM+6DIZcONsP/P/WYTik kY0I5YLvw0H3n4HMp09e1ZdIz9GBHj6qrF42g4YovgDSeKY4bS2IasM0LHDLrBQ1iUT0 fCSPg5yuCOSZx1dejzP6j9/5+D4MW++P5boDfjZYY4MfSPcIFKCr/LQtZYoyUlhyM7Pf XLQ/No2rJEhAnRDY+XQj992ocsI+jCZy82/21l5YsoEQbjzwWfUhb+Ptk9rn80KcgvJv 7egg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=XvEWLdTP12+jkH31Qz1RIjtLoj5HzpXwR07Z3mSoUjM=; b=O3L8zpELAtEECS1GH8PzIUf2qxfQkYQDv6PkPQ3WwWsmuQKgxnXa3VgtljBn2RJorE pDAP2nfvfleYKNHbtqR+VaE/DbQapnWGPm0i6jBqZ/+perD4zkCMvA/eE1izfaImYrhL iXq3dFio7GAI77jfvZ0xKrzNWBcLiEx/EbIH3E7l3+i9HSERLD0hvkBU3D85RkdicuuX iYGCoBNJVW6gKg5no6qG4pb2jU65iEU268Ac7qfjq78cT/S4EqmRcuATtObvAjDeXkIH 249gRaUIN0eZIKueJAlgc4b6tIS1H8ehc9owDJo9tPUA73ONSgev+jo4FtYa8pGuYeZd 3qpA==
X-Gm-Message-State: ACgBeo04W0Fn+zKZ95YasoFymZTnmsaH92uYwJoYWeVvOtCB5tssz9S/ FaM9zwodr8QYSHIvOJipWAfRHvIBuLw=
X-Google-Smtp-Source: AA6agR7ZHOKiiO8UYVnIkqulJFh1yBiXSXhiQ5Bpk3eQ8Dwv3QGy3f7SkyW07EdfWgGuYi9BjkOJ4Q==
X-Received: by 2002:a17:90b:4f8b:b0:1fb:2bc6:abd9 with SMTP id qe11-20020a17090b4f8b00b001fb2bc6abd9mr6451949pjb.227.1661551298467; Fri, 26 Aug 2022 15:01:38 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id i10-20020a17090332ca00b0017292073839sm2123944plr.178.2022.08.26.15.01.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 26 Aug 2022 15:01:37 -0700 (PDT)
Message-ID: <9663119a-fdb3-b349-c1cc-9fcf2e88da08@gmail.com>
Date: Sat, 27 Aug 2022 10:01:33 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Barry Leiba <barryleiba@computer.org>
Cc: eligibility-discuss@ietf.org
References: <CALaySJ+uvZME0bWQnB9tSvABxkjgsTG8xpfLT1g62bBL3QeG6w@mail.gmail.com> <e6eaa9c5-b73f-b155-725a-b49fb48e15c0@cs.tcd.ie> <CALaySJKoK_3JVuDYXsc27R9zRTb=tSuTPuJcV9z4c61JpVtCyg@mail.gmail.com> <f612028a-ba66-f543-adaf-28cfda81bad7@cs.tcd.ie>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <f612028a-ba66-f543-adaf-28cfda81bad7@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/6g_MpNVunberaw8mqPQylz7JAkA>
Subject: Re: [Eligibility-discuss] Discussion: do eligibility paths need to be monitored
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: Fri, 26 Aug 2022 22:01:41 -0000
On 27-Aug-22 08:39, Stephen Farrell wrote: > > Hiya, > > On 26/08/2022 20:55, Barry Leiba wrote: >>> what's the probability we end up with a nomcom where >>> N voting members who did not attend a f2f meeting in the >>> relevant timeframe are only eligible under path 1? > > >> Can you clarify? > > Sure. > > Path 1 allows for f2f or online attendance, which I support. > Let's ignore the people who were in-person at one or more > relevant meetings and only think about those who qualify via > path 1 but never attended in-person at a relevant meeting. > (And who don't qualify via part 2 or 3.) > > For N=1 to 10, I'm asking if we might want to estimate the > probability that we have N such voting members, and whether > we want to worry about that or not. > > mcr said: > > I think that you are dealing with the _6.1. A Surge of > > Volunteers_ threat, right? > > Not quite. I'm not concerned with a deliberate attack, but > rather about whether we want to worry about the probability > that few of the voting members have recent f2f attendance. You mean that the organisation that created many of the technologies now used worldwide for on-line meetings should be concerned about its nominiating committee consisting of people who attend via on-line meetings? > That wasn't an issue with 8989 since we were all online but > could be a thing to consider now. > > BTW - I'm not asking we try specify what to do in the event > of such a situation becoming worrisome as that'd be out of > charter. I'm just asking if we want to ask for this to be > monitored, or to establish some threshold that'd cause the > criteria to be revisited. Yes, it's a good idea for the data to be gathered and analysed. But I have no preconception of what we might discover. Brian > > Cheers, > S. > >
- [Eligibility-discuss] New ELEGY working group -- … Barry Leiba
- Re: [Eligibility-discuss] New ELEGY working group… Stephen Farrell
- Re: [Eligibility-discuss] New ELEGY working group… John C Klensin
- [Eligibility-discuss] Discussion: do eligibility … Barry Leiba
- [Eligibility-discuss] probabilities of N voting m… Michael Richardson
- Re: [Eligibility-discuss] Discussion: do eligibil… Stephen Farrell
- Re: [Eligibility-discuss] Discussion: do eligibil… Brian E Carpenter
- Re: [Eligibility-discuss] Discussion: do eligibil… Stephen Farrell
- Re: [Eligibility-discuss] Discussion: do eligibil… Michael Richardson
- Re: [Eligibility-discuss] New ELEGY working group… Salz, Rich
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- [Eligibility-discuss] Considering I-D contributor… Lars Eggert
- Re: [Eligibility-discuss] Considering I-D contrib… Eliot Lear
- Re: [Eligibility-discuss] Considering I-D contrib… Eric Rescorla
- Re: [Eligibility-discuss] Considering I-D contrib… Michael Richardson
- Re: [Eligibility-discuss] New ELEGY working group… Luc André Burdet
- Re: [Eligibility-discuss] New ELEGY working group… Salz, Rich
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- Re: [Eligibility-discuss] New ELEGY working group… Brian E Carpenter
- Re: [Eligibility-discuss] Considering I-D contrib… Brian E Carpenter
- Re: [Eligibility-discuss] New ELEGY working group… Eric Rescorla
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- Re: [Eligibility-discuss] New ELEGY working group… Eric Rescorla
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- Re: [Eligibility-discuss] New ELEGY working group… Eric Rescorla
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- Re: [Eligibility-discuss] New ELEGY working group… Eric Rescorla
- Re: [Eligibility-discuss] New ELEGY working group… Joel Halpern
- Re: [Eligibility-discuss] New ELEGY working group… Stephen Farrell
- Re: [Eligibility-discuss] New ELEGY working group… Salz, Rich
- Re: [Eligibility-discuss] New ELEGY working group… Joel Halpern
- Re: [Eligibility-discuss] New ELEGY working group… Salz, Rich
- [Eligibility-discuss] ISE vs IETF Stream RFCs for… Michael Richardson
- Re: [Eligibility-discuss] New ELEGY working group… Michael StJohns
- Re: [Eligibility-discuss] New ELEGY working group… Eliot Lear
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Adrian Farrel
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Michael Richardson
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Adrian Farrel
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… John C Klensin
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Michael Richardson
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Michael Richardson
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… John C Klensin
- [Eligibility-discuss] RFC criterion [was ISE vs I… Brian E Carpenter
- Re: [Eligibility-discuss] RFC criterion [was ISE … Stephen Farrell
- Re: [Eligibility-discuss] RFC criterion [was ISE … Michael Richardson
- Re: [Eligibility-discuss] RFC criterion [was ISE … John C Klensin
- Re: [Eligibility-discuss] RFC criterion [was ISE … Michael Richardson
- Re: [Eligibility-discuss] RFC criterion [was ISE … John C Klensin
- Re: [Eligibility-discuss] New ELEGY working group… Barry Leiba
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Donald Eastlake
- Re: [Eligibility-discuss] ISE vs IETF Stream RFCs… Michael Richardson