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

Adrian Farrel <adrian@olddog.co.uk> Thu, 10 September 2020 11:52 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 50EBA3A093B for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 04:52:09 -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_H3=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 ErSD8RcbnGGy for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 04:52:07 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 D50A83A0936 for <eligibility-discuss@ietf.org>; Thu, 10 Sep 2020 04:52:06 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 08ABq1Z0015718; Thu, 10 Sep 2020 12:52:01 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C7A972205A; Thu, 10 Sep 2020 12:51:47 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id BB52C22099; Thu, 10 Sep 2020 12:51:47 +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 08ABpk0Q026600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Sep 2020 12:51:47 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Bron Gondwana' <brong@fastmailteam.com>, 'Eric Rescorla' <ekr@rtfm.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>
Cc: 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> <07ad01d6875a$e70c07a0$b52416e0$@olddog.co.uk> <a149053f-dcde-4c7c-87d8-ebe86102ef44@www.fastmail.com> <07cf01d68765$44d1dfe0$ce759fa0$@olddog.co.uk> <5bffbc36-9368-4498-80f4-88ecd3ea6697@dogfood.fastmail.com>
In-Reply-To: <5bffbc36-9368-4498-80f4-88ecd3ea6697@dogfood.fastmail.com>
Date: Thu, 10 Sep 2020 12:51:45 +0100
Organization: Old Dog Consulting
Message-ID: <07e901d68768$c2a7be50$47f73af0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07EA_01D68771.246D10B0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLI8QTNySoNiBPZlRgVGYG7V8otrwIt7KXmAmuhkfQCHb+fbwGa2BNWAl+PhjMCEFP8XgJVDL3iAiyibhCm8tFvYA==
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.007
X-TM-AS-Result: No--12.633-10.0-31-10
X-imss-scan-details: No--12.633-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25656.007
X-TMASE-Result: 10--12.632500-10.000000
X-TMASE-MatchedRID: CxmI61mtwh9or4mPA3EMtnFPUrVDm6jt1z5/X1vqH0AEJn46HBWx+7V9 bZkwbW7J7+U2XZtk9iqnVOsT1h4vuM8hZTuRtNznsgYw1+LBrk25lj6HVxsd71HpIy6wt5UweE6 H4OmdJb5ZNxHEotMe1nWSmqejMBT2/Qyesqk4CKDwpAypldoLOVBijjE0XjY+T0IkL8xYhnitks CIxuVJEXTYwH5n5oGwMCqdq5v8pqzH9nl5elRSFMVbb3pjW5MnW6IdALvH8VORlpMKVczGVPh5g T8kXkoMgJvVWlJ+UT/BLsjt3re8zpxjBzzEqmFV3zen1b+Th8p6vXCVWhHpNE+86maMM3aS3gOL 71QHyctfDxIMr4CwacOnGqjuv48yxW7Ez38LY1zZulfZck3CoeDTYjejIZTwI0YrtQLsSUzclay GYv+Tv2KAODW34ckfN2OwxNFDk7u36bWU2xVUiu5b8GtgkaX9Af1C358hdK95Q7d9a8+idKyAQb vPfXXm+yjUpUnSRKAblhF5SURqFuRsO3/KQYNmcZj4H1CyNUxwSovBIzQ2lHlZu+awgqiN5PZKE 4fa/Jc22uoEm245flgUFTT7Y9QpYTZ2mX+nxwwItCy6ZX/lL4IWSprjdsebHCP6WbPscS8wfkn2 bVbTj4vfSJuNTN/rxWGby5Hg6eAsS7de5tK9ATE06wHA1+f+AcGk+q40InQXM2Z1UyweuKkWS6g saJykjSiAYevD2gFBRSIMqj3Vp/fIaGUVYG+VGUubsVz8TemoaP5jEFB0mMO/l0Ny5PZ5GoO5M/ YEX3dVFFwXIlKBAT7ES0yB0QCIvBkFvcgSMyKeAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyLr8uVzX avvgwaIkv313qJp4kYXbobxJbLLLrRfL5Fh4SsvYXEHM/OUJ+qBes3jyqF4KcJ4dzx6fPF1pvRJ a7w7BYyf9r98Q3yo3Zhb1ZEiJyWuh0Hig8c4OaZfJGzTi19kUQgbD1mBjA==
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/ZmWTn98TtBRfaTcMq4SuroobnZo>
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 11:52:09 -0000

OK. I understand the concern, but I cannot believe it is a mainstream worry.

 

A

 

From: Bron Gondwana <brong@fastmailteam.com> 
Sent: 10 September 2020 12:47
To: Adrian Farrel <adrian@olddog.co.uk>; Eric Rescorla <ekr@rtfm.com>; 'Michael Richardson' <mcr+ietf@sandelman.ca>
Cc: eligibility-discuss@ietf.org
Subject: Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-05.txt

 

I believe the theory is that multiple "identities" would resolve down to one "actor" when selected, who would then show up in person and press their party line.  It's quite a complex process, but it does appear to be the only way that one would branch-stack this process.  And of course, you'd have to find someone willing to play the part of a false identity.


Bron.

 

On Thu, Sep 10, 2020, at 21:26, Adrian Farrel wrote:

Hi Bron,

 

Thanks for your proposal (which has, I think, been on the table for a while). I would accept it.

 

Should we have a separate thread about the whole sock-puppet thing? Or shall we deal with it here?

You are suggesting that people might establish false Datatracker accounts, register to attend remotely, pay for or apply for a bursary for attendance for three out of five meetings, put their names forward to be on NomCom, get selected, and then what? Will the sock-puppet show up to NomCom calls and meetings?

 

Best,

Adrian

 

From: Bron Gondwana <brong@fastmailteam.com <mailto:brong@fastmailteam.com> > 
Sent: 10 September 2020 12:12
To: Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> >; Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com> >; 'Michael Richardson' <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca> >
Cc: eligibility-discuss@ietf.org <mailto:eligibility-discuss@ietf.org> 
Subject: Re: [Eligibility-discuss] Fwd: I-D Action: draft-carpenter-eligibility-expand-05.txt

 

On Thu, Sep 10, 2020, at 20:12, Adrian Farrel wrote:

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. 

 

Can I propose the following:

 

Remote attendance will be included for IETF110 regardless of whether there is an in-person meeting, as we don't expect that everyone will be able to travel.

 

Changing the treatment of meetings after IETF110 is not done by this document - we need to publish a new document anyway in order to extend this experiment, and that new document could choose whatever treatment it likes.

 

So - this means that ONLY IETF109 and IETF110 could be sockpuppetted, and that's not enough for eligibility by itself.

 

Cheers,


Bron.

 

 

--

  Bron Gondwana, CEO, Fastmail Pty Ltd

  brong@fastmailteam.com <mailto:brong@fastmailteam.com> 

 

 

 

--

  Bron Gondwana, CEO, Fastmail Pty Ltd

  brong@fastmailteam.com <mailto:brong@fastmailteam.com>