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

Eric Rescorla <ekr@rtfm.com> Tue, 11 June 2019 12:59 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 DBE32120158 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:59:22 -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 ZMU37q_Z_3DU for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:59:19 -0700 (PDT)
Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (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 3B71A120025 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:59:19 -0700 (PDT)
Received: by mail-lj1-x244.google.com with SMTP id 16so11500829ljv.10 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:59:19 -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=fHjj72mfB2b8ntVk6R8Hhp7J6ExILfwPnaNpkPOdleA=; b=E32b0/riT0aZJgXJoQnoie6VzyNeQ4AJOMC5e/QaTN3kvnwpuYJhCsP6cHwFvfoabc U7dUu3CvthzfINoln5biG0ue7QxU4uIGu/6uggWtR4J+34gcgPy6tFth1Cnrqs/7RjHK dWwCkh9Ntk7+U/9fkrn6TgMrRPB8bgyMAQf4FZ0qT4kYsYXmw4NpeuG0TaxQ3dHXNgod lafwrlKcX1jBWPgF1OdZRHF0/FmtSGSyLtEuyMZ31FSOtYSbb+EpgSvVHX6nZ2UQ8OMb MJWx07XSC0TP5Lo81dhqRvUHqPC0cao38BjsMSh8EQwOOSzPf+9OcRKaB5I0SPJJgATU /++Q==
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=fHjj72mfB2b8ntVk6R8Hhp7J6ExILfwPnaNpkPOdleA=; b=WJDEG/rrMnzWYKIpS0Kl8k2rg4Duz+nPSYJM0v0vwmStL/GZbKFgQL77lxmaJ2HjyK 7ya6zT20tf03IZzuOcoOCwOymiWgNn+xC2FL33A3aJKdxSZUslYp7Zq8VTuP6C5ELJBJ fQViWxyusvQKkg0hfKm3Ff7W5PoUsVBll0mR8OmGsy1M/txE87yQnfjbPbmbQLTSQv4l CyMyxZyCu81zmauN9VTMXHyl58ZIdhqiEU41Y+O4Mjq5ry8PCTe7rQKMCTXs3UFMfd2a 8ax++vHaAHxRLwmyKYJZXbkz4PGKEkHXdfH6EvITXRGNlvPCY6l9q2uEH4Infqgosr0K ibGA==
X-Gm-Message-State: APjAAAUPwgLRQLv5cXnETd18KWX1Ayoqrcii6a6RCm1bvS08/mshNjiJ z4BnO66jWPcNiRNEAkD7OduVMqLtAvb74ObdXHv/xQ==
X-Google-Smtp-Source: APXvYqzLNi830gaYa8Jwg9kJQ+iZSh4xUNZvErJ7z0p7ODByNu96aDQCEuFd1YOveZ7J9oMqGPa6TiBIocfA6miSZ9Y=
X-Received: by 2002:a2e:9152:: with SMTP id q18mr21126704ljg.77.1560257957490; Tue, 11 Jun 2019 05:59:17 -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> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk>
In-Reply-To: <066801d52053$650ea290$2f2be7b0$@olddog.co.uk>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Jun 2019 05:58:40 -0700
Message-ID: <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: Eliot Lear <lear@cisco.com>, 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="000000000000508578058b0bddc5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/ITC4-0E2oGivcUd7Xl1KHcXoFBo>
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:59:23 -0000

On Tue, Jun 11, 2019 at 5:45 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> How about phrasing the problem as “You need too many people to sign a
> recall petition, and that makes it too hard to achieve a recall”?
>

Without taking a position on the merits, that seems more like a problem
statement. An even crisper statement, perhaps, would be "It's too hard to
achieve a recall"


We can agree or disagree about whether this is a problem and whether we
> want to work on it. That’s why we have BoFs and mailing lists.
>

Yes.

We can debate the correct solution for each problem, but (usually, when we
> have a BoF) the discussion of the solutions is sequenced after the
> discussion of the problems and agreement that we want to work on the
> problems.
>

Agreed. That's what I'm hoping for here.

-Ekr

Adrian
>
>
>
> *From:* Eric Rescorla <ekr@rtfm.com>
> *Sent:* 11 June 2019 13:32
> *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>
> *Subject:* Re: [Eligibility-discuss] Virtual BoF for
> draft-moonesamy-recall-rev
>
>
>
>
>
>
>
> 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
>
>
>
>