Re: [Eligibility-discuss] Questions about I* bodies removing their own membership

Warren Kumari <warren@kumari.net> Sat, 02 November 2019 15:16 UTC

Return-Path: <warren@kumari.net>
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 67851120125 for <eligibility-discuss@ietfa.amsl.com>; Sat, 2 Nov 2019 08:16:06 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 y1Es-QmXuEpZ for <eligibility-discuss@ietfa.amsl.com>; Sat, 2 Nov 2019 08:16:03 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 160B7120091 for <eligibility-discuss@ietf.org>; Sat, 2 Nov 2019 08:15:13 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id e2so13509076qkn.5 for <eligibility-discuss@ietf.org>; Sat, 02 Nov 2019 08:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=127wRG1wf369KXaUu1Z8RGbnFX4Hlc2E8qa8y20RdvM=; b=KeysyjOhodlqQkbCesZm7ryGHGC32Kobx7eQGj6NGNl6kkCYKk7yigNQpd74HghvnX Zl9X8J5UsX1Z8yY72MW8NPBoephnYqFKEfZwER/iNxP8Z1AC16cchlelgYl92g/QaHCn KxkMgnwzwZPuDB2tXm+1RkMDG15GsMJH7z4FU8lr3E5Y20phKK5cOMDqDvAtThKEpYra nHDdVjq0YKns04fkyN1cupVcXiglXvHdttXzr0UNbcx+cafiaZUSF8YitjN8x6RGxC8B FfIWkf5d4ZzwYCIVQ/6H21x0cMGF1pIL6YM47aBUXzpEbbHkSU/6wbfKHy5ScoryHwOp FbaA==
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=127wRG1wf369KXaUu1Z8RGbnFX4Hlc2E8qa8y20RdvM=; b=uiiG1H0vPDB8VZ/3B6OGilINb1tnnQhnIZLysTHiTXrTpZcOkSZIfyzu/aM8GBiIMQ 688JGSDwxE1KYrnFdD35jzxrilBnuzBpTDYUQv/fnmTc8f/UbVUZHSqdGOb2oGc09wCI aLa0eYcCqJEeUVbMDWAY3yacxHjb1v48q6nsgPBQ/Hox0UIiYcWYHCNBZvtA3jxggWWK ASRd3N7f5RgKP/3AYHO09PyuBCPQRyByqk7tKmoUMpvX1fK1fK/pYEMBFfdfdGGqg3YQ BURRIbDCOPVxh+RFBrvgJKDjhNUfq54yWQk+zQZd/bMBsyk2nJVLZ32iIO6ADHQKgT74 KOXQ==
X-Gm-Message-State: APjAAAVKM83cHcSlH4Tz56R8erne89IIFc90hK3Fxo3gX22luvG++MO8 30UqR1C9a5Le7yDVoOSnnWx3rT9zI9+/vdmjn4F3DvV7Adw=
X-Google-Smtp-Source: APXvYqzRuyIvNt5IO/rfrUx30oB1+Eq/o+mvyMn0zYlzXvQZ2HxsudYox4ns5/IZ93wSsdovO7Bs7f1UOI2p0TduHtg=
X-Received: by 2002:a37:b4c:: with SMTP id 73mr9794231qkl.37.1572707711626; Sat, 02 Nov 2019 08:15:11 -0700 (PDT)
MIME-Version: 1.0
References: <99234A93-2224-47F1-AA65-C71DC5DA3CD3@episteme.net> <69DFC9FF020C06F8353314B2@PSB> <BD6598AF5EC96F4BD8BCBAC8@PSB> <6.2.5.6.2.20191030005251.14fab888@elandnews.com> <A1ED83383C425799F1B1DEFC@PSB> <6.2.5.6.2.20191030072829.0cb52490@elandnews.com> <0C3D15B092B5FD83C03B88A3@PSB>
In-Reply-To: <0C3D15B092B5FD83C03B88A3@PSB>
From: Warren Kumari <warren@kumari.net>
Date: Sat, 02 Nov 2019 11:15:00 -0400
Message-ID: <CAHw9_iLKGQ3vD-nXy=iUB_25uMeEoPDS7cYVcrnwGjYLeyFuxw@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007cc4c205965e8c3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/kh4oOGvoTaADCupLxNiKcZcI61Y>
Subject: Re: [Eligibility-discuss] Questions about I* bodies removing their own membership
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: Sat, 02 Nov 2019 15:16:07 -0000

On Thu, Oct 31, 2019 at 12:25 AM John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Wednesday, October 30, 2019 08:34 -0700 S Moonesamy
> <sm+ietf@elandsys.com> wrote:
>
> >...
> > Returning the person who has been recalled requires the
> > approval of both a future Nomcom and the confirming body.  My
> > current thinking is that it is not worth figuring that one out.
>
> Actually, unless I have misunderstood the procedures, the
> sequence for a removal is
>
> (1) Petition is submitted to ISOC CEO (or, in the case of the
> Ombudsteam, a request goes to the ISOC CEO without a petition).
>
> (2) ISOC CEO appoints recall committee chair, who organizes and
> runs the request for volunteers and random selection process for
> recall committee members.
>
> (3) Recall committee figures out if the person should be
> removed.  If they reach a "yes" decision, the person is out,
> creating a vacancy.
>
> (4) The vacancy is filled, as quickly as possible, by the
> relevant nomcom.  Depending on when the person recalled was
> selected and the timing of the removal action, that might well
> be the same nomcom that originally selected the person who was
> just removed.
>
> If it happens to be that same nomcom and their conclusion is
> that, independent of the recall committee's conclusions and
> whatever the petition has to say, they were right the first
> time, nothing prevents them from reappointing the same person to
> fill his or her own vacancy.   For many reasons, including my
> not being paranoid enough to imagine a nomcom behaving that way,
> I think the odds of that occurring are small enough that I can
> agree with you that this is probably not worth figuring out.  I
> can imagine, but only with difficulty, someone who was recalled
> wanting the job back.  But it is not an issue about a "future
> nomcom" -- for two year terms, it would be either the nomcom
> that seated the person who was recalled or the sitting one after
> it.
>
> It was pointed out to me last night that there is one exception
> worth worrying about but probably not in the current context.
> At least for the IESG, we've had occasions in which the number
> of volunteers/ candidates for a given slot has been very small,
> perhaps only one.  If the recalled person was the only plausible
> one who volunteered for that slot and no further volunteers are
> found with to fill the vacancy, the nomcom might be faced with a
> question that has been raised on and off for years but never
> answered:  Given a choice between an unsatisfactory candidate
> and a decision to not fill the position and, presumably,
> strongly advise the IESG to rethink into organizational, area
> definition, and AD structure, it has never been clear whether a
> nomcom has the option of leaving the position unfilled.   But
> that issue is very clearly out of scope for this discussion even
> if we expanded to overhaul the whole recall procedure.



Obviously it depends upon the case, position, phase of moon, remaining time
the person would be serving, but I’d think that usually the WGs could be
reshuffled, the remaining members can lean a bit more heavily on
directorates, etc. ADs have taken vacations, been swamped with $dayjob, etc
and we’ve managed just fine... Most areas (other than Ops & Mgmt, which act
more like 2 areas that are joined together) have redundancy...

Being an AD to isn’t rocket science - much of it is common sense, reading
lots of documents and shuffling papers / administrivia.

The exception to this is the Chair, who requires skills which many of the
iesg cannot easily fill.

W


>
> best,
>    john
>
>
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf