Re: Corrected announcement of NomCom members

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 09 August 2022 15:02 UTC

Return-Path: <sarikaya2012@gmail.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 40724C13C51D for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2022 08:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.754
X-Spam-Level:
X-Spam-Status: No, score=-1.754 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 XsljvfAh-9UY for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2022 08:02:57 -0700 (PDT)
Received: from mail-vk1-xa36.google.com (mail-vk1-xa36.google.com [IPv6:2607:f8b0:4864:20::a36]) (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 945D3C13C50D for <ietf@ietf.org>; Tue, 9 Aug 2022 08:02:57 -0700 (PDT)
Received: by mail-vk1-xa36.google.com with SMTP id j11so1168510vkk.11 for <ietf@ietf.org>; Tue, 09 Aug 2022 08:02:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc; bh=ZxwycayV2rI2mYLvH08yv5mwauvlFfAGQJ4XQQCb0Vg=; b=fxh8OhWP/S1IRK1tSh5cqnnN8lsBuByIkoNE6GuGFb8PAdn2FFFwYDdMhROrWxVmKs +S5tH77wo4SpcfV0Vu71AEixtFumdWAa60YbM5V/VQ5LZjK2OLzxB7VQoZbQNfOrJ5pu L8hRR03RKmxVLEUAoK0IMID1cUIlslJENdE3nQqM0FShTGq/+tYeAgim87ktV4lyynq7 20vV2qGqxx5ZC++QNvLeukuiC1HPNztvCg38MhNvvSxKcb89oM0PqJXAlyH4WPDgavTX JtziTro9ufukFaceqaadiy1Td5l58D7Rc61etIqWq/zVHi/9hYpC7YkI3q/nDXLeZOp1 a8Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=ZxwycayV2rI2mYLvH08yv5mwauvlFfAGQJ4XQQCb0Vg=; b=jbPw4DYESrr0WNgRevLJ7eLphLVIDaAHs6fzpSQQ5C4Yd+VmeNpQVYOVTckTm1HwNp wG+bOsfdcIQuPYZABEz9yDrT8eiJW0K+n6c0XYjxzpzFJcY7glgIv/mqWT2o5n4dGJyr GRALxusvhF4Z7YSuxH7SnuwKSsBK97yySAL63uOsfNEcIzkqAMcc/fRCIC9Ir1kIdNrK RU3aEZvBINqOP+caFs+Wm0H96VhLNTu/L+hDHl0c8g2YQYQX5YM2vk1dxI60enbfr6L7 1ALzYPNKFlQj1dB/DcR2g4wY0mzd/HrDs8xQm/5budGFsh/908C1YGDtDV3iHEIdSb2L J83A==
X-Gm-Message-State: ACgBeo2w0DWH3JtGVFkygg/x3pN89/wbAiredk/KViQbVq6JJVtCePLJ 9Sx65LKqYN8cyEuUbr1qJv6RFTHatu2MTQqi41Tin+5A7+c=
X-Google-Smtp-Source: AA6agR6cf2kqyhTfWfAURBIQBBhA7KCo/DfQodoIE/qwEOW4Q/gSGJb6/Mw73x6tJXWM5l5AgYejfJD8GYVtQskJH6s=
X-Received: by 2002:ac5:c92d:0:b0:377:37fb:945b with SMTP id u13-20020ac5c92d000000b0037737fb945bmr9851960vkl.30.1660057374752; Tue, 09 Aug 2022 08:02:54 -0700 (PDT)
MIME-Version: 1.0
References: <166000188302.4870.13324057713844585930@ietfa.amsl.com> <CA+9kkMCA2V9ipDop0kBynk=_spuKyf7WNPyht9VUYgB85aK1Dw@mail.gmail.com> <452D0C6E-A937-4FE6-B10E-2BEA2AC291DA@akamai.com>
In-Reply-To: <452D0C6E-A937-4FE6-B10E-2BEA2AC291DA@akamai.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 09 Aug 2022 10:02:43 -0500
Message-ID: <CAC8QAcdsYKmRa3OUh0y_HihVyvsEen1uJSO3CFDOJ0F=TX64mw@mail.gmail.com>
Subject: Re: Corrected announcement of NomCom members
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002103cb05e5d03a62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eN5N4mVSb7EJX0zcqc0s-iDqS9s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 09 Aug 2022 15:02:58 -0000

On Tue, Aug 9, 2022 at 9:59 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>
wrote:

>
>    - The list posted here: https://datatracker.ietf.org/nomcom/ann/504888/
>    <https://urldefense.com/v3/__https:/datatracker.ietf.org/nomcom/ann/504888/__;!!GjvTz_vk!U7yR-PTGDDPOBngkMqkdv3HOt-Z9irtQPeRVrvTJYDuAM4uQ37hQgUxAiQwtJmz1zGiwtd134ymvLg$>
>    contains both Barry Leiba and Victor Kuarsingh, both of whom are ineligible
>    because they serve on the ISOC Board of Trustees at the moment.  I believe
>    you were notified of both prior to the running of the algorithm, during the
>    challenge period.  Barry followed up with a question on this on August 8th:
>
>
>
> I had thought that this was considered resolved after multiple threads in
> the ietf@ mailing list. This thread, among others.
>
>
> https://mailarchive.ietf.org/arch/msg/ietf/S5W5hjCpld2ZSmUsjhM96p5cDNY/
>
> But it probably deserves a summary, here.
>
>
>
> RFC 3797 (quoted by Kyle) says
>
>
>
> > >    The best way to handle this is to maintain the announced schedule,
>
> > >    INCLUDE in the published pool all those whose eligibility is
>
> > >    uncertain and to keep the published pool list numbering IMMUTABLE
>
> > >    after its publication.  If someone in the pool is later selected by
>
> > >    the algorithm and random input but it has been determined they are
>
> > >    ineligible, they can be skipped and the algorithm run further to
> make
>
> > >    an additional selection.
>
>
>
> I had said the only thing I considered normative from 8713 was the
> algorithm. Others, including Mary Barnes, explained that this was wrong; I
> retracted that and agreed that the right thing is to follow the quoted
> paragraph above.
>
>
>
> I was wrong to use a list that was modified after I posted the final. It
> was my mistake to not notice and remove various Board members until after
> the July 25 posting. But the process has mechanisms to handle that and that
> is what I (belatedly) followed.
>


Seems to be not a good start. I wish a very very happy end. 👍🏻

Behcet

>
>
> Hope this addresses the concern.
>
>
>
> -Rich Salz, 2022 NomCom chair.
>
>
>