Re: NomCom eligibility & IETF 107

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 13 March 2020 15:47 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 3CF303A0BB7 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 08:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level:
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.274, MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 nh_wVWS-Z0Od for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 08:47:20 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 289EF3A0B9A for <ietf@ietf.org>; Fri, 13 Mar 2020 08:47:18 -0700 (PDT)
Received: from [10.32.60.84] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged)) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 02DFkglb083083 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Mar 2020 08:46:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged) claimed to be [10.32.60.84]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Barry Leiba" <barryleiba@computer.org>
Cc: "IETF discussion list" <ietf@ietf.org>
Subject: Re: NomCom eligibility & IETF 107
Date: Fri, 13 Mar 2020 08:47:13 -0700
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <BA0278B4-7BCE-473C-B92A-662FD91172C3@vpnc.org>
In-Reply-To: <CALaySJJVhrY2YdzW4T1-51Lm-3VxKpzdu2=Hq+9Gdc0vVbi=aA@mail.gmail.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <E6FB26B505C8B7952BB81CEA@PSB> <CALaySJJVhrY2YdzW4T1-51Lm-3VxKpzdu2=Hq+9Gdc0vVbi=aA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jyA7_A9475N3ahSbROQlrmbT9yk>
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: Fri, 13 Mar 2020 15:47:22 -0000

Describing some of these requirements to potential NomCom members is 
going to cause confusion. Thus, it is probably better to not have to 
describe them at all. Simply skip IETF 107 in the eligibility 
calculation.

--Paul Hoffmam