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

Eric Rescorla <ekr@rtfm.com> Thu, 16 May 2019 13:52 UTC

Return-Path: <ekr@rtfm.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 C20A11200F8 for <eligibility-discuss@ietfa.amsl.com>; Thu, 16 May 2019 06:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 jHmunyHPtOpd for <eligibility-discuss@ietfa.amsl.com>; Thu, 16 May 2019 06:52:12 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 ABDF8120176 for <eligibility-discuss@ietf.org>; Thu, 16 May 2019 06:52:11 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id h21so3135033ljk.13 for <eligibility-discuss@ietf.org>; Thu, 16 May 2019 06:52:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6Xdbxl5cMH8HUDIt2S+6Wkto2PmC0RrFJaCUREP8QiI=; b=WEcG2wmbBVFHxisUHwo6wL05FpNiLCqvZw/4L9pBIzo54HFpTJZ3dnAd6tp6114FmH Ir/yUoGWK/1ALei6RntO3if4SKX26+x/LXO84qVZxbOGWGCO1huce2LqimqVKWpFnVjZ jLUpfJk30rV4hf3wLNBZC9YIZ5yjbpt9WloNseMXoP1PL0judf7/ibPT7r+CFo4YR/fc +wbYiNWhrtqwZzr/EEfSHF08L/cfqq6l1Mrz4H17nW8hGWUPbOR/Xuagwch1RlT4t6r3 lmGZqGd/hwuCeIWgqe8ofn44RTrHL4vIod3I2qoHzPhXrAO0bDiCGd/iVkRaEWtBZPJK OATA==
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=6Xdbxl5cMH8HUDIt2S+6Wkto2PmC0RrFJaCUREP8QiI=; b=hF0HMSYDCyucduWXD0FUVpBiMCeTdyWfxME3RUYPUXMCLo0444zKFQ2WQJimm1/QyX BBR5sKnfVy74dj8odA169/FbitYMalCCFxARU7b64HFBMxhTBDbfuxayVc2yWORL58ZP BOX+VwMoYBuJU+4aRAaAqLdSEvzn39ks20ed7DiqkPnNj+SRLUiJdA2sX/HDCFiQtizp vbEGdODuPtmD6AJAxT7Y01Yhr/Y6qw7b/3v3EwARI672Kk9Mz+e6Fwkvb7jr0rn5LDds Ip15uImuvTQ0pP3xlsSVeHmDvxBshYhtrb5eacaNg7D7LR4WhFsAPDF2KNrjNMT8/Fw3 JY0A==
X-Gm-Message-State: APjAAAW9cMyDJ2SrR4XEzCMEVSb74InOWaSYmA4yb3zw6kVl6tJ3u1g0 69xogsr3k8aJ95WNvqyCudirGqvHzamcracRTqftfPWPtvA=
X-Google-Smtp-Source: APXvYqw+6Sk8eKBs7CFWmeZMQJTch0Wvq7a3Q0NBlI/c0tbFOvg0KGIH6sMqV67RmmXG4Nd5OjX66NOi0QPLlU4hOZw=
X-Received: by 2002:a2e:206:: with SMTP id 6mr21891539ljc.59.1558014729959; Thu, 16 May 2019 06:52:09 -0700 (PDT)
MIME-Version: 1.0
References: <CABcZeBNMorOsoyaga2Axh1285ps345GGNjtBYy7K84qhNS3FQA@mail.gmail.com> <187912b7-467f-2f57-b059-89c2e92280cd@joelhalpern.com>
In-Reply-To: <187912b7-467f-2f57-b059-89c2e92280cd@joelhalpern.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 16 May 2019 06:51:34 -0700
Message-ID: <CABcZeBPS_Homp_YhnYq3iFuD7WHd1bfO_AoDLog4y72YG=XcoA@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="00000000000088d0280589019250"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/8SEU3cgd1uewJmP6J8smxNO9-ZQ>
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:52:14 -0000

Hi Joel,

Thanks for your comments.


On Thu, May 16, 2019 at 6:32 AM Joel M. Halpern <jmh@joelhalpern.com> wrote:

> 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.
>

I hadn't thought of this. I think this generally points to a point of
confusion
in this document about the role of the  appeal to the confirming body,
namely
is that appeal supposed to check that the expulsion was good or that it
formally followed the rules?

I tried to follow the precedent of 7437, which is basically to specify
voting
rules but not allow decisions to be made on any basis (for instance, here's
the text about confirmation in 3.7.3):

   The confirming bodies conduct their review using all information and
   any means acceptable to them, including but not limited to the
   supporting information provided by the nominating committee,
   information known personally to members of the confirming bodies and
   shared within the confirming body, the results of interactions within
   the confirming bodies, and the confirming bodies' interpretation of
   what is in the best interests of the IETF community.

The text around recalls is similar, just requiring a "justification".
But perhaps that's not the right way to think about it?


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.
>

I don't feel strongly about 2/3; it's just a common supermajority level. If
people
thought 3/4 was appropriate, that wouldn't be something I would fight about.

-Ekr


> 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
> >
>