IETF Logo Mail Archive

Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107

Ted Lemon <mellon@fugue.com> Mon, 30 March 2020 23:36 UTC

Return-Path: <mellon@fugue.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 B61823A15C2 for <eligibility-discuss@ietfa.amsl.com>; Mon, 30 Mar 2020 16:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=fugue-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 1jWio5qMpXJJ for <eligibility-discuss@ietfa.amsl.com>; Mon, 30 Mar 2020 16:36:02 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 581C83A15C1 for <eligibility-discuss@ietf.org>; Mon, 30 Mar 2020 16:36:01 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id j4so21119009qkc.11 for <eligibility-discuss@ietf.org>; Mon, 30 Mar 2020 16:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=1KEFhvI1WKdsSOv0cQUaFMoyLrfVIdpuDszNGxSbwI4=; b=DgwOqLnWxu5aJWt/cb66ND3eA9qNW1MBO818gvgjhRJGTT/dSnR+cRIlrBdFjXoSsl M0c/C48WvIKLHhLjqDuL6Ob8i5P1wk+gw2tJjQDuFnIk45ctn6CVYU1LaoIZnG270L8+ QNcSH9RGuJK7w1ImLn5PfRnCs673zzLUco+q1Q0zqdhkRYDO0+bjI6ptxOtQ8+5FRhdK HnepO22e3MEcoDYxAeZHorEdj3B2a3cgKwjLjvVPbajReJVo8kjqJWGnRkvoSCSDHf3M NUq0AP3uGP+/bXSADlQ1Vfpcn+1guu7hwLRLmhj3Z9Kl52C398DQAP2RutiHsKHMzlqD bIYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=1KEFhvI1WKdsSOv0cQUaFMoyLrfVIdpuDszNGxSbwI4=; b=dzMcfYMO+d3Hbne1sTdBlYQuk9ekw1sjkZmRhoDaJ540hndInHkyXfVJ5jp/S5I/5A Igm4BbfrTC+vJeYuGVOTxj2nprnDigLV2usDYhgKXJGxUjm2BtICrpOUF6mS9fo1vj1O nHodDRpStWoPHprOdYKs6yl7j+GlDNqBItiBkC0zIpHHZRpEE88wYWlJbpM6AXc+u7k4 F8xc2uZ0hZP2dSt5Pbc8oWLLkBBPHx0ORDSbz+SIwchcnXzrw5+7VXrURQwbb88kgY9h Aw6QIN1YdZMvRJ3ZCFFb/ZmlLDW7GBTgdpBBMZtRa96ImW1TRe0xDS4H8BI8g2YSNDXB CvQA==
X-Gm-Message-State: ANhLgQ3FYTkSBrhIeNzFx/jOkLUkwWYeMKJ6/q3pU/rUWLpQOakimTky +sUVHvpXdp9y90JBL+B1xLJvJg==
X-Google-Smtp-Source: ADFU+vu/xxyu8/+EvNhverRwEuD+B8ZYdPS9hosBSporlVyyJfeE5RI8QNZ0kJOZ9cofffzmVVpjaw==
X-Received: by 2002:a37:4ec1:: with SMTP id c184mr1759735qkb.0.1585611360340; Mon, 30 Mar 2020 16:36:00 -0700 (PDT)
Received: from penumbra.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id s4sm12651623qte.36.2020.03.30.16.35.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2020 16:35:59 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <1EF64084-5B11-4E37-9304-98377E5F09D9@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E8825F6-5582-49E2-9E0B-1527B30725B6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 30 Mar 2020 19:35:56 -0400
In-Reply-To: <CAJc3aaNs2DipcSAdddB1PayPSFN+zRPDwyKog_LhjTu4B95afg@mail.gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, eligibility-discuss@ietf.org
To: Victor Kuarsingh <victor@jvknet.com>
References: <28433.1585520758@localhost> <CAJc3aaNs2DipcSAdddB1PayPSFN+zRPDwyKog_LhjTu4B95afg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/W86gQCiV1wExpuE9KJri3dwvapQ>
Subject: Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107
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: Mon, 30 Mar 2020 23:36:10 -0000

On Mar 30, 2020, at 7:10 PM, Victor Kuarsingh <victor@jvknet.com> wrote:
> I was just thinking that we keep it as simple as possible for now to seat this Nomcom and give ourselves more time to then make more substantive changes to the eligibility.  Making other changes (large or small), are likely to have unintended impacts so I think trying to avoid that may be best (IMO).

I agree.  This is not ideal, but we’re opening a really big can of worms, and while I think we should be expeditious about it, trying to rush it done for the 2020 nomcom seems too rushed.

v2.23.0 | Report a Bug | By Email