draft-moonesamy-recall-rev-01: Number of Signatures Required

Mark Nottingham <mnot@mnot.net> Mon, 22 April 2019 02:20 UTC

Return-Path: <mnot@mnot.net>
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 2BCBD1200FE for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2019 19:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=oBd94No/; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GzE+Q9Mb
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 PDFltGhYF0XS for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2019 19:19:57 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF77A120090 for <ietf@ietf.org>; Sun, 21 Apr 2019 19:19:56 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B34782073F; Sun, 21 Apr 2019 22:19:55 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 21 Apr 2019 22:19:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm2; bh=TQ+/u2MRLUXHf0TllbdsRkZuqAY90v QRfVE87tBXyFg=; b=oBd94No/EbFAMCHDEg5LQ4HctGsIMVCAGf3d5uWO4LMQQA 67Fdr7v8or7i/bJ8OgE5h6iQjZER2NPPqPWqZEwJsZVLjyrT06WwsWeYwPs3ed+G 4GvO2iXOUS19UiFce2Um+lezmZbBhZc6I5WqddoYhLs6WEkCaQ2KPjmp1/Dc6JfH vpxCAOJGlvGk1mu+O+WCi6epctSHCO2ITBD4xKmm4jBGD1bcasxB7fnh7GqGmdPo H/2JKz1llSzH/ClI9XqNNC7d4x9M5j1x3zRFKOsuzDM9LPhsPmiCrnT+Dx6CZCwY fatdEDfFsS4BcdedrSWi/qfJP/IqIRF17Hwl20wA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=TQ+/u2 MRLUXHf0TllbdsRkZuqAY90vQRfVE87tBXyFg=; b=GzE+Q9Mb9Bh+yEM1vthvcN mjzpP6/svcsfMx4rPPwpV01ZAJ5rWZnWMReEFdnn3RQWKPJxqTfUXw7PrKS9l6ZT NGmkkCA2TiN5MSUUp7NiE7ajqZDx5ER3GgOGolsjpSDjHDAvGr0z4MDRfG4r0+SD cCrdM3QBd6inxELFE10ST0DKw81V/x6ubuiYiOcGEV9witGUsy3rmUS0IH3gTSIG GravYA5HEozOyIXUSBEAIcCmHJN0zflzWE4ff7t5/idTMpQEMezcr2alQbnpJU3r +Nc6w7uSY7QbMVfyEoDiry/J/NB1Up1P/lWNliAPqxQr/otbjp2YYnxJq3LsPsmg ==
X-ME-Sender: <xms:ySS9XJM2xXl9IkNnYVDU9tOCLvb8A4yoGBqerVR9zCS1nfY4y9ivEA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeehgdehhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffkfffvofesthhqmhdthh dtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohht rdhnvghtqeenucffohhmrghinhepfihikhhiphgvughirgdrohhrghdpmhhnohhtrdhnvg htnecukfhppedugeegrddufeeirddujeehrddvkeenucfrrghrrghmpehmrghilhhfrhho mhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:ySS9XB5wdE4taK7eU9VgH-XZRd6x8WgqKNBJ-bRJn23QgyPR6REseQ> <xmx:ySS9XFZQZMm-R7aWPvYEVdn9YksFkU8wtdQPCfIiU1RzOaz9osN7iQ> <xmx:ySS9XGeDFRzsn4APcou7JWieV9WTodAfgAtpcQWdcE5yX8TOpEXSQw> <xmx:yyS9XP65LR3fxqtuQ3KOeDITnm_Ls5d8LdaJQby-RF4rWUH6gZaCNg>
Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id D8DB3103CB; Sun, 21 Apr 2019 22:19:52 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: draft-moonesamy-recall-rev-01: Number of Signatures Required
Message-Id: <272737C2-FCF6-48CE-AB8C-B9FEBEE1E965@mnot.net>
Date: Mon, 22 Apr 2019 12:19:49 +1000
Cc: S Moonesamy <sm+ietf@elandsys.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HXTsPNBfJ4PUFUgwJKh723BHpA8>
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: Mon, 22 Apr 2019 02:20:00 -0000

Hi SM,

Without going into the other aspects of this draft (I'm watching with interest), Section 2.3 caught my eye:

>    [RFC7437] requires at least 20 signatories for a recall petition with
>    no more than two of the signatories having the same primary
>    affiliation.  That sets a very high barrier for a recall petition
>    even though the recall petition requires a, justification, an
>    investigation by a Recall Committee and a 3/4 majority of the members
>    of the Recall Committee who vote on the recall decision.  This
>    document also proposes to decrease the number of signatures required
>    to avoid making it impractical to invoke the first step of the recall
>    procedures.

Sorry if I missed a previous discussion, but this strikes me as an interesting change to couple to a proposed increase in the number of people eligible to sign a recall petition.

Given that the number of people who attend IETF meetings -- both physically and remotely -- varies quite a bit, and since we now can track the size of both populations, I'd expect this number to be expressed as a percentage of the total eligible population (however the above discussion goes).

Looking at the attendance of the last five IETFs*, it appears that about 777 people are nomcom eligible, so it would currently take a bit more than 2.5% of that community to initiate a recall. 

If remote participation is also counted, about 1083 would currently be qualified; your proposed 10 signatories is 0.92% of that community.

What's the right number**? I'm not sure, but I'll make a few observations.

It seems to me that the number of signatories required helps to ensure that the recall represents a significant portion of the community, so as not to waste the noncom's time. I also see it as a way to manage secondary effects; e.g., so that people aren't dissuaded from putting their hands up for nomcom, lest they be committing to a series of frivolous recall efforts. 

More importantly, perhaps, I think we also need to ask ourselves whether we want our leadership concerned about the possibility of a recall -- even if a failed one -- from a small, determined set of people. I imagine there are upsides and downsides to that.

To me, allowing 1% of the community to initiate such an action seems like a really low bar for disruption, not at all a "very high barrier". Looking elsewhere:
  * Various Swiss cantons seem to run between 2% and 13% of the electorate <https://en.wikipedia.org/wiki/Recall_election#Switzerland>
  *  In the UK, it takes 10% <https://en.wikipedia.org/wiki/Recall_of_MPs_Act_2015>

Cheers,


* This is estimated by scraping the attendance tables for the last five IETFs, removing affiliation (since it might change) but keeping country (less likely to change, but still possible), case-normalising and doing some command line sorting and filtering. No doubt mistakes were made (if anything, these numbers are probably low, thanks to false negatives), and I'm sure this isn't how the actual eligibility is determined. But it's good enough for estimating, I think.

** I really do think it should be a percentage.

--
Mark Nottingham   https://www.mnot.net/