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

Eliot Lear <lear@cisco.com> Tue, 11 June 2019 12:21 UTC

Return-Path: <lear@cisco.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 A3152120115 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 n2r6bmxUwvy1 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:21:28 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF6C9120043 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12164; q=dns/txt; s=iport; t=1560255688; x=1561465288; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=07aFQrB9WLppRQacb7rFx8WeAF0OOfa08Aw2hpX5RNo=; b=FieCEMnJljizjLRKK2/s4LeBp9X9wLFAiufdWA4jzh3+vfImyDlxmPhm UGseDpn3vrJPYWS4Y4BulPGzTLlFEI2jDxaD6FFicMKYOQYYazvvCN1uV JiUFJldU/PU2uax+h7WqZ16hZ7S0t2Db53pKdDh87dBjFrR58fEQSoRn7 c=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAABpm/9c/xbLJq1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUgMBAQEBAQsBgWaBFFEBIBIojRCMBYlDiR2GAYF7AgcBAQEJAwEBGAEKDAEBg3pGAoMhNQgOAQMBAQQBAQIBBG0cDIVKAQEBAQIBAQFsCwUHBAsOAwQBAQEnByEGHwkIBhMbgwcBgWoDDg8PqgqFR4JCDYITCgaBNAGBT4okgX+BEScfgkw+ghpHAQGFHYImBJQOlGQ+CYISghuBBow5g2sbgiWGfYNgih6WDoo/gwcCBAYFAhWBUQI0gVgzGggbFTsqAYJBPoJ2AQmHVYVBPQMwkBABAQ
X-IronPort-AV: E=Sophos;i="5.63,579,1557187200"; d="asc'?scan'208,217";a="12975131"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 12:21:24 +0000
Received: from [10.61.194.73] ([10.61.194.73]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x5BCLNno006131 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 12:21:24 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DF307A8E-8F11-4D10-B635-8F2C730A04F2"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 14:21:21 +0200
In-Reply-To: <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.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>
To: Eric Rescorla <ekr@rtfm.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>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.194.73, [10.61.194.73]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Ju7R5EwgJX9rhBF0vBH-pi6LwJM>
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:21:31 -0000


> 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.

Eliot

> -Ekr
> 
> 
> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk <mailto: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 <mailto:eligibility-discuss-bounces@ietf.org>> On Behalf
> Of S Moonesamy
> Sent: 11 June 2019 11:45
> To: Suresh Krishnan <suresh.krishnan@gmail.com <mailto:suresh.krishnan@gmail.com>>;
> eligibility-discuss@ietf.org <mailto:eligibility-discuss@ietf.org>
> Cc: John C Klensin <john-ietf@jck.com <mailto:john-ietf@jck.com>>; Warren Kumari <warren@kumari.net <mailto:warren@kumari.net>>;
> Alexey Melnikov <aamelnikov@fastmail.fm <mailto: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 <mailto:Eligibility-discuss@ietf.org>
> https://www.ietf.org/mailman/listinfo/eligibility-discuss <https://www.ietf.org/mailman/listinfo/eligibility-discuss>
> 
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
> https://www.ietf.org/mailman/listinfo/eligibility-discuss <https://www.ietf.org/mailman/listinfo/eligibility-discuss>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss