Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process

Benjamin Kaduk <kaduk@mit.edu> Sat, 11 July 2020 03:04 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63AC83A0CEB for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 20:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MjsZjO14s2hq for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 20:04:28 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A31E03A0CEA for <ietf@ietf.org>; Fri, 10 Jul 2020 20:04:28 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 06B34JfQ015651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 10 Jul 2020 23:04:21 -0400
Date: Fri, 10 Jul 2020 20:04:18 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Toerless Eckert <tte@cs.fau.de>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
Message-ID: <20200711030418.GN16335@kduck.mit.edu>
References: <159422819660.27889.6475902734358747001@ietfa.amsl.com> <b4f5a3cf-5fab-8188-926a-a4100f776610@comcast.net> <1112046E-04ED-4DB1-8766-4928AC5D15F5@akamai.com> <20200711002800.GC49328@faui48f.informatik.uni-erlangen.de> <17D66D97-9F29-470C-83CA-53C48F49D323@strayalpha.com> <20200711011915.GE49328@faui48f.informatik.uni-erlangen.de> <20200711012801.GE16335@kduck.mit.edu> <20200711021620.GF49328@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20200711021620.GF49328@faui48f.informatik.uni-erlangen.de>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RZTmO_UY6A3tzWYYAnRYEHoAwbE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jul 2020 03:04:30 -0000

On Sat, Jul 11, 2020 at 04:16:20AM +0200, Toerless Eckert wrote:
> On Fri, Jul 10, 2020 at 06:28:01PM -0700, Benjamin Kaduk wrote:
> > > On which planet did this happen ?
> > > How do you come to interpret what happened in that way ?
> > > Luigi declined to serve. Thats all.
> > 
> > I'm not sure that we actually have enough information to say that.
> > https://mailarchive.ietf.org/arch/msg/ietf/o8p6rh9boOs65QTTIpBb73t-fV4/
> > says "has informed [the Nomcom chair] his affiliation has recently
> > changed".  That's not exactly "has said he cannot serve", and doesn't say
> > anything about when the affiliation changed with respect to the timeline of
> > the Nomcom selection process.  Is there other information available that
> > I'm missing (n.b. I'm quite behind on IETF mail at the moment)?
> 
> Sure, but yada yada yada -> he decided that he did not want to serve.

I still don't see that as the only possibly conclusion possible from the
available data.  I see a difference between "he concluded that he could not
comply with the rules and still serve" and "he decided that he did not want
to serve".

> Aka: How is all the justification how he arrived at that decision relevant ?
> 
> And even if the reasons where relevant, for which i can not find
> any evidence in the relevant RFCs, then i can't see how this woud
> have changed the outcome.
> 
> And even if he would have decided that he did want to serve, it
> would have been up to NomCom chair to decide (my reading of the RFC),
> and but i can't seriously not think of how a NomCom chair would have
> kicked out anyone else (from that company) than the person newly announcing
> the affiliation.

My understanding is that we do not know that it's about anyone's specific
with (other than to comply with the BCPs, I guess).  It might be, but it
might just be about complying with the BCPs.  Specifically, Section 4.17 of
RFC 7437 makes a prohibition regarding "volunteers with the same primary
affiliation may be selected".  I read that as saying that the "selection"
occurs when the randomness is finalized and the 3797 algorithm run, and
thus that the relevant affiliation is the primary affiliation at that time.
If the affiliation at that time is disclosed after that time, then we are
into the Section 5.1 of 3797 case that you mention below.

-Ben


> The argument made on the list is to violate section 5.1 of rfc3793 AFAIK.
> 
> Cheers
>    Toerless