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

Bron Gondwana <brong@fastmailteam.com> Thu, 10 September 2020 11:47 UTC

Return-Path: <brong@fastmailteam.com>
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 67CAF3A092E for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 04:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=fastmailteam.com header.b=w9RzkzRm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MnDR6EhW
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 SoAb0dedyPKS for <eligibility-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 04:47:02 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F6EF3A0933 for <eligibility-discuss@ietf.org>; Thu, 10 Sep 2020 04:47:02 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 38907A8B; Thu, 10 Sep 2020 07:47:01 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Thu, 10 Sep 2020 07:47:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm3; bh=/xxd VFGsKNbJaoUqEsmbSmcd+j/YLJBU7bBzuGSxPz0=; b=w9RzkzRmI79bLR8BtmJd T0oZXHrbzP36SlWZ5JFlTiHl8NziOuXdhxKehFoxrIUpCh9/Pdv3fa/Cfbjo/Pwv IiGZsNCGYCCPgA3YbcmSYUJl7k7TioHGo9MQA/sGHtxq0qkXpIpB4E8V2rxPG1hA YOkmuOn9pLwzPxIcWIWiAHcNLHM14/CFvU9i7HXd0uUrwCWSpeMZWA4nUsB5KE0+ CnCCezmqtt3T+NAynh9l7QJJVIUraTOWrfRFNCUIpzMRxOGniJfgJVG9nADWqtAu an8Hak1L/riq76LJJdpTxKh/fAZ5XQdbfQFW7Yn23BuJrrARw6GWst/RmIK8LwHV Jw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=/xxdVF GsKNbJaoUqEsmbSmcd+j/YLJBU7bBzuGSxPz0=; b=MnDR6EhWuHodVe1VvsrRKL Jb3eE4ROmDrJUaSBC6twn0YmBBwfZf/DgPgchjAbd3Ed/aUWQkV1Zpr9D4CpHQGF XbOXa1qI7GajxhcUbkvggMHmOOd6dLDt2B0Rv3WiX8FU/7D+M0VRHwgJA06/qZdz 05lZXkNIJ7kYEke9oX5v10YFbYjE5pwl8K2lsuTx0aYQX2Axy7xuU2FnLdAo+yKn 3CILpI9kn6AmrpyhUmAN46WaKprH/BaXMtrAvf8ZXPfyRuBQKfXO5SZSfuxQMUiF jxO/zBQa6/TKyq+Ps7F/nJV+SmMpKcdAX4rlxdwol2rJum9I4ATAa1Ni01mItOZw ==
X-ME-Sender: <xms:NBJaX8umpqlVVYLmkGI6ISdkcsnYRBSKGLMruWUXFKGTT2WMBN2Psw> <xme:NBJaX5eC6Qry8jKMmoBZ_trtRNeCX8rT_xAhndVUuH8PpADzchW4X7_Rvbhbx4rlR zxwK6sfXlw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudehjedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnheptdehteegfeevteduffevteehfffghefhvdevkeeuhfeh ueetudehgfegieekjeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:NBJaX3ycVL0oPosuscbbw_6IJcsp1fDSDfwtgodKm8MpF_Un9x0D_A> <xmx:NBJaX_N00bDBkECKkRXFqaexkFQlTM0AL90vLkZlW4kq59ah27pRiQ> <xmx:NBJaX8_hiD4GDFxL1_m7ghq80ZPfkpjv7K0D15looj0FIzwLlyJEUA> <xmx:NBJaX6kLGdKG-BL4E326USgUwUwAxQ8wcUeNsGH45-EFMvPOrUN0_w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E826318028C; Thu, 10 Sep 2020 07:46:59 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-259-g88fbbfa-fm-20200903.003-g88fbbfa3
Mime-Version: 1.0
Message-Id: <5bffbc36-9368-4498-80f4-88ecd3ea6697@dogfood.fastmail.com>
In-Reply-To: <07cf01d68765$44d1dfe0$ce759fa0$@olddog.co.uk>
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>
Date: Thu, 10 Sep 2020 21:46:38 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: Adrian Farrel <adrian@olddog.co.uk>, Eric Rescorla <ekr@rtfm.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>
Cc: eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="8f0e1b8e0e924406a264b349d3128d8c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/5oVrCtE7v7CLCjwvLkPRNFoO1yg>
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:47:03 -0000

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> 
> *Sent:* 10 September 2020 12:12
> *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

>  

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

>> Hi Eric,

>>  

>>>  

>>> Bron Gondwana <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

>  

>  


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com