Re: NomCom eligibility & IETF 107

Victor Kuarsingh <victor@jvknet.com> Tue, 31 March 2020 21:13 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 7DE313A060D for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 14:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 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, URIBL_BLOCKED=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 lsEV3jtygdPB for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 14:13:44 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 C984B3A060A for <ietf@ietf.org>; Tue, 31 Mar 2020 14:13:43 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id j17so27842269wru.13 for <ietf@ietf.org>; Tue, 31 Mar 2020 14:13:43 -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=VngHPcahep/kuXaBXn6umquksoLXuxLP4/quiKjHEQc=; b=w0v4PF2JSkZsANa+8j0ljgT2KcKCxN3rV43sGSbit35EiBBQ/K6B/x4oXJrignZUnd JfRwwaI6xUwSej/TEGKIWSOfanmTsA51ih5ZBSYZiVMN22WDybqT+kYwLdPwSW2PpcYA ieQWQqLVOh2384XxgnNNKME7dLwT8bOEnorZC7fmU0OHk+4IEBTsGgoscQlNatuCkeSu oHpbfRf3p4zHXwpfOPvan82Y32Z7tDiPR4nlVSa30uAa8qH4ssFiZK+r5LFigcEdeSmh cZReAk7ywKv3fX7uzm1GUzTq75sXhVqlpPbkGnO1wN/1nFfOq+SYA4CFq8VU1yIR4r8x G8eQ==
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=VngHPcahep/kuXaBXn6umquksoLXuxLP4/quiKjHEQc=; b=fVB5yEM6KciJNaHEHQRtHjBLfZsQc6zsN8wnUDKxLy5NEOmzQipK0kQ02qXuDBvW+O Snntk/TKBsRg0z8TCPUCPnxsukRxSyGQMm0EETa7IkrgpVlP4RCjqV0So7hDhVHHdJ5/ EYKhkPWCanR3DcGA0Ot7GRxERDTLC7oxT5s9vtNxbvyWOWsGl+UoBkELZ9LXZPf75QIE RhQ6kLZy8oMxJ5cNv8lLb6zcM++V74OMs9HxCOYr/0pJg/alpkm0VGEuSgYDJp33RMWE W8O3hjBocwbtv4OIssp+rHo40hXmlSgcj5NYbK2m7KPCvnUDyAMKeXsVjC6ertqR9yE5 okrw==
X-Gm-Message-State: ANhLgQ2nqltfi2rmovbmHW6HXRk4RymU3kpQHdS+s5VuG7fLU37zW9Ee rArbc8hn9ndlfKjTdS7fquD2qXw0F2oCDMWfAexgzQ==
X-Google-Smtp-Source: ADFU+vv+Au3yoddAS8CQz9eYU7DnIlNR0f6IkSKHSSwot9xfRBfTFqLGMoxDadsdtOjtyFCkAwAZsr0ZGNC7Sl7+xJ8=
X-Received: by 2002:adf:f50d:: with SMTP id q13mr23005158wro.374.1585689221939; Tue, 31 Mar 2020 14:13:41 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com> <CAC4RtVCzMPGuunYZBCSh90ddY2kKJ_Hqnot0s1jmhNQ7qT0xkg@mail.gmail.com> <89730DD8-0451-4658-A0CD-83A85E2055FE@episteme.net> <0C31D020-46FA-424E-8FFD-64BBE8F952E9@cooperw.in> <1E702B62-9982-48F2-B8D6-F4F80A8DE168@episteme.net> <20200331184236.GT18021@localhost> <CALaySJ+_+-kf+3nta8LwMiwPmqPmRdOgC7KAnDfeDgx0ThVa-w@mail.gmail.com> <CALaySJ+27gcT6x5BcKU1YHHv+xeaXDnxPU0yhtBSULb36VpFWA@mail.gmail.com>
In-Reply-To: <CALaySJ+27gcT6x5BcKU1YHHv+xeaXDnxPU0yhtBSULb36VpFWA@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Tue, 31 Mar 2020 17:13:31 -0400
Message-ID: <CAJc3aaMzqxiDdFR_1q6Lcj0ivQDcz3tEtLH0zzVHm=xBWuAu_Q@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cc5aaf05a22d0a03"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/atLqaNrFJ90n0lnPu-CPoVUYl2U>
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: Tue, 31 Mar 2020 21:13:46 -0000

On Tue, Mar 31, 2020 at 3:37 PM Barry Leiba <barryleiba@computer.org> wrote:

> While we are sorting this out, and whether we publish an Internet
> draft or not, I would like to know this:
>
> As I (Barry, not the IESG as a whole) currently read the rough
> consensus, considering what people have said the reasons you all have
> given, and the discussion of those reasons, I see things falling
> toward option 1.  Specifically, looking at RFC 8713, Section 4.14, FOR
> THIS NOMCOM CYCLE ONLY and SETTING NO PRECEDENT, I would replace the
> first two paragraphs this way:
>
>    Members of the IETF community must have attended at least three of
>    the last five in-person IETF meetings in order to volunteer.
>
>    The five meetings are the five most recent in-person meetings that
>    ended prior to the date on which the solicitation for NomCom
>    volunteers was submitted for distribution to the IETF community.
>    For the 2020-2021 Nominating Committee those five meetings are
>    IETFs 102, 103, 104, 105, and 106.
>
> The question I will ask is this: Is there anyone who *can't live with
> that outcome*?
>

Yes, I can live with this outcome.  It allows the organization to get down
to business and keeps the intent of the documented process sufficient
enough (under the circumstances).

regards,

Victor K


>