Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev

John C Klensin <john-ietf@jck.com> Sun, 26 May 2019 17:40 UTC

Return-Path: <john-ietf@jck.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 582F51200B1 for <eligibility-discuss@ietfa.amsl.com>; Sun, 26 May 2019 10:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, URIBL_BLOCKED=0.001] autolearn=no 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 QoW6or3t0sOf for <eligibility-discuss@ietfa.amsl.com>; Sun, 26 May 2019 10:40:21 -0700 (PDT)
Received: from bsa3.jck.com (unknown [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 252421200A4 for <eligibility-discuss@ietf.org>; Sun, 26 May 2019 10:40:21 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hUx83-000MAc-DW; Sun, 26 May 2019 13:40:15 -0400
Date: Sun, 26 May 2019 13:40:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, "'Eliot Lear (elear)'" <elear@cisco.com>
cc: eligibility-discuss@ietf.org
Message-ID: <27C342782110704662033130@JcK-HP5.jck.com>
In-Reply-To: <067701d513bd$c1bec7b0$453c5710$@olddog.co.uk>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <FDDEFD82-E276-4874-896E-490397EDA735@akamai.com>, <6.2.5.6.2.20190525151934.0c0099e0@elandnews.com> <7D195412-2A8E-44FC-9144-B7C48F33EE5C@cisco.com>, <067001d513ad$09739f60$1c5ade20$@olddog.co.uk> <1F0265EE-0686-4DF7-9A74-93F6D6C8CA47@cisco.com> <067701d513bd$c1bec7b0$453c5710$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/roQTIvd5eqiQ6ZDGH3y4j1AcKMo>
Subject: Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev
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: Sun, 26 May 2019 17:40:22 -0000


--On Sunday, 26 May, 2019 13:22 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> I did once start to put together a recall petition for an AD
> (so long ago that we need not dwell on the details). I found
> that collecting cosignatories was slow, but for good reasons.
> People generally said "Yes, bad stuff is happening, but recall
> is pretty serious. Can we think about other ways of handling
> this?". And, indeed, once the seriousness got discussed a bit,
> the AD concerned modified their behaviour (coincidence is not
> causation).
>...

And that, IMO, is one of the reasons we have disagreements about
whether the recall mechanism "works".  While I wish I was more
confident that it could be carried all the way to its conclusion
of removing people if necessary -- and doing so in less than
nine months or a year -- there is a very real sense in which, if
starting the process results, even coincidentally, in an adjust
of behavior behavior in more positive directions (good) or a
resignation (less good but still effective), it is doing its
job.   That does not make the perception of fairness and
accessibility to all active IETF participants any less
important; indeed it may make it more important.

  john