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

Victor Kuarsingh <victor@jvknet.com> Mon, 13 July 2020 00:54 UTC

Return-Path: <victor@jvknet.com>
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 11DF93A0C06 for <ietf@ietfa.amsl.com>; Sun, 12 Jul 2020 17:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=jvknet-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 RVGTXDb6sYvH for <ietf@ietfa.amsl.com>; Sun, 12 Jul 2020 17:54:24 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 74D243A0C03 for <ietf@ietf.org>; Sun, 12 Jul 2020 17:54:24 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id l2so11404584wmf.0 for <ietf@ietf.org>; Sun, 12 Jul 2020 17:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WDRDBANwn4S1c4bbVi8w4BlVLu76EX9k4HPIOKugMoA=; b=teZNZMpKEg/SdaoUPjOMg0XnDdc/XyQ/j7AQ1GFMEdOTHJLsvEsDlurvDD8Yjr/7To 3Ccd5ylfREDFwWBGY1THy1Z/N9l1eq9lIJ5ibiL8bt1G6tqg8ZwX3rGqsRF7L/4YWjEk +cWwsnxsHN+5+wZn2xS0w7dNVlYOSnKufwyC/CzGC+sBnSDNnokoDmIIgSofJJLJ5365 lFuTnA+3S4McDR395wl/9P9x6yi76jMI9A8UOc7SfBn0YEqaM2FBqoMXxXosDfgiMjBj 6sttc1D9TOv9rPwP3/DTPwLEc4TlFiWz6E6GXTOosBUrh005R601WK57oNQft46eJ1Xz 6SyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WDRDBANwn4S1c4bbVi8w4BlVLu76EX9k4HPIOKugMoA=; b=lY3SG9q1vjezm2XD+O2NUJvrtUSGdZjaawWPRBOSm4KQxyqABA1O3cAdUeTVyfDO8H xfpgYCVuStiumRpVIyjIQOtFi78ikE1X6pttNLGnWfCaBNqHglTzfRpKWZLj//2zjfN/ A4rnL2gbzXwd8FEmiqkfaSw0831qCV8lO/7bmR2RrpjowWzbBdUAmDCZo6/7DWu+ppBW 92duWa6+A/l9EfDXU176OEbVEzdpyFNGM0AIKSezitSnyHh4WQQD84OyhscpTGfT3ePJ PGcAb7KgcLMGoSN+7gcremRHzsWktc/CLOM66pngwLWxUtglFgWml8TYJQMbLtZ/QXfK 3eaA==
X-Gm-Message-State: AOAM531HbKMv7umY9joNENVArUCbq3+P+zfCN+KoQkjtZttET1rcWvm+ Y8NqHHkimBbfvk92W5LC3cV6IO781nWWz9M7M7BvKw==
X-Google-Smtp-Source: ABdhPJwB9b0WtnGwzYlqw6LGrVi/LT3m/fVFSiSSTo7cJtzyqqZuh/FoubUDcqWQHVJftBn+KoSfg35KD+88K6p7QCY=
X-Received: by 2002:a1c:1d46:: with SMTP id d67mr17611108wmd.152.1594601662591; Sun, 12 Jul 2020 17:54:22 -0700 (PDT)
MIME-Version: 1.0
References: <5e24af05-23e6-ef8a-a8e9-44da95d86037@gmail.com> <ADE7C48C-9C38-4B8E-AB9F-BB58DE7B92CC@comcast.net>
In-Reply-To: <ADE7C48C-9C38-4B8E-AB9F-BB58DE7B92CC@comcast.net>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Sun, 12 Jul 2020 20:54:11 -0400
Message-ID: <CAJc3aaMJjYX7qijK3hthtGe_-caJE0=82_JFBNidh9+BGip5oQ@mail.gmail.com>
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
To: Mike StJohns <mstjohns@comcast.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, The IETF List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8491f05aa4821d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s3sRx_8J97fcJWaaFgGVyhVI0R0>
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: Mon, 13 Jul 2020 00:54:26 -0000

All,

My understanding its under review.  Sufficient time for
community discussion and input.

regards,

Victor K

P.S. serving as past chair advisor.

On Sun, Jul 12, 2020 at 7:14 PM Mike StJohns <mstjohns@comcast.net> wrote:

> Hmm.  She’s overdue,  but it’s a weekend so....   Mike
>
> Sent from my iPad
>
> > On Jul 12, 2020, at 17:23, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> >
> > I suggest that at this point, we should wait and see the NomCom chair's
> > response to the challenge. After that, there is a defined dispute
> > resolution procedure if people don't agree with her resolution.
> >
> > Regards
> >   Brian Carpenter
> >
> >> On 13-Jul-20 02:19, Toerless Eckert wrote:
> >> It seems to me as if better RFC text, it could IMHO pick either of the
> >> following two options to amend the text we have now:
> >>
> >> A) removal of Tal - because of re-evaluation of hash-list.
> >> B) removal of Luigi - because of new disclosure about his affiliation.
> >>
> >> To me, B) looks more logical because it maintains a bit more of the
> >> "individual contributor" pretense the IETF claims to have (and directly
> violates
> >> with the max2 rule). Aka: It only eliminates a person for which there
> is a
> >> new disclosure, not a different person.
> >>
> >> Any disucssion between Luigi and NomCom chair to me just looks like an
> >> attempt to decide which one of these two cases would be best match the
> >> intent of the process given how the RFCs are not prescriptive enough.
> >>
> >> Both options i think match Eliots corollary of removal based on
> association.
> >>
> >> The more important corollary from Eliot not well written down either is
> the
> >> non-addition based on association, e.g.: If Luigi would have been
> Huawei initially
> >> and would have left Huawei instead, then that would not raise Tal from
> the max2
> >> eliminations of the initial run.
> >>
> >> Cheers
> >>    Toerless
> >>
> >> P.S.: If there was a new RFC done, you should ask for the rights to use
> the
> >> names Luigi and Tal, otherwise use Alice and Bob ;-))
> >>
> >>> On Sun, Jul 12, 2020 at 01:28:16AM -0700, Rob Sayre wrote:
> >>>> On Sat, Jul 11, 2020 at 11:00 AM Yoav Nir <ynir.ietf@gmail.com>
> wrote:
> >>>
> >>>> Clearly, Luigi requested to be removed because both he and the NomCom
> >>>> chair agreed with an interpretation like mine. If the powers that be
> (which
> >>>> AFAIK is the NomCom chair) decide that this is a wrong
> interpretation, he
> >>>> should at least be allowed to withdraw his resignation which was made
> in
> >>>> error.
> >>>>
> >>>
> >>> I don't agree with your reading of the RFC. But, even if I did, it
> seems
> >>> unwise to do this kind of negotiation. Your reading grants the chair a
> lot
> >>> of discretion, but does not make a case for this particular decision.
> >>> For example, one relevant piece of information might be who the next
> few
> >>> candidates would have been.
> >>>
> >>> It would be a shame to call any of these into question:
> >>>
> >>> - selection of NomCom members
> >>> - the actions of their nominees
> >>> - the IETF itself
> >>>
> >>> If those seem questionable, there is no benefit to publishing an RFC
> over
> >>> an Internet Draft.
> >>>
> >>> thanks,
> >>> Rob
> >>
> >
>
>