Re: NomCom eligibility & IETF 107

Bob Hinden <bob.hinden@gmail.com> Thu, 26 March 2020 15:44 UTC

Return-Path: <bob.hinden@gmail.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 2FAA53A09F1 for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 08:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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=gmail.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 1Es53SSoT0Ro for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 08:44:05 -0700 (PDT)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 AAA733A09D4 for <ietf@ietf.org>; Thu, 26 Mar 2020 08:44:05 -0700 (PDT)
Received: by mail-wr1-x433.google.com with SMTP id p10so8384692wrt.6 for <ietf@ietf.org>; Thu, 26 Mar 2020 08:44:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Y3PHCw8jZeRp92l4EKEKfdpXGPdkX8mOeL8+Q+FxcHU=; b=BjuDF1JM0ygjBK8m1NGOL9o+qE0/3ZtN7iYkudT+vhgOCjMt6KpJgolXjKTNMtxOQP RiZYrMbDi/kogsCg4yYQSn082nDn93Sua4tk9ZPEST8l4cvWLjAv5zl0V7cPRI2lcZJ3 3LEDJ7McTHtv8R9TusPS87gXTqonzUE4J92fvgObJAOf7rpZxHJg5tvHWpbTqU/+MNCN 9UdYqu6xgoBwQgxGlr4drg6dG36W+IvhvHuvrvtyAmzHrWRih3czp9zRsj5qa/K2Vtaf tZdc3n4viLl5JeBo4SbHhvLJ4ZmuhkJpsGElaTYJ0G2SDHhyW87l6r2h4RzyqodwqUK0 5FCQ==
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=Y3PHCw8jZeRp92l4EKEKfdpXGPdkX8mOeL8+Q+FxcHU=; b=jtMO3h162UWVgIVVLjv+7E2LWYouy2ltoyZqfze8t7cXYMV5DZXsOlxeedM2qj3aqc zh+kuJK60d4KpK48Jf0aXYmlgDeiNp23CnLMbbiqGWpOsgK5v7w/UoDIY+qtwQPhfyV2 yRLxSokPNK0PLMMtwJMm/LDf0VucSBzkyFHi1VaUY0mVMkVPJsO0Kv6tiL5ocntDiZl+ fznJDpdIVZ79wcCLyT0Bwf7I1qAZQJJKECDy6qI/UedLiJEd75+HJTguVt9+hFwdZqIs icTjmbN7IjJUDUMj0v0HQ1XFCPCLmpGTzYDl++3KOi2bJnqpHgeXKrwXABSmyWmkKFI1 kCmQ==
X-Gm-Message-State: ANhLgQ09LbNvclk9Er9Z/S5c9eEEr94Z7YehFzd87s6cBBr4VuHhITwV 9pLbHdgSV2CsS0nHudRT0A4=
X-Google-Smtp-Source: ADFU+vtbmB6KoFfZjU2AW7zAGf6HmnksDvy91gZiETA/yHT5pm/Mzqd9uT0h2xq2PL6mBVpVdjLtEQ==
X-Received: by 2002:a5d:53c8:: with SMTP id a8mr9786516wrw.242.1585237444044; Thu, 26 Mar 2020 08:44:04 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:d181:7507:3422:d369? ([2601:647:5a00:ef0b:d181:7507:3422:d369]) by smtp.gmail.com with ESMTPSA id i19sm4113467wmb.44.2020.03.26.08.44.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Mar 2020 08:44:03 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <F0A062BC-56D9-4875-911D-964F0B3673A0@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_12DA5DC3-9872-45DF-935A-3F82224FCB2D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Re: NomCom eligibility & IETF 107
Date: Thu, 26 Mar 2020 08:43:59 -0700
In-Reply-To: <1UW64HHr2j.1YlDGqDnLsi@pc8xp>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Barry Leiba <barryleiba@computer.org>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com> <1UW64HHr2j.1YlDGqDnLsi@pc8xp>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8wl-05Z42ZIlDDjy_0fLebGv0D4>
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: Thu, 26 Mar 2020 15:44:08 -0000


> On Mar 26, 2020, at 3:26 AM, tom petch <daedulus@btconnect.com> wrote:
> 
> Barry
> 
> Ignore 107 entirely; treat 102 to 106 as the qualifying meetings.

At this point, I agree with this approach.  I though differently early, but that was before I saw the limited agenda for IETF 107.   Except for the plenary, the sessions that were scheduled didn’t overlap with my interests very much.

We will need to be prepared if IETF 108 isn’t face to face, but we have some time to work that out.

Bob


> 
> Going forward, if 108 is cancelled, then we should consider virtual qualification but that is for a future discussion.  107 has had too many uncertainties and changes on the part of all parties to be considered.
> 
> Tom Petch
> 
> 
> 
> 
> 
> ----- Original Message -----
> From: Barry Leiba <barryleiba@computer.org>
> Sent: 25/03/2020 23:14:00
> 
> 
> ---
> New Outlook Express and Windows Live Mail replacement - get it here:
> https://www.oeclassic.com/
> 
> ________________________________________________________________________________
> 
> If you haven't already weighed in on this, please post your comment
> here, in this thread on <ietf@ietf.org>rg>, by 30 April 2020.
> 
> Thanks,
> Barry, for the IESG
> 
> On Fri, Mar 13, 2020 at 9:44 AM Barry Leiba <barryleiba@computer.org> wrote:
>> 
>> 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
>> 
>