Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions

Michael StJohns <msj@nthpermutation.com> Mon, 28 October 2019 04:20 UTC

Return-Path: <msj@nthpermutation.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 86B3D1200D8 for <eligibility-discuss@ietfa.amsl.com>; Sun, 27 Oct 2019 21:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylRYjm7Igj1I for <eligibility-discuss@ietfa.amsl.com>; Sun, 27 Oct 2019 21:20:46 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 7B5861200DB for <eligibility-discuss@ietf.org>; Sun, 27 Oct 2019 21:20:46 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id m4so7307667qke.9 for <eligibility-discuss@ietf.org>; Sun, 27 Oct 2019 21:20:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=rBc9vFJ0d4j/Hn26PEz869JkUiX4lFUUfeNcNP3I9V0=; b=fLEpUml7fFdqhB7VgmfVZgCHBeQL1jXRII7/YtB+/HofT64UyktqUWffzczFURjOAp 9u91DEKR4uNPezGCBZVxeB1LSkydDVUFotQJ5wEoulX8Ol4eeMfWreUgEiCts6vtsu4E Na+H1MphCVxnJrS4jXvVEP8xR9ZJbxBow31wSRuaLXW4TWhKvrkk+gSULwbjnJkhXIao 4UTSsIKMqBJiT+NcY8AKU08CFIAEvFM39j3L1vCyVIAkYebyFULjguNURuoIVP0YWaaJ +pHnvcx/YoqrHAuintFmM3ofxH5rFdm4tZ00XON/xOFsid9TCacL2mrUvhaRaJsFmX84 RpLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=rBc9vFJ0d4j/Hn26PEz869JkUiX4lFUUfeNcNP3I9V0=; b=CJ8GR+KDsFXpp1Ir/yfeucxNRUxam14s4tkH0Q+lSAndudt6lfs9nfsth5fWQQJA4v LK+kdHAZLhTtOXNpvGXAZjqOpgLrlCJSxepjdegb7qxlyF2/CbpVR1LKkGNOv7ZlUo1T Zj+t8n0SK4GSD5kgO5m5BQS2Rg8lSzxVNPHPIO3XcsbXPCLFLSFGQK0HmtyUNfMj/i7q 9piKTRzhkuxsnywI72sanZkXwVIM1TmQ7wRuZhV67VQybhRALHIAgGFdQLQp9Pcn8HI4 69+pZptEXPhT4tQinjWJOOk7eOdnN4vY2dgti51xCxlstDav4iSpJgbAPZkeqfAH6ioB jwgA==
X-Gm-Message-State: APjAAAVo5+9K+ZGSAYCZRZNs+ZicROCajPPEMppyk98m9NwIdEwmpc2Q DtUSVetv9pBNVEFJpcdI8OrZ5WEretM=
X-Google-Smtp-Source: APXvYqwKNUbMumscgK3SXdjX04HBWFaPsgHbISBcvCU/klsKMNDYVEmOsDkXYYOVPKwmHIGuEAEitg==
X-Received: by 2002:a37:a083:: with SMTP id j125mr7273496qke.55.1572236444812; Sun, 27 Oct 2019 21:20:44 -0700 (PDT)
Received: from ?IPv6:2601:152:4400:437c:a144:6d9:e069:bebe? ([2601:152:4400:437c:a144:6d9:e069:bebe]) by smtp.gmail.com with ESMTPSA id v4sm4667624qkj.28.2019.10.27.21.20.44 for <eligibility-discuss@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Oct 2019 21:20:44 -0700 (PDT)
To: eligibility-discuss@ietf.org
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk> <CB806045-0E5E-4445-A377-7CD547B9DD90@cisco.com> <010a01d58ac1$c0ab2320$42016960$@olddog.co.uk> <dc3bf13f-0178-8e4c-6680-ae3258ac1a9b@gmail.com> <865BF4B8-CB57-4586-8C2E-34B5218E53E2@episteme.net> <8D2605D0-33F0-4ED3-A063-A3F1469F3685@cisco.com> <B0B0A84A-D47D-475E-B37F-B6D9524A7D64@episteme.net> <CAL02cgQii6iuzh+sXd=S5T7ftOG+LeOcRKdtAkvhiTgVGFDT7w@mail.gmail.com> <F5AD56FA-AE72-4A30-8876-617479C1BDF9@episteme.net> <A6158553922F4866A5AB3667@JcK-HP5.jck.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <d6b2a713-f021-ca53-9b90-beedc7daa8df@nthpermutation.com>
Date: Mon, 28 Oct 2019 00:20:43 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <A6158553922F4866A5AB3667@JcK-HP5.jck.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/9xbaWQCwzs8EvNvMF3-iruP6_zg>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Mon, 28 Oct 2019 04:20:49 -0000

On 10/27/2019 11:47 PM, John C Klensin wrote:
> (and yes, Mike's suggestion of splitting the Nomcom function
> itself into two parts is, to me, fascinating and deserving of
> more consideration but it seems to me to be completely
> orthogonal to the proposal on the table.)

Not completely.   My observation was that splitting the Nomcom (and 
hence the related recall committee process - should have been more clear 
- I was dealing with lack of sleep) into two and making the membership 
of the IESG selecting/recalling committee(s) open to remote attendees 
might make some sense.  My thought here is that the remote-only 
attendees tend to have some idea of the standards related processes and 
giving them some say in the selection (or recall) of the people 
implementing those processes makes sense.

The IAB and LLC tend to be more about the support structure for the 
standards process and other things (e.g. IRTF, in-person meeting 
structure, long term planning, external relationships, etc) and leaving 
that to a Nomcom/Recall committee selected using the current criteria of 
in-person attendance, at least for the interim, also appears to make sense.

Creating a second Nomcom to off-load some of the work seems to make even 
more sense given the number of positions that the current Nomcom needs 
to fill each cycle - and it keeps ticking upwards.

WRT to the question of bogus  - ISTM you have to solve the problem of 
bogus people not only for the recall process, but for the selection of 
the Nomcom  at some point if you want to open either to remote 
participation.  It may be time to enumerate the possibilities people 
have discussed so far and just pick one.

I think I agree with Andy that the threat to the recall process is 
pretty minimal under most of the proposals.  There may be a higher 
threat if we want to open the appointment side.

Later, Mike