Re: [Eligibility-discuss] New draft: draft-rescorla-istar-recall-00

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 16 May 2019 13:32 UTC

Return-Path: <jmh@joelhalpern.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 7BF04120025 for <eligibility-discuss@ietfa.amsl.com>; Thu, 16 May 2019 06:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 8E857jXxa161 for <eligibility-discuss@ietfa.amsl.com>; Thu, 16 May 2019 06:32:26 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 29169120045 for <eligibility-discuss@ietf.org>; Thu, 16 May 2019 06:32:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 454XQx6YvnzKmpC; Thu, 16 May 2019 06:32:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1558013545; bh=n7NCRidKq9IqIBrCyGcypwW5A/T6uXIsVnHbR9gW2y4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=MPqMVY5H7v5Bi8P2p48ulshDqjT9PznFUImaTq5zsUfDUcMyMINQz2NIt4r1tlZ+p c2gq/nIwJuJEm4mHXGwRplka2MJxCMSlza54QQAA3KQTMraLRADjv09hYApLvzK1Lj YQ3FgjA2/Mtk4StnAyc3XwxXMiujj0M+eD9STww0=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 454XQx2jjYzKmp1; Thu, 16 May 2019 06:32:25 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>, eligibility-discuss@ietf.org
References: <CABcZeBNMorOsoyaga2Axh1285ps345GGNjtBYy7K84qhNS3FQA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <187912b7-467f-2f57-b059-89c2e92280cd@joelhalpern.com>
Date: Thu, 16 May 2019 09:32:24 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBNMorOsoyaga2Axh1285ps345GGNjtBYy7K84qhNS3FQA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/YYEr0R854wD841VwsnwuVJVM6J0>
Subject: Re: [Eligibility-discuss] New draft: draft-rescorla-istar-recall-00
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: Thu, 16 May 2019 13:32:27 -0000

Given your description here, I would have expected the document to 
include a clear set of definitions for what constituted legitimate 
grounds for such expulsion.
As written, although you specify an appeal process there does not seem 
to be any well-defined grounds provided for such an appeal.

If it is really about cases of serious non-performance, I would think it 
should say that.  And that it should take more than 67% of the body for 
the removal.

Yours,
Joel

On 5/16/19 9:16 AM, Eric Rescorla wrote:
> Hi folks,
> 
> I've just posted a fleshed out version of the proposal that MSJ
> made a while back of allowing a body to recall its members. Here's
> the rationale:
> 
> This document proposes an alternate structure which is designed
> to deal with just egregious cases (e.g., total member checkout,
> major misconduct) but is also faster because it doesn't involve
> spinning up the nomcom machinery (twice, once to recall and once
> to replace). In this structure, the IAB/IESG would vote to
> expel the offending member with consent from the other body.
> The rationale here is that the body themselves is in the best
> position to know when a member really needs to be removed.
> 
> Thanks for reading!
> 
> -Ekr
>