Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-06.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 23 October 2020 02:18 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 BBB713A0C93 for <eligibility-discuss@ietfa.amsl.com>; Thu, 22 Oct 2020 19:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 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.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIoWDZoCqle9 for <eligibility-discuss@ietfa.amsl.com>; Thu, 22 Oct 2020 19:18:09 -0700 (PDT)
Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) (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 DE9123A0B2D for <eligibility-discuss@ietf.org>; Thu, 22 Oct 2020 19:18:09 -0700 (PDT)
Received: by mail-pl1-x644.google.com with SMTP id r10so65603plx.3 for <eligibility-discuss@ietf.org>; Thu, 22 Oct 2020 19:18:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9FvY+F5YyJaijO4mDdKWIAJuLkwN7jOjAfHUUh/XkSA=; b=IxPXkqqBsULwYoCR/99Vbnr8gJl5p6JwL4729wx4I91D5rua0yKSebD+lZLHiyASub O10mwQgCeLxiia5a/oJ1kjAV6qe2Eijlel/O0Wu5WTHTFFo2f6QTi9P+z5kvdWIF4Cfi UXGHAJDXZhVLbF0jsiCQcPFfIW3Uw3MrhZ3IAkzvRzKWZXVEYqyJwq+Eg9xy9Vms1h1+ GLfHI623hvbCsRVhQIKG/U1xzWv5VmLFFXnpgyYrBrtzWKzcf5CYh6M+q//0+Qo08mGr UazGbCr5BfJ1NLfluXqlfNy0x9M/XTIAESUJB51otimRktVOK1yY/JYOCW0XatKW5BIK Agow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9FvY+F5YyJaijO4mDdKWIAJuLkwN7jOjAfHUUh/XkSA=; b=ORysii5Ty6ZuP+BL62U57K6I1cbrxh8HhD/gb+QJ+hgiozPc+hv5pPog5Mgi1Ge84v B68dmTONRGyDeYYbGrSQK+dw62gmJP7QO/7sgIJKdDkQd2jSqTABkTZa7X6OO65udX5R nZCKqOPPdRp/W9iUdXrdOOIpq5mwG12+/d04ot3lblP5px3z3chQps4Syriaw9N0wV6e Q+uEAemOef4u82Q+zCZXh5xydX9HSeDnDMAYOc7O9tshnXVRLVp2xx4iJ6WHOK4PEY6k OgzxElefn2zhSIuONFu2tAP/mN6xL1PZIKxF3vTamRQ+zSf45Y091JToZiKO/SgV2oCq N+GQ==
X-Gm-Message-State: AOAM531ZBZ+yYvhez0mmFXeuFqY0tbACuVKYr3RxqMq/a6mrc3cLxJ2+ WL1AeR2O2D2JbbPFUs009ngfnnfk4b+3yg==
X-Google-Smtp-Source: ABdhPJxzDEPfGCoSLSWYHJ9ttsO+GBJPZdoYrlXhZCNEf6q6GW8MkbywNv4dHsXfE+4IRIfCWSaWIw==
X-Received: by 2002:a17:902:8c88:b029:d5:ffe1:6653 with SMTP id t8-20020a1709028c88b02900d5ffe16653mr320506plo.22.1603419488642; Thu, 22 Oct 2020 19:18:08 -0700 (PDT)
Received: from [10.2.2.9] ([103.23.18.158]) by smtp.gmail.com with ESMTPSA id m4sm3493685pgv.87.2020.10.22.19.18.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Oct 2020 19:18:07 -0700 (PDT)
To: Victor Kuarsingh <victor@jvknet.com>
Cc: eligibility-discuss@ietf.org
References: <160264449870.15606.11390985094452603984@ietfa.amsl.com> <57021c3c-1dc7-c2bb-6800-32dfd2ddd15d@gmail.com> <CAJc3aaO=d33JQvTmKs=uzcqKBx5BHt5yLZ0==cX5gZ4czUpf2g@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <90f7459e-0742-79d2-4902-0bdb71c6869c@gmail.com>
Date: Fri, 23 Oct 2020 15:18:05 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAJc3aaO=d33JQvTmKs=uzcqKBx5BHt5yLZ0==cX5gZ4czUpf2g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/UB0auduZiOTQNKgnwoJ7NdK3saw>
Subject: Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-06.txt
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: Fri, 23 Oct 2020 02:18:12 -0000

Hi Victor,

Thanks for reading the draft carefully. Comments in line.

On 23-Oct-20 02:50, Victor Kuarsingh wrote:
> Brian et al,
> 
> I had been a bit absent from the discussion so my input here may have been already considered but I will make the point anyway.  I note this with my Nomcom Chair and previous voting member hat on.
> 
> I realize path 3 is vector that can be mechanically evaluated, and my be agreed to by the list/group.  However, my concerns are: 
> (1) it can result in people being allowed into the pool which are unfamiliar with IETF community members whom are nominees for the positions

Have we any assurance that remote attendance doesn't lead to the same problem? Or to reverse the argument, our most important interactions are by email, since consensus decisions are based on email, and therefore knowledge of individuals via email is arguably *more* important than face-to-face observation.

I'd also observe that this is a one or two year experiment, so if the results are bad they will not persist.

> (2) listed as an author can include folks who may not have had any participation in the IETF at all (just listed)

That shouldn't happen, of course, but I agree it could happen. However, under the present system, and especially with remote meetings, registration and participation can be bogus too (i.e. just listed).

> Both of these issues (related to each other) can make it difficult for that person to participate in an adequate way with respect to the following duties 
> - Driving / contributing the questionnaire 
> - Driving / contributing to interview questions 
> - Conducting interviews (where adaptive questions may be needed for evaluation)
> - Participating in the active discussion where nominee attributes abilities and group/body needs are discuss (with adequate context) 

Yes, all of that could happen, but I assume that in a NomCom of ten people, having one or two such members would be unpleasant but survivable.

> 
> Item (2) above can also be used as a vector to introduce people into the Nomcom whom are not primarily focused on the IETF work, but seeking selection in the Nomcom itself (not for the test period since its likely too late for that), but if adopted over time.   One can say this is true for path 1, but the bar is much higher given the need to actually attend (in-person or remotely) which exposes folks in some cases to outside working group activities (increasing familiarity with people, roles, and teams). 

Well, speaking only for myself, I don't think the bar is higher. I'm not saying there are never passengers in RFC author lists, but I don't think it's endemic. And similarly, we certainly have passengers at meetings, but again it's not endemic.
 
> Although not every member of the Nomcom body is familiar with all rules and/or nominees, but by extending the pool too far (far == folks likely to be less familiar with the people, teams, groups, work), we can add risk that there can be some areas represented by enough (or anybody) on the Nomcom body outside of Liaisons and advisors.  If this is the result, the Chair may need to work harder to provide context, drive questions, promote adequate discussion which then, in my opinion, puts too much onus on the chair (and causes potentially natural bias)

That's true, but again...
 
> However, I do think the experiment is a good approach to the challenge we face.

... we have to try *something*, I think.

Regards,
    Brian


> 
> regards,
> 
> Victor K
> 
> 
> 
> 
> 
> 
> 
> On Tue, Oct 13, 2020 at 11:18 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     Hi,
> 
>     This version has been updated (with advice from Bron) according to what we've understood of the discussions since the previous version, plus today's news:
> 
>     * Allowed for IETF 110 decision
>     * Resolved open issue (see the previous point)
>     * Removed "future work" section (as suggested on the list)
>     * Editorial improvements
> 
>         Brian + Stephen
> 
>     -------- Forwarded Message --------
>     Subject: I-D Action: draft-carpenter-eligibility-expand-06.txt
>     Date: Tue, 13 Oct 2020 20:01:38 -0700
>     From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>     Reply-To: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>     To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
> 
> 
>     A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>             Title           : Additional Criteria for Nominating Committee Eligibility
>             Authors         : Brian E. Carpenter
>                               Stephen Farrell
>             Filename        : draft-carpenter-eligibility-expand-06.txt
>             Pages           : 8
>             Date            : 2020-10-13
> 
>     Abstract:
>        This document defines a process experiment under RFC 3933 that
>        temporarily updates the criteria for qualifying volunteers to
>        participate in the IETF Nominating Committee.  It therefore also
>        updates the criteria for qualifying signatories to a community recall
>        petition.  The purpose is to make the criteria more flexible in view
>        of increasing remote participation in the IETF and a reduction in
>        face-to-face meetings.  The experiment is of fixed duration and will
>        apply to one, or at most two, Nominating Committee cycles.  This
>        document temporarily varies the rules in RFC 8713.
> 
> 
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-carpenter-eligibility-expand/
> 
>     There is also an HTML version available at:
>     https://www.ietf.org/archive/id/draft-carpenter-eligibility-expand-06.html
> 
>     A diff from the previous version is available at:
>     https://www.ietf.org/rfcdiff?url2=draft-carpenter-eligibility-expand-06
> 
> 
>     Please note that it may take a couple of minutes from the time of submission
>     until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org>.
> 
>     Internet-Drafts are also available by anonymous FTP at:
>     ftp://ftp.ietf.org/internet-drafts/
> 
> 
>     _______________________________________________
>     I-D-Announce mailing list
>     I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
>     https://www.ietf.org/mailman/listinfo/i-d-announce
>     Internet-Draft directories: http://www.ietf.org/shadow.html
>     or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
>     -- 
>     Eligibility-discuss mailing list
>     Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
>     https://www.ietf.org/mailman/listinfo/eligibility-discuss
>