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

Keith Moore <moore@network-heretics.com> Tue, 23 April 2019 04:39 UTC

Return-Path: <moore@network-heretics.com>
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 503D012030E for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2019 21:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 ShjYMPLAANNF for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2019 21:39:32 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7329B12026B for <ietf@ietf.org>; Mon, 22 Apr 2019 21:39:32 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A528022131; Tue, 23 Apr 2019 00:39:31 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 23 Apr 2019 00:39:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=3qCenNiew+e66r0P3kA6kJxTB3/f/vYHhpKrm9eXX f8=; b=uUz8TY0wlfSk9T4v+bUqJWg1SJZdrhEu7f0PNGY8SzDNxSaPyYqeMd89Q 7cqOmVmYA8EKo6geisVZuvBzx8hXdAuAf6qHR/O7GxhvcLfZu1v9EFILE+xm+fGB WKOxzjP/Nui9hcznlDva3q9FwyMoKkrB4Yqm1Zb7uPNgA1HZjg4ksHVjXq0cfCpU 8VtLJRtos/2HyEFBi+DGo/dePBAZAq+8ciTlHlZIC8kesimlODZ6RTqW2zAKdZRv A9vF0T9O2Ovo5svZIEZVJtmZ9/4I7u5gVFx8SOAl4O1ms3Ph2HM4CRN7zLf3viZu /ioIguvLVLjOZrDcqkxtIrCX3GfUQ==
X-ME-Sender: <xms:A5e-XHpetb9OUELKY4D3fihx8S3wjWfOBJ8j2uImtMMoF-R0ujgggw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeejgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgv thhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:A5e-XMjfZeVmSxMMckMnTHLF8-0FECR_Z6aYV05-_Vb3tCEH7O956w> <xmx:A5e-XMC4_FJ1E_ZVmn68hTA183MH15xAStNox_Q7WCelxw14TIjRVA> <xmx:A5e-XJE3gaKpMOrNbuDeHa4Olg7uSaS454rQG86J2qkDffxSg2wbqg> <xmx:A5e-XPJTpEATW3VxBX9hBU1WFtZAsASjU9Lb8zIG7FdaXIrzqoWcqg>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id D71BE10316; Tue, 23 Apr 2019 00:39:30 -0400 (EDT)
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>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <b4c79b85-15b3-0c56-d4ab-a274b7bdae78@network-heretics.com>
Date: Tue, 23 Apr 2019 00:39:29 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net>
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/0J2JuA29mlV6HK5q2WN3nFIf7cM>
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: Tue, 23 Apr 2019 04:39:34 -0000

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.

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.

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.

Keith