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

Eric Rescorla <ekr@rtfm.com> Tue, 11 June 2019 12:32 UTC

Return-Path: <ekr@rtfm.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 CD7D9120154 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 JF0d-NEyWudz for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:32:24 -0700 (PDT)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1A65120043 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:32:23 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id y17so9174895lfe.0 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zj0p/gTLZPWDb0lhf0XP+9gDlo/L9v3EbZnROuxNJwo=; b=XLNK8AimvB2lwzb5WsSvY9QTnpH/p/arhcP6ESi79fHSvg6fYDG2WuTBEJtvN7dFQy 7S7Y2gP6kTFfvGsAe/DDpfkuhFRBqf4fNQ4I2ksAt0PSYpLyf5uXqn7dMGH52bK+a8Mf WA9j3UCfskaq+PikgONUAjhHo1MQzNwaHuQRxEVZNBMnBc0ZSQc1SpGM4GFJMsK8zI+/ yUS8148xbELNSZW64Rx3K2kkjvxy2PSX2Qmam+tdCnsEZPIdZZ0iSEM+mFk3ivVRFcAp Cr9ZY/XS4RFBqGDYnl3nSx1QwS1NykR8bqWmZN6UFVMFLOok+OoR/reGLwXnWIvl5MW/ dF6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Zj0p/gTLZPWDb0lhf0XP+9gDlo/L9v3EbZnROuxNJwo=; b=HHzBHxqXXcWEr2GEQPteEClMXbkLlSEYW/PmYwwYHh00t5YLAjXjR+EaivpWAYsvmG YXy19TnXvIcyyzXkhKnQ8pTVNLB1wJHT9iReUx2IO5DcoQIlu3Oes85lFL5OcwtZhuGe L8uw7jcNbxrGMJIN9f7nBX81Iigftf8f2pFJyYWr+pTbYpv4Y074zFTTU/3+SyaO6ecG +ikmnBaIIpOp1rFxWZrc9084mY58lkrCVnbVmVHMjpw+rAQugU5s6Nuzja3Zx0XfQ26q F/zrz8XcD7khg8qKMSk58eU/AUDmli7Cm1fWQB3mgfhGQlGbNwtYgB7QfYBaLozwOuWh L6IA==
X-Gm-Message-State: APjAAAUK6avFj7N6YfzS8U7zYKohYLcOqMzi75xs+jchhRxcY9k+ZQcz 6xKX2ocbNpvn2E6IFA+Ji3RaDOea5QIPjcmf/QqsMA==
X-Google-Smtp-Source: APXvYqwoGfcPDdhfz/5AXE4rKywbM6CNRFM/GvN/7s5Am7PGh04aC+n+FQLXccqgIePhj20FKvn9N2tsCtZYPZ0MQB8=
X-Received: by 2002:ac2:5b0c:: with SMTP id v12mr24269831lfn.184.1560256342030; Tue, 11 Jun 2019 05:32:22 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Jun 2019 05:31:45 -0700
Message-ID: <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="0000000000000696d8058b0b7dcd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/rXnwR0UTjeSxxU66ESrLOX9TDBM>
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 12:32:27 -0000

On Tue, Jun 11, 2019 at 5:21 AM 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.
>

That's helpful, but I think it also suggests that the problem statement
that SM has written is not really right: for instance, we could solve the
problem of people being targets of retribution by having the signers be
secret [0].. And we could address the pool issue by letting them serve on
the committee.

OTOH, it seems to me that the purpose of these requirements is to have a
certain level of accountability for the people requesting the recall and to
have a certain minimum level of support. So, is it clear that we actually
want to relax those objectives?

in any case, I think this exchange suggests that the first thing that's
needed is a problem statement that's decoupled from the solutions being
proposed.

-Ekr

[0] I'm aware that there are challenges here in verifying eligibility. I
believe there are solutions here, though they are too small to be contained
in this message.

Eliot
>
> -Ekr
>
>
> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>> That's nice. I like the clarity.
>>
>> I also like that the worms are kept firmly in their cans. It is without
>> doubt that a hundred other issues concerning the recall process could be
>> aired, and I am certain that many people have different hot issues. But I
>> firmly believe that addressing a few at a time is the best (only!) way to
>> make progress.
>>
>> If it turns out that there is support for resolving any of these three
>> issues, they can be quickly picked off and we can move on to other issues
>> if
>> there is interest. If there is no support for addressing these three
>> concerns, then they can be put to one side and work can start on other
>> issues if there is interest.
>>
>> For my part, I think that all three issues should be addressed, and I
>> think
>> that the approaches suggested in SM's draft are a good starting point for
>> discussion.
>>
>> Thanks,
>> Adrian
>>
>> -----Original Message-----
>> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On
>> Behalf
>> Of S Moonesamy
>> Sent: 11 June 2019 11:45
>> To: Suresh Krishnan <suresh.krishnan@gmail.com>;
>> eligibility-discuss@ietf.org
>> Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net
>> >;
>> Alexey Melnikov <aamelnikov@fastmail.fm>
>> Subject: Re: [Eligibility-discuss] Virtual BoF for
>> draft-moonesamy-recall-rev
>>
>> Hi Suresh,
>>
>> Please see a revised version of the BOF proposal to address your comments:
>>
>> Problem statement
>>
>>       The current description of the process for initiating petitions
>> for recalls
>>       for NomCom-appointed roles is described in RFC 7437 and is
>> being updated in
>>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only
>> three
>>       specific issues with the petition process; other parts of the
>> recall model
>>       and other ways of removing Nomcom-appointees are explicitly out of
>> scope.
>>
>>       The three issues are:
>>
>>       - Ineligibility of remote participants to seek redress through the
>>         recall process;
>>
>>       - Reducing the number of signatories for a recall petition;
>>
>>       - Ineligibility of IAB and IESG Members and other Nomcom
>>         Appointees to sign a recall petition.
>>
>> The purpose of the BOF is to examine the above-mentioned issues and
>> determine,
>> for each, whether it is sufficient interest and importance.
>> draft-moonesamy-recall-rev
>> is a possible starting point for the effort.
>>
>> Regards,
>> S. Moonesamy
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
>
>