Re: AD Sponsorship of draft-moonesamy-recall-rev

Michael StJohns <mstjohns@comcast.net> Thu, 25 April 2019 17:36 UTC

Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6FEB1201DC for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2019 10:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 lEmHeKwYrh8D for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2019 10:36:40 -0700 (PDT)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 841C812025D for <ietf@ietf.org>; Thu, 25 Apr 2019 10:36:30 -0700 (PDT)
Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-09v.sys.comcast.net with ESMTP id JdGjh2HWxNBGvJiIPhERFO; Thu, 25 Apr 2019 17:36:29 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1556213789; bh=L5yV+mSmdQSI7WIAP1F8CqLN5Pl/5VKdwuwR53euAbM=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=B7aIxtoMEpHF4Wp7BngmmS8+TEO7G5nJ6hJnIEku12E2UkhT+ZVUA13cycFQzpAvC E7cE9WXl1+Fb1aFSttiDezBgJuZKqGWBAPY51WiD0HjrUmhcAJuSz2S39Bel6avU4b kJ+HIquT8DDqKNMKng4StPyhKxvh5+ovtiXGguX7XtBsSaNVLP7A3XOCa9cHFNcD1c 3JcqIzzGkKGBSTVzItKFnPvBfFQERDUZeC0GYkSqtj8cm1VuczN7ZrXsK0d04os35s +clM09OZzs3fTmcBvLuSOoTT7ihSrxCc1Rig7QbJH6N90jsOkI/NID2LpzIttO+3AM k15drDgaoKbCw==
Received: from [IPv6:2601:152:4400:437c:583d:abed:961d:e6df] ([IPv6:2601:152:4400:437c:583d:abed:961d:e6df]) by resomta-po-12v.sys.comcast.net with ESMTPSA id JiIOhTxpW3i74JiIPh6mpL; Thu, 25 Apr 2019 17:36:29 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: ietf@ietf.org
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <C7274EAB-7DDC-491F-9DD2-0CFFADB13CA9@cooperw.in> <72f00d0b-7ec6-ba6a-b17b-97879d457ae3@comcast.net> <CAKKJt-fOMMdM-mkbJaYpsH6XPCpatUkwZY-d_A+MaNa3nhaNDg@mail.gmail.com> <CABcZeBNdaWU4wwOK_MnWC5hOr7Lu3osmC_6_KKxB5fHuHVHyTw@mail.gmail.com> <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net> <b4c79b85-15b3-0c56-d4ab-a274b7bdae78@network-heretics.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <507d3dc9-dd90-827d-a8df-f8bb33fada3c@comcast.net>
Date: Thu, 25 Apr 2019 13:36:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <b4c79b85-15b3-0c56-d4ab-a274b7bdae78@network-heretics.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zkWXPAHTyD18eZqQPaRtcVom1hM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2019 17:36:43 -0000

In line

On 4/23/2019 12:39 AM, Keith Moore wrote:
> On 4/22/19 11:32 PM, Michael StJohns wrote:
>
>> Instead, I'd like to propose that we move to an expulsion model for 
>> the IAB and IESG where the members of the organizations are able to 
>> remove a member under certain circumstances:  Behavior inconsistent 
>> with a fiduciary (e.g. acting for your company or contracting entity 
>> to the detriment of the standards process); behavior that adversely 
>> affects the standardization process (IESG) or behavior that adversely 
>> affects the general operation of the IAB (e.g. things like 
>> harassment); abandonment of the position or  lack of communication 
>> from the member. 
>
> I definitely think it's worth looking at alternative models for 
> removing IAB/IESG members who misbehave.   However for your proposal:
>
> a) I suspect there's a risk that an IESG would not support expulsion 
> of a member who had clearly discriminated against a participant out of 
> some kind of prejudice (other than technical judgment), because that 
> IESG wished to protect its own.   If nothing else, the perception of 
> such a choice by IESG would harm IETF's reputation and thereby harm 
> its ability to do work.   So I think IESG cannot be its own sole 
> watchdog of its members; there must be the possibility for some other 
> "last resort" means of recalling an AD from outside of IESG.   Perhaps 
> that could be managed as a kind of an appeal rather than initiating a 
> recall petition as is currently envisioned.
>

Good comments overall.  But:

Appeals are generally taken against final decisions rather than just 
hanging there loose to be applied against something that might not 
actually have had a formal appraisal and decision.

WRT to "protect its own" - if there's a problem that has enough 
consensus of a need for resolution, and the IAB or IESG does not take 
action, then you address it  at the next Nomcom cycle and remove not 
only the problem child, but the folks that didn't act. But I'd be 
surprised if we end up with that result.  I don't always get along with 
the leadership and some actions they've taken over the years annoy the 
hell out of me, but for the most part I consider them honorable and 
generally good fiduciaries of the IETF process.


> b) On the flip side, there's also some risk that an IESG would seek to 
> marginalize a lone voice within its ranks that argued for sanity 
> against a widely-accepted madness, and use the expulsion process as a 
> way to silence that individual.   So I don't think IESG should be able 
> to expel one of its members without external scrutiny as to what 
> justified it.   (note that I didn't say _public_ scrutiny.)   In such 
> a case, review by the current nomcom might be appropriate.

There are a few ways of dealing with this -  either have a second body 
confirm the expulsion - or - my preference - make the expulsion 
appealable and use normal appeals process to act as a check and 
balance.  I don't think it's an unsolvable problem.


>
> All of this is tricky to get right though, and we could easily end up 
> with worse (e.g. more easily gamed) than what we have now.

To be blunt - I think the "easy to game" argument is a red herring in 
all its forms, such argument only given some small amount of life based 
on the actual black and white text of the recall process and vivid 
imaginations.  A bigger problem - IMHO - is the ridiculous amount of 
time it would take to process the recall after the petition is 
certified.  I neither think it would be difficult to got 20 signatures 
using the current criteria for something sufficiently serious for a 
recall, nor would the IETF fall for any of the various permutations of 
sock puppets and trolling and DOS attacks we've discussed in this and 
other related threads.


Later, Mike


>
> Keith
>
>