Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions

Eliot Lear <lear@cisco.com> Fri, 25 October 2019 15: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 2DA99120168 for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 08:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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, URIBL_BLOCKED=0.001, 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 m0QSsI5hyFgP for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 08:39:27 -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 365CA1200C5 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 08:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13951; q=dns/txt; s=iport; t=1572017967; x=1573227567; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=TiMWRDkruYZJ2rDYLInPgE6Safb0elqMa7HCCqpqBmc=; b=hC68Q9WhLJuKZ5A+lvCfQ7Imsmh/qujkfDSL37A4NM0cI8+nhwDUi9u4 98tF/SvRfkiy3nuDFCfNvCtSPeKSREvdNt3QR6vT2TGbZonhbAPPur0Km IwZD7E+6EZQQDoBL5xIX3ClhJt600I099EfZhMfz5xW/LCfUcirq8mCUh 4=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQAAC0FbNd/xbLJq1lGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgWkCAQEBAQELAYFugR1UIBIqhCiJBIgLkySGD4F7AgcBAQEJAwEBGAEKDAEBg3tFAoNjNgcOAgMJAQEEAQEBAgEFBG2FNwyFUAEBAQECAQEBIUsLBQsLDgonAwICJx8RBhMVgw0BglcgD7FEdYEyhU6EawoGgTYBgVKKVIF/gREnH4JMPoJiAQGEcTKCLASWNYgujwKCLoIzgRORZxuCPItcJ4sUpHSDFAIEBgUCFYFZCSmBWDMaCBsVOyoBgkE+EhAUjA2FQT8DMJAvAQE
X-IronPort-AV: E=Sophos;i="5.68,229,1569283200"; d="asc'?scan'208,217";a="18377072"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Oct 2019 15:39:25 +0000
Received: from [10.61.195.187] ([10.61.195.187]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x9PFdNq4004816 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 25 Oct 2019 15:39:24 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <AC7F5A9D-4F74-464E-A63F-7F5D8BD62921@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2AA1ABAC-18B2-4778-B0CC-4B917BCA2BC2"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 25 Oct 2019 17:39:23 +0200
In-Reply-To: <CAL02cgSo3yQe7ZBiV_ZT4qNw7ApZt8t5yY7viwAW7xvhS31hsw@mail.gmail.com>
Cc: adrian@olddog.co.uk, eligibility-discuss@ietf.org
To: Richard Barnes <rlb@ipv.sx>
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk> <CB806045-0E5E-4445-A377-7CD547B9DD90@cisco.com> <010a01d58ac1$c0ab2320$42016960$@olddog.co.uk> <CB7198FC-294A-4F5E-A57F-49333DD8C56E@cisco.com> <017a01d58b1d$9e5969b0$db0c3d10$@olddog.co.uk> <2D6F641A-CED0-4C35-A72E-D4BDC48F457C@cisco.com> <CAL02cgSo3yQe7ZBiV_ZT4qNw7ApZt8t5yY7viwAW7xvhS31hsw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.195.187, [10.61.195.187]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/igSoW2KWCADFUjE8g43n3gg-_Dc>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
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: Fri, 25 Oct 2019 15:39:30 -0000


> On 25 Oct 2019, at 14:52, Richard Barnes <rlb@ipv.sx> wrote:
> 
> I'm puzzled by the focus on meeting attendance and acculturation here.  The former is at best an obsolete metric; the latter is so vague as to be useless.
> 
> Let me try to articulate propose a different operating principle here, one effectively of self-determination: A person should have a say in a decision if and only if they are affected by the outcome.  I think this principle leads to the right result in the base case, and provides helpful insights in the recall/NOMCOM case.

Sort of.

You want a big enough pool of people in the NOMCOM to have some detachment from any particular Area.  And those people should have understanding of what should be expected from that individual, independent of what they read on the job of description.  That is acculturation or experience with the organization.  Vague, but not useless.

> 
> By "the base case", I mean: Who gets to participate in the development of IETF specifications?  While some are affected more than others, IETF technologies have impacts for the whole Internet, so it makes sense that anyone involved in the Internet should have a say -- and nowadays, that's basically anyone.
> 
> With regard to NOMCOM and recall, this raises the question of who is affected by the choice of who is on the leadership bodies.  Clearly not everyone; your average user of the Internet has no reason to care who's on the IESG.  Meeting attendees are affected to a degree, since the NOMCOM-appointed leadership is in charge of setting the agenda and the norms for participation.  The people who are much more affected by the leadership are those who are actively participating in document production -- people who have authored documents, participated in discussions in meetings, contributed to last calls, chaired WGs, etc.

I’m a little less clear on how to evaluate some of that, but

> 
> --Richard
> 
> 
> On Fri, Oct 25, 2019 at 6:51 AM Eliot Lear <lear@cisco.com <mailto:lear@cisco.com>> wrote:
> Hi Adrian,
> 
> > On 25 Oct 2019, at 12:18, Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk>> wrote:
> >
> > So, if I might rephrase, you are worried about:
> > - gaming the system (as previously noted)
> > - not understanding the IETF culture and attempting
> >  to make it that which it is not.
> >
> > I hope I have that right.
> 
> That’s close enough wording to what I am thinking.
> 
> >
> > Asides from the fact that that leads to perpetuation and ossification, I think we are agreed that "some level" of established participation is required.
> >
> > Now, I would argue that physically attending three IETF meetings does not do much more than show financial support from a sponsor organisation. I might even suggest that there are a few people who have attended a number of IETF meetings who really have no clue how the IETF works: they "vote" on mailing lists; they post individual drafts and are upset that no one converted them to RFCs; they don't read the drafts. So let's not make the barriers for remote participants such that we embarrass ourselves.
> >
> 
> Yes, we have had all of that.  None of this guarantees clue, and quite honestly, to address your other point, the culture sometimes does have to change. So long as that is a conscious change, that’s fine, but not knowing the culture means it would not be.
> 
> 
> > On the other hand, I do agree that we need to see remote participants as, in some sense, full participants before considering that they can start a recall. So we are just arguing about the detail.
> >
> > You (it seems to me) are suggesting a large number of potential criteria against which we can measure "involvement". I am looking for a more simple measure just like the 3-of-5 that we apply for physical presence where we don't additionally require co-authoring of I-Ds or some such.
> >
> > I think we could arrive at an easy bar such as 5-of-6 when less than 3 have been physical.
> 
> I would be happy if someone attended so much as once, such that the 3/5 would apply. The lengthy criteria was just meant to lower the bar as far as possible, but one can certainly at least start simple.
> 
> 
> > And I'm happy to talk about that. But the question of "culture" comes down to this: what is the IETF culture and where is it documented?
> 
> Oh I don’t even think we have to go that far.  So long as someone has an educated perspective, their entitled to decide that for themselves.
> 
> > Do I understand the IETF culture? Do you?
> 
> Yes, we both do.  But our understandings may differ ;-)
> 
> Eliot
> 
> --
> 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>