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

Eliot Lear <lear@cisco.com> Tue, 11 June 2019 12:39 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 D042D120136 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:39:01 -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_HIGH=-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 lftNq13O7umZ for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:38:59 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44CA612011E for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:38:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21504; q=dns/txt; s=iport; t=1560256738; x=1561466338; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=H7ovk4gDQKBjZStecKEanKwzuPhJFZe1A6o91GZ35IE=; b=eKRQNcQDU97glUTnbgYALj/OqMRqAygr/kdoHAoNdIeRCyQH/1zuDT0B s6sMXbJHr3H1vDBOTRI6dndpfJ3YqRydATrqdxJPQ6Jl1vaw/YOhoRqgX 608KbCDi/dGxGcJRjiJ89shuO2GH+lFlJAInqbDRNTGGw+kJ2S3rPl65O A=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAABtoP9c/xbLJq1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ5TBYEUUQEgEiiEFYgcX4wFiUOPHhSBZwIHAQEBCQMBARgBCgwBAYN6RgKDITQJDgEDAQEEAQECAQRtHAyFSgEBAQECAQEBIUsLBQcECw4DBAEBAScDAgIhBh8JCAYTG4MHAYFqAw4PD6hpgTGFR4JCDYITCgaBNAGBT4okgX+BEScfgkw+ghpHAQGBSYMiMoImBJQOlGQ+CYISghuBBow5g2sbgiWGfYNgih6WDoo/gwcCBAYFAhWBTziBWDMaCBsVOyoBgkE+gnYBCYdVhUE9AzCQEAEB
X-IronPort-AV: E=Sophos;i="5.63,579,1557187200"; d="asc'?scan'208,217";a="13036367"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 12:38:55 +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 x5BCcsAs008848 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 12:38:55 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <C30E8A9D-5D0A-456F-AC09-DB6787DEE4C6@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D8C6174D-B489-4E7B-91C6-46014289C319"; 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:38:52 +0200
In-Reply-To: <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
Cc: 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>, Adrian Farrel <adrian@olddog.co.uk>, 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> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@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/ed-Y4SpTIIrp6ku6AlnXFXZ8XXo>
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:39:02 -0000


> On 11 Jun 2019, at 14:31, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> 
> 
> On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com <mailto:lear@cisco.com>> wrote:
> 
> 
>> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com <mailto: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.

I agree with your 2nd sentence, but not your first, at least entirely.  It’s just just about eligibility, but also about the recall committee being able to understand the concerns of those seeking to have someone removed.  But I think your general point is well made: there needs to be one or more crisp problem statements to start with, and then various approaches can be considered to address the matter(s).

Eliot


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