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

Richard Barnes <rlb@ipv.sx> Fri, 25 October 2019 12:52 UTC

Return-Path: <rlb@ipv.sx>
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 89C3812086F for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 05:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 s5eI2cl81l6I for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 05:52:27 -0700 (PDT)
Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (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 288BA1200B5 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 05:52:27 -0700 (PDT)
Received: by mail-oi1-x234.google.com with SMTP id j7so1570661oib.3 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 05:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JD+ijPhxW9wMmALDhvzhWB+GLnJhZKpFNF5fz0RZGKI=; b=rhECfvZbhH+/jyUk+IqySDMxcGh7I6/hD8S6uUateMSIhJH9fVR54K4tbM5nPZYJjp s8i7FffARg+DrlFa1K5UZPPLb/n3LrYB4jCvp+FyOuCDd90dNkYkfa/Htm8CTXMhN+6t +yub97garupN7ZanrWRhbT69QG3NqC9kcPHmq23O03H4TycxZ+Ex7tR+4i1uUZvJIHCo XwvmHxPZYNGLmXWuoFWctVT0nvYJTQrdYAhtMzSYkTuURKs0HdqD30Ki37z4+H/v+Loy ZFw0HQ65Uj0TGyKnTxy1bsdS2R8txzW/gER70ky9ucI4JU/2D8Lpnl9V59SVY6XeCsg+ CRqA==
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=JD+ijPhxW9wMmALDhvzhWB+GLnJhZKpFNF5fz0RZGKI=; b=i+fPCIedy+LQGZXnCm34bgyTsRcrVnxkS0an7z/4Nxz6fJE2R4A85UZZ94o02KBtoT KOOqZIxfyUZVvCFqQbhK+3qfuhpX6k1lCLHkWoakRmHJNKAGj6OuUAT3xfi4I3fxQBeh RS5J/Xv2PoPGNE4mOFmjKB8HKreh2ewdZLkSchq6aGbzXI2FM5pLOACQnXJAU9kKXyb4 ofvMCyxCeMtcNgZKctpFv1VlramfcLGbceP9ZiBOZa2kCf7yUPRDRD9s1tnPhNMTZ8yO VvY6tOetIY8bmHjBFoC+JLDzzB0oSGXYAFUorfHCAnK1txd8qLtj7eQqhRBTWBWOBzYP nl0w==
X-Gm-Message-State: APjAAAWEbyJ5elZNAbuMICAi89aiO3JYVXDiriuGkhZDDGIK3p94PCmM 5UZGZ6C39+DAyHwEBD+8u0/dnbC5GYL/aA8I/M2flw==
X-Google-Smtp-Source: APXvYqzswmReWFk887S1WahOk3mrkWjCrO0bUqmXIBfCGkoiLmBh5GtUlh3OMEdToG0PeBhQF7f11GFjMolmGbKGujA=
X-Received: by 2002:a05:6808:5ca:: with SMTP id d10mr2740612oij.135.1572007946093; Fri, 25 Oct 2019 05:52:26 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <2D6F641A-CED0-4C35-A72E-D4BDC48F457C@cisco.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 25 Oct 2019 08:52:04 -0400
Message-ID: <CAL02cgSo3yQe7ZBiV_ZT4qNw7ApZt8t5yY7viwAW7xvhS31hsw@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: adrian@olddog.co.uk, eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000361f3a0595bb9f13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/9jzmrha_O4Vcdi1dlHjCd9SwykI>
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 12:52:30 -0000

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.

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.

--Richard


On Fri, Oct 25, 2019 at 6:51 AM Eliot Lear <lear@cisco.com> wrote:

> Hi Adrian,
>
> > On 25 Oct 2019, at 12:18, Adrian Farrel <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
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>