Re: NomCom eligibility & IETF 107

Barry Leiba <> Tue, 31 March 2020 04:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 702433A1A7E for <>; Mon, 30 Mar 2020 21:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.255
X-Spam-Status: No, score=0.255 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tv3cblK3Fu8Z for <>; Mon, 30 Mar 2020 21:25:48 -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 AEB903A0995 for <>; Mon, 30 Mar 2020 21:25:47 -0700 (PDT)
Received: by with SMTP id l23so20705663otf.3 for <>; Mon, 30 Mar 2020 21:25:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dbx3impDeBcpA8I3ENnYrK+7NFvfQdAV5+8ddBJPByc=; b=PD8vBPYEyHzlCdJYJyofZlmTGfGwYqxcnH9PF2WJixTGAyfiYztkJRbsHL7IDp7F5P 9Yy+RTnlQGeAt+ycwNv2jT9/EoWaRwSjSBRvIg3amLuDmfgkZPyhlgIohME5elEtMouw 7b5N1S4LbCXO3bWtMvWr9xtlWh0yNcrLwMxii+Wcu25+RWT5vm2+5jfIShvWqiDR/maF DT7ddBrlEGC8UMuRes/y4GbiC7aHhF63CYg4NBkii9MI2BtZ53MqHSqK1BuBJo5h4ldr vco0YCBNLRwTeB98ltBaC0GNSDmqDKLUsiRt9TGEWEdmI1DUldF/X5azgztKMq/RMBKI CTAw==
X-Gm-Message-State: ANhLgQ3jIkQDtAtV6yVJQ3S03FCzUwm8/IEwZcq8OfcwHd0Z76lM/w2B 6RG+Ycp22qe1zyzLoze14OrI6OQyfGeW3er4/jv35Q==
X-Google-Smtp-Source: ADFU+vvm+SvB+TS9rosepD8uCV1OE+35C2Yf8qhA8eU2GS1j/tZjy2LLTmQZTWv//wB1tCdOeoNsbleUeLw4bC0Oq9k=
X-Received: by 2002:a4a:b91a:: with SMTP id x26mr1794368ooo.2.1585628746550; Mon, 30 Mar 2020 21:25:46 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Barry Leiba <>
Date: Tue, 31 Mar 2020 00:25:35 -0400
Message-ID: <>
Subject: Re: NomCom eligibility & IETF 107
To: IETF discussion list <>
Content-Type: multipart/alternative; boundary="0000000000002f12a305a21ef62b"
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: Tue, 31 Mar 2020 04:25:49 -0000

The IESG has discussed what the best way is to handle a decision for
eligibility for the 2020/21 NomCom, given the timeframe involved and the
discussions that are already happening.

1. We are concerned that a normal process for discussing a draft,
conducting a last call, and approving a BCP would take too long.

2. We are concerned that rushing such a process by, for example, posting a
draft now and immediately last-calling it without a normal period of
discussion would call into question the legitimacy of our consensus process
and would set a bad precedent.  We also note that have already stated that
we’d like community comments by 30 April, and we are concerned about
cutting that time short in order to write such a draft.

4. We believe the IESG does have — and must have — the latitude to address
exceptional situations such as this and to make exceptions to our
processes.  At the same time, we appreciate and agree with concerns about
overstepping, and we agree that maintaining accountability and appropriate
checks and balances is important.

The IESG, therefore, plans to continue collecting input and evaluating the
community’s rough consensus about the immediate NomCom-eligibility question
through 30 April, as stated.  We will then post a statement and inform the
ISOC Board of Trustees, as we would do with a process BCP.  That statement
will serve as the basis for eligibility to serve on this year’s NomCom, and
this year’s only; it will NOT remain in effect beyond that brief timeframe,
and will make that aspect clear.

If rough consensus of the community is that it is important for the IESG’s
decision to be published as a BCP, we will do so, handling that after the
immediate need for a quick decision has passed and making the publication
for archival purposes.

We also encourage the community to continue and complete the two efforts
that have been started, to formally define an exception process, and to
update NomCom eligibility requirements to account for virtual meetings and
for remote participation.

Barry, for the IESG