NomCom eligibility & IETF 107

Barry Leiba <> Fri, 13 March 2020 13:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BD8923A073D for <>; Fri, 13 Mar 2020 06:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.112
X-Spam-Status: No, score=-3.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-1.463, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LGh1R2WCLX0F for <>; Fri, 13 Mar 2020 06:43:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 93B643A05E2 for <>; Fri, 13 Mar 2020 06:43:47 -0700 (PDT)
Received: by with SMTP id w15so1581668ilq.6 for <>; Fri, 13 Mar 2020 06:43:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=IEirWMklyyEziW2nkPxpzmSVhm0YDzek8c3aQAtYAvU=; b=rHI5Fu2hDfwfKq/ArrXEsWM7V8M/UpMmh74LbzxT9SWNk4I0bgpFjNQGb/1VAQBzt/ 0zG3VKddJjdMCyaQBUkyg6Ljf4/9yLh+QFlwkQRo2ucCd2oJLGhIDvQvJHdrALv7VbPV +RLI4PxOrNx+dvFMl48xjEFkb42Mq5gkjxUASbWbqAaIUNAxai2VtPYbYzVYOvlAUv+5 jXFdg8GyKjI4v64pwbv87LtetdGdEPCdPhcxe0RTQndprJDz2vBZ08Pu7vErA4jyZ0Nb jD+TzO/wq6a9yWlpsT4b1ExsRqob6lVoE9rHXJgmhrR9hXl+Qj/q8x7rhyHKADJy6tAN Jl3Q==
X-Gm-Message-State: ANhLgQ2ydEroX6jbOLx1mnOH7z31ojTy0+AomrLYRnejgnwrVk2G/1WA Jy+3kn21s6VQ2B+jykPSYZty+MRfm8KvGAHDvmJOwsZh
X-Google-Smtp-Source: =?utf-8?q?ADFU+vsx8usxEAuhBkfo6aNLiT5WUYsDhDalgp5ijLNu?= =?utf-8?q?7zUJTkOEllxbYHfUgnuBYuiL7Ic/IuDAZXeeLW6B+wFFlzQ=3D?=
X-Received: by 2002:a92:8f4b:: with SMTP id j72mr13280341ild.17.1584107026441; Fri, 13 Mar 2020 06:43:46 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <>
Date: Fri, 13 Mar 2020 09:43:34 -0400
Message-ID: <>
Subject: NomCom eligibility & IETF 107
To: IETF discussion list <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Mar 2020 13:43:49 -0000

The cancellation of the in-person IETF 107 meeting raises the issue of
how that meeting affects NomCom (Nominating Committee) eligibility.
This is especially important because a new NomCom will be formed
between now and IETF 108, giving us all a fairly short time to figure
out what to do.

For convenient reference, the current rules for an IETF participant to
be eligible to be a voting member of a NomCom (Section 4.14 of RFC
8713) require attendance in person at three of the last five meetings.
Normally, for the upcoming NomCom, that would mean three of the
following five meetings: 107 (Vancouver), 106 (Singapore), 105
(Montréal), 104 (Prague), 103 (Bangkok). A new participant who had
been to 105 and 106 would become eligible by attending 107.  An
occasional participant who had been to 103 and 105 would also become
eligible by attending 107. On the other side, someone who had attended
102, 104, and 105 would lose eligibility by NOT attending 107.

The IESG would like the community’s input: How do *you* think 107
should be treated in regards to NomCom eligibility?  While we have
time to come up with a longer-term answer for this as a general
matter, we need to make a one-time decision about how to handle 107
now, before this year’s NomCom is formed.

One choice is to entirely ignore 107 for the purposes of NomCom
eligibility.  The last five meetings would then be 106, 105, 104, 103,
and 102, and one would have had to attend three of those to be
eligible this year.

Another choice is to consider 107 to be a meeting that everyone has
attended, for the purpose of NomCom eligibility.  There, the last five
would still be 107 to 103, but 107 would be an automatic “yes” for
anyone who volunteers for the NomCom.

Perhaps there are other workable options.  Please let us know what you
think by responding to this message thread.  And to be absolutely
clear: whatever we, as a community, decide now, with fairly short lead
time, is for the 2020-2021 NomCom cycle only.  Any longer-term
decisions might be different and will need to be done through a more
formal, consensus-based process, which we also hope to initiate in the
near future.

Thanks in advance for the discussion we’re sure to have on this.

Barry, for the IESG