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

John C Klensin <john-ietf@jck.com> Tue, 11 June 2019 15:41 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 0017012018B for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 cLCU89F6PfHW for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:41:14 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E146F120157 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 08:41:13 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1haitZ-000DKm-4P; Tue, 11 Jun 2019 11:41:09 -0400
Date: Tue, 11 Jun 2019 11:41:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Eric Rescorla <ekr@rtfm.com>
cc: S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org
Message-ID: <987121D4908D32C98579FEE8@PSB>
In-Reply-To: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
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
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/EKfou1ygw6a25tTrCBZ5vPeGQmc>
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: Tue, 11 Jun 2019 15:41:16 -0000


--On Tuesday, June 11, 2019 14:21 +0200 Eliot Lear
<lear@cisco.com> wrote:

> 
> 
>> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>> 
>> H/mm..  These don't seem like "issues" so much as
>> restatements of the solution SM's draft proposes.
>> 
>> To take a specific one, what issue is addressed by reducing
>> the number of people required to sign the petition?
> 
> Fewer people would have to set themselves up as targets for
> retribution; the pool of people able to serve on the recall
> committee is marginally increased.

And, like the remote participants measure, if makes recall
initiation marginally more plausible, especially for remote
participants.

Thanks for mentioning the fear of retribution issue.  I've seen
it several times when people have felt unable to post negative
Last Call comments about documents in which one or more ADs are
involved as authors or by having significant skin in the game.
I had not considered it in the case of recall initiation, but it
is obviously going to be a concern.

It seems to me that, if a high level statement is needed, it
would be something like:

	"During the years since the Recall petitioning procedure
	was changed, with RFC 3777 in June 2004, to require
	Nomcom eligibility and 20 signatures it has become
	fairly clear that it is unusable in practice for any
	case that is not so completely obvious that a complex,
	time-consuming, multi-step, procedure should not be
	required.   It has also become progressively more unfair
	as the requirements exclude potential petitioners who
	are likely to be more knowledgeable than typical IETF
	f2f participants about particular types of abuses,
	whether because of the position those people hold or
	because as significant fraction of their participation
	is not f2f at IETF meetings.  It is also more burdensome
	for the latter group of participants than for those who
	are Nomcom-eligible under the normal rules, which is
	another source of unfairness.  The BoF is expected to
	address three specific aspects of those issues: the
	Nomcom eligibility requirement of physical meeting
	attendance, the number of signatures required on a
	petition, and the ineligibility of Nomcom-appointed
	members of leadership bodies to initiate petitions."

I remain concerned about broad statements opening up discussions
of the entire recall model (more about that in a note I have
written but hope I don't have to send), but perhaps something
like the above would respond to the need that others seem to be
feeling without significantly opening that door.

 best,
   john