Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 25 October 2019 14:17 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 DB959120123 for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 07:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 mDK56pd6v5fz for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 07:17:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20E16120105 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 07:17:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7E1873897D; Fri, 25 Oct 2019 10:14:54 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8FAC9723; Fri, 25 Oct 2019 10:17:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: adrian@olddog.co.uk
cc: eligibility-discuss@ietf.org
In-Reply-To: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk>
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 25 Oct 2019 10:17:31 -0400
Message-ID: <14501.1572013051@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/k_zCSKtYb44MDVbqKwb2JpAsnw8>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
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: Fri, 25 Oct 2019 14:17:36 -0000

Adrian Farrel <adrian@olddog.co.uk> wrote:
    > Something that is not in draft-moonesamy-recall-rev but which I floated
    > before, was that the list of signatures should not be exclusively remote
    > participants. That is, the petitioners would need to persuade some physical
    > participants to co-sign.

    > You might note, we already apply this today, but the threshold is 100%
    > physical participants.

    > I think that would help mitigate the risk of any attack.

I agree.

    > I'd also note that the draft doesn't just allow any old remote participant,
    > but still requires the 3-of-5 threshold. That means that anyone wanting to
    > DoS has to spend at least eight months preparing.

I am unclear if SM's recall draft enfranchises all remote participants are
nomcom eligible, or if it just does that for recall motions.  I agree that
the attack surface is not that big.

    > And I would like to contrast this with the enfranchisement issue which is
    > that two fifths of our meeting attendees are now remote. That means that the
    > IETF is (as it has always billed itself) an organisation where the work is
    > done on the mailing lists and through Internet-Drafts. Hooray for that!

!

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-