Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-05.txt

Adrian Farrel <adrian@olddog.co.uk> Thu, 10 September 2020 10:12 UTC

Return-Path: <adrian@olddog.co.uk>
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 C29433A1245 for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 03:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 W-XpOIl9JJR3 for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 03:12:55 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 BE1003A119B for <eligibility-discuss@ietf.org>; Thu, 10 Sep 2020 03:12:54 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 08AACmrT020666; Thu, 10 Sep 2020 11:12:48 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0AE7A22088; Thu, 10 Sep 2020 11:12:36 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id F365E22087; Thu, 10 Sep 2020 11:12:35 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.221.249]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 08AACYWA027363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Sep 2020 11:12:34 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eric Rescorla' <ekr@rtfm.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>
Cc: 'Bron Gondwana' <brong@fastmailteam.com>, eligibility-discuss@ietf.org
References: <159962318959.19375.6649774205472330786@ietfa.amsl.com> <943d5d03-9605-35c7-2a3b-3cc9a48ff0e1@gmail.com> <e2afeee6-f5db-4cd1-8371-b163e01a6931@dogfood.fastmail.com> <29455.1599663931@localhost> <CABcZeBMywwqPDSg9wgEGYOdG55d+E8dKYrELasV8meOiXBAFkA@mail.gmail.com>
In-Reply-To: <CABcZeBMywwqPDSg9wgEGYOdG55d+E8dKYrELasV8meOiXBAFkA@mail.gmail.com>
Date: Thu, 10 Sep 2020 11:12:33 +0100
Organization: Old Dog Consulting
Message-ID: <07ad01d6875a$e70c07a0$b52416e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07AE_01D68763.48D10BE0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLI8QTNySoNiBPZlRgVGYG7V8otrwIt7KXmAmuhkfQCHb+fbwGa2BNWpzo6pBA=
Content-Language: en-gb
X-Originating-IP: 87.112.221.249
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25656.006
X-TM-AS-Result: No--17.738-10.0-31-10
X-imss-scan-details: No--17.738-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25656.006
X-TMASE-Result: 10--17.737700-10.000000
X-TMASE-MatchedRID: gTucSmrmRMNor4mPA3EMtnFPUrVDm6jto6VTlZ7piRZPQiQvzFiGeN4D i+9UB8nLXw8SDK+AsGncU2HgCa5JjeVsdeNpdvi/vmT2VURehlpMhH/KpYxyu1hs8uimgHNCGba NfEO4jWNmEHHqgNu8LWuJr35VFPwvJrk+tkFzAHCqNnzrkU+2mlOBrtD2w1fp2dP9ypSe+fcEtA N4XKvn46B2Jk8cTgr+3A0Bu17t9z2/zyJyZLmRNgQZkZUveGbboPqXw+FolM4EDOJQflFm+3ERb S7OZpEDUmdx8640hiXiHC2pMqCwC++ItmrT5nY2KUnZzo2UQD3MKpTwtwWkPr1Xhhq8rF/j2zMl MhmuHAjGPYP6kM1IwumdIFGMTlHtAZskQh6hLX0K4MBRf7I7pgH9Qt+fIXSvP0x3XXd/NekWahW L740rrg9TQMwVAjQIQ3uyYiQUJddHW+94FA8JF8K1Ib9JAALxrogFtKd/P7cLBZEuqIL9SpO9mQ Gx4jC3Sa7i4WMGYwF/2SsgU8jyNW7vEKjEI8LygNylVbI/EAyoCf7IdvPAJzAx/HIgP92dNEZZm AO2JUg/+RSNQ9LGXvws7nAqLxhScejanjZWHJiL6bUMM+bbIlzWPAcG6DFAwEXirjns+34SkGdm Qt+XWfJ0c/jxNrWl3NClAvtxoSNhyMOhUPZ7ng6w00GeWBFafS0Ip2eEHnyvXSmSdlcYmrLn+0V m71Lcz7345D1T/l8gBwKKRHe+r0q928Qiz2oOFXI/GdjsNbGYpG2kLgwKu5qRHsBA5CuTPf7u1e o9eaY=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/vgHwEu9WsT9Uv_uApQz81b7XMds>
Subject: Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-05.txt
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: Thu, 10 Sep 2020 10:12:57 -0000

Hi Eric,

 

Bron Gondwana <brong@fastmailteam.com <mailto:brong@fastmailteam.com> > wrote:
    > 1) we should not include remote participants for IETF106 and earlier.
    > They did not have an expectation of eligibility.  I hold this very
    > weakly and would be easily persuaded to change my mind!

I was going to post the same thing.

    > 2) we should include remote participants for IETF110 (and any future
    > IETFs if this document is renewed) regardless of whether there is a
    > face-to-face component.

I can live with this, but I believe that this is what the other paths are for.
to be clear: I don't think that we should count remote attendees when there
is a face-to-face meeting.

 

I agree with Michael. The reason we are making this adjustment is because we are not having in-person meetings. If we have in-person meetings again, we can of course decide to include remote people, but that's not a decision we should take now.

 

[AF] Well, I guess I disagree with Michael once, and you twice.

 

I am fine with not including remote attendees at previous in-person meetings, but we have to handle future meetings.

 

The question about counting remote attendees when there is a face-to-face meeting is significantly about enfranchisement and also about the future direction of the IETF. It is, IMHO, a very important question to consider if the IETF is to continue to claim to be an open and accessible body.

 

Whether *this* document needs to consider in-person meetings depends on whether there is any prospect of there being an in-person meeting during the period of this experiment. I think this remains possible (if unlikely). It is certain that if there is an in-person meeting in the near future, attendance will be significantly limited – many people will not be allowed to travel depending on governmental rules, company policies, and insurance limitations; others will not want to travel for their own safety. In that case, we will have a distinctly partial face-to-face meeting and we have to decide (now) how those who don’t attend in person will be treated.

 

Since this experiment is of limited duration and the number of people who might be included by this measure is small, I wonder what the risks are that predicate against including them?

 

Thanks,

Adrian