Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

Barry Leiba <barryleiba@computer.org> Fri, 26 April 2019 20:30 UTC

Return-Path: <barryleiba@gmail.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 C7BC412001B; Fri, 26 Apr 2019 13:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 d7uLnxMWWzq7; Fri, 26 Apr 2019 13:30:37 -0700 (PDT)
Received: from mail-it1-f178.google.com (mail-it1-f178.google.com [209.85.166.178]) (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 B225612048C; Fri, 26 Apr 2019 13:30:37 -0700 (PDT)
Received: by mail-it1-f178.google.com with SMTP id x132so7884041itf.2; Fri, 26 Apr 2019 13:30:37 -0700 (PDT)
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:content-transfer-encoding; bh=r4OegbFPtaf0PZqKsWMXI/wr0GLHMC1i33Vmjz5Gzrw=; b=ITWDIe+LHFa8wrNAwWktsrysqupYug2cph5eR/LLPBPiAwuHUlcshkcvmih43totzl u7eQpH4VQwbZTNN3G0bz96a3U1LBFrZ3M4/V36cLm2mKUY2sPFbhNh1nXV4n3OxQkXom yo4EXJFWr17J11SSXl/TsKVaBc7vUJQ0hJ/WTYYLRfSDbucCMB3S6o5Tz0EpySRTqrcs LP+NKcPR2Y69lA5xq7oqNPHVDWK5uY2sMbNCgkrxOYpeWsLhWQiLwSAUplHE5zMPhVgw t2G56MDRFS8a0Isf5xNpUWSnyfk51S6jESXJ708NFHiBDy/OzxsnTjg1h1UQYGmdYNRN Lq7w==
X-Gm-Message-State: APjAAAX9OHwsXNx+DckawwCjAYCrBbcqaW7iBEMoP6L8kDT1/gbpUyth b/YCG9xJffKejWTlMKooBIWGdFSbYcgHAWj6GxA=
X-Google-Smtp-Source: APXvYqwm+L5ziJGJa33vubmKH/d/YTVXcplgEszYxZt1sP489kcXzTLbcmiY63uMgSWICNhHv9eEgdQCyxVRdQUR4O0=
X-Received: by 2002:a05:6638:214:: with SMTP id e20mr6631619jaq.59.1556310636532; Fri, 26 Apr 2019 13:30:36 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <BB40F115-46E8-4EF3-ABDE-15ABB33B4ACA@akamai.com> <C11980900F520E0EFCC83CEB@PSB> <A18C5417-F40B-4DC4-B6AB-BA0A592D15D3@cooperw.in> <6.2.5.6.2.20190419223655.108e5998@elandnews.com> <C70ADE76-0BA7-4E3A-BEFA-37F12601A6F7@cooperw.in>
In-Reply-To: <C70ADE76-0BA7-4E3A-BEFA-37F12601A6F7@cooperw.in>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 26 Apr 2019 16:30:25 -0400
Message-ID: <CALaySJLQ_v8iDbD8uT3aSiNxqYRuJxWn9YmANWPmcs1FwKAUow@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: S Moonesamy <sm+ietf@elandsys.com>, Adrian Farrel <adrian@olddog.co.uk>, Aaron Falk <aafalk@akamai.com>, IESG <iesg@ietf.org>, eligibility-discuss@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Ul_ZQy52oYMkkgjuEdHTKT9cyRw>
X-Mailman-Approved-At: Fri, 26 Apr 2019 19:25:03 -0700
Subject: Re: [Eligibility-discuss] AD Sponsorship of 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: Fri, 26 Apr 2019 20:30:39 -0000

> > From what I understand, the governance part of the IETF is done by the IETF LLC.
>
> I guess it depends on your interpretation of governance, but as I said in my other mail
> I don’t think the IETF LLC has to do with the IETF’s governance, which is done by the
> community itself.

I agree with Alissa: the aspects of what one might call "governance"
that the LLC is responsible for are the financial and contractual
ones, and that is explicitly designed as "administration" in
everything we say about the LLC.  What I normally consider a
governance role as deals with day-to-day running of the organization
-- leadership to achieve the organization's goals.  The LLC explicitly
does not get involved with that.  There is, of course, a connection
through the finances, but I think there are enough checks to keep that
clean.

> > from Section 2.2: 'Restricting signatories to those who are "nomcom qualified" disenfranchises
> > active remote participants who reside in emerging countries as they lack the extensive travel
> > resources required to seek redress’.
>
> People who participate exclusively remotely are disenfranchised from seeking redress in a number
> of ways, not limited to the recall process. If the community views the disenfranchisement of remote
> participants from seeking redress as a problem to be rectified, it would be useful to know that and
> to use it to guide solution discussions.

Again, I agree with Alissa.  SM, I know you had tried at some point to
set up a path for nomcom eligibility for remote participants, and that
didn't happen.  I think that is a much broader, more significant, more
useful way to enfranchise remote participants.  If this effort is an
alternative to that which comes out of not being able to get the
broader issue addressed, then I suggest we look at the broader issue
again instead.  But to know whether that's the approach to take, it's
important to properly and fully understand the reasons we're looking
at this current effort.

> My point is that I believe the key reason the recall process does not get used is because it
> creates reputational risk for the petitioners.

Actually, I quite hope that is not "the key reason".  It's surely a
concern, and we can (and perhaps should) develop ways to mitigate
that.  But as I see it, the *key* reason we have never recalled an AD
or IAB member is that we view it as a very serious thing to do, and
something that should be reserved for only the most egregious
situations.  And, while there have been rumblings in the past about
kicking off a recall, our (correct, as I see it) aversion to using the
process has kept it from actually happening.  *For the most part*, a
bad situation with an AD or IAB member can and should wait the less
than two years it takes to have the next nomcom unseat that member.

I hope we don't move in the direction of turning recalls into more
normal actions than what I describe above.  I'm not averse to
adjusting the process, but in the end I still want it to be fairly
much in the realm of dropping a major bomb.

Barry