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

Michael StJohns <mstjohns@comcast.net> Fri, 26 April 2019 21:27 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 A9A4812023D for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2019 14:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, URIBL_BLOCKED=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 ehiKJHE_-uOJ for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2019 14:27:48 -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 9CFA1120121 for <ietf@ietf.org>; Fri, 26 Apr 2019 14:27:48 -0700 (PDT)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-09v.sys.comcast.net with ESMTP id K3XFh3ueGNBGvK8NohIK7s; Fri, 26 Apr 2019 21:27:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1556314068; bh=Hl14pTIwTiuDObxH4IG3Ia+/OR0HiCAS5TXIXrR8kFk=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=MaUITG9BxYl1AgeuNY3Ko7L0knRoFPG80soak0/2oDGpnmYdfal6t/BeQKYINdgxs erePtuogzrM56UIcK3eHnG8V26zRR9Cj45YtSjFvUaehb4d0tY+7K7mJ26hjXLDUDu L7UNvmYgi3VDs9B7sKyIGLNaN/bdsmaTeYJQkD2ZAfdCNbGtEApLFsoT+2NAA8yPdm sRshpbJoEBMXAeehwWKqV20zNgItIp868RXR/7+A0SxKfDX8wobPoyZ/escIE2+e3A rqBjvrawnhti+y4BzymBDmx393BS1n6Ku79iU10D8RGA9uRwNNmcyLPityxpClB0Hl sLs/3daaFBEHQ==
Received: from [192.168.1.113] ([68.83.218.6]) by resomta-po-03v.sys.comcast.net with ESMTPSA id K8Nmhi4jXZo7dK8NnhqFfU; Fri, 26 Apr 2019 21:27:47 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduuddrheejgddtudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepofhitghhrggvlhcuufhtlfhohhhnshcuoehmshhtjhhohhhnshestghomhgtrghsthdrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepieekrdekfedrvddukedrieenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduudefngdpihhnvghtpeeikedrkeefrddvudekrdeipdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihgvthhfsehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedt
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: ietf@ietf.org
References: <CABcZeBNdaWU4wwOK_MnWC5hOr7Lu3osmC_6_KKxB5fHuHVHyTw@mail.gmail.com> <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net> <6.2.5.6.2.20190424095017.13cdadc8@elandnews.com> <51068F13-E90F-42A2-8AE2-627D5E18B145@akamai.com> <20190424201939.GM3137@localhost> <6.2.5.6.2.20190424134823.0c9faf68@elandnews.com> <20190424211123.GO3137@localhost> <6.2.5.6.2.20190424144539.0cabcde0@elandnews.com> <20190424234334.GQ3137@localhost> <11F97591808485C30AD98A22@PSB> <20190426150436.v4svwa67xja6267r@mx4.yitter.info>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <57985c27-490b-c2e0-6e7e-b3862e40ab32@comcast.net>
Date: Fri, 26 Apr 2019 17:27:45 -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: <20190426150436.v4svwa67xja6267r@mx4.yitter.info>
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/DBKMo-7xBAY9buZIl2KrcIEWwuI>
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: Fri, 26 Apr 2019 21:27:51 -0000

On 4/26/2019 11:04 AM, Andrew Sullivan wrote:
> Speaking selfishly, the procedure also imposes a burden on the
> Internet Society President to find and appoint a Recall Committee
> Chair.  As the incumbent who'd have to do that, my first problem is to
> write a job description, then to find a suitable candidate who has the
> time and motivation and reputation to do this.  Making this burden
> easier to impose on me at surprising intervals is something that,
> quite frankly, I would be inclined to resist were someone to ask me in
> my professional capacity what I thought.  That suggests to me that the
> procedure would need some additional modifications in order to make
> the changes practical, and once the worm-can is open who knows what
> additional red wrigglers will start moving around?

Way back when I wrote 
https://tools.ietf.org/html/draft-stjohns-alt-3777bis-00  - especially 
section 6 - to address some of this.  Basically, what I suggested was 
that the chair of the recall committee should be the most recent chair  
of the nomcom committee who wasn't currently serving on a nomcom and who 
would accept the appointment.  I also suggested that the list of 
volunteers for the most recent nomcom instance be used to select the 
recall committee (after being pruned of the actual nomcom selectees).  I 
proposed a model where the recall committee could be stood up in about a 
week and finish in either two or three.

There is no need to refer to the ISOC for any of this (seriously - 
"write a job description"?????  serious overkill), and  avoiding all the 
issues that you mention by avoiding the ISOC is a "good thing".  
Instead, work with known quantities and people and a pre-agreed upon plan.

Later, Mike