Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
Michael StJohns <mstjohns@comcast.net> Wed, 25 March 2020 22:48 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 3DFF73A0DFA for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 15:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 MF9mQ0xIssdL for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 15:48:18 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 80F793A0896 for <ietf@ietf.org>; Wed, 25 Mar 2020 15:48:13 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id HE6AjayZ4D4wEHEomjJ8dU; Wed, 25 Mar 2020 22:48:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1585176492; bh=1QEWCA+8akxHgHFwCLzyhY9vU/WGGrnZjEfcbLEww7g=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=nydu6lOngV5gv1ODjADHimsbvtlvqbYtzdTkK+W/U4F15UnWo4zEqsXeyu+nrlbGU wwe97jLN6PqVbx2tx/inxmNBNLA++n4SjEh38YH/dAEFPDDWQzwKaizkfX1QCHPS6K 3c5PXCu/HuTUZaaUFQEghX+8O4YrbXv7F5DAYQnqd9KnD8r0NnFfntejUZRwdU0vIT 0LWXCJWt49sYO6OAm4+Z9jwtPwm5DVt1/jPATYnWYkyDiCZmtqypTKcSzCdFSVi7KV QAdv6mieqsW4kzZfvvCsZ9yEgmssx7BO7IYqEHQznlSaj4pOV6ZTvS8MH2PRpjZh6g PWd/lEdHCr4kA==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-19v.sys.comcast.net with ESMTPSA id HEodjzUgasMl9HEodjXMhN; Wed, 25 Mar 2020 22:48:09 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedugedrudehhecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucffohhmrghinhepihgrsgdrohhrghenucfkphepjedurdduieefrddukeekrdduudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduudehngdpihhnvghtpeejuddrudeifedrudekkedrudduhedpmhgrihhlfhhrohhmpehmshhtjhhohhhnshestghomhgtrghsthdrnhgvthdprhgtphhtthhopehivghtfhesihgvthhfrdhorhhgpdhrtghpthhtohepthgvugdrihgvthhfsehgmhgrihhlrdgtohhm
X-Xfinity-VMeta: sc=0.00;st=legit
Subject: Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
References: <158515861056.31362.1577145055370523251@ietfa.amsl.com> <06f0ef99-728e-1b41-0596-7b7286c29ead@comcast.net> <CA+9kkMBTb=Z2C5VJ1LQ6JoN0hB8OnmSdebkLHFhG+O-9F_Tv7A@mail.gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <2375d191-dd72-3e09-6417-5bcae5ba1d4b@comcast.net>
Date: Wed, 25 Mar 2020 18:48:03 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <CA+9kkMBTb=Z2C5VJ1LQ6JoN0hB8OnmSdebkLHFhG+O-9F_Tv7A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1FA941B06B546C65D58521F7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MoGjjZyadcTB3BT7mFIgsqUhUtc>
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: Wed, 25 Mar 2020 22:48:29 -0000
See below. On 3/25/2020 6:30 PM, Ted Hardie wrote: > Hi Mike, > > On Wed, Mar 25, 2020 at 1:47 PM Michael StJohns <mstjohns@comcast.net > <mailto:mstjohns@comcast.net>> wrote: > > On 3/25/2020 1:50 PM, IAB Executive Administrative Manager wrote: > > The IAB has selected Eliot Lear to serve as chair of the RFC Editor > > Future Development Program [1]. > > > > To satisfy my curiosity - could the IAB give us some idea of its > thinking in selecting Eliot? > > > The IAB followed the same process it uses for many appointments: it > solicited volunteers (and then extended the deadline for volunteers), > asked them for statements of interests, in some cases held > conversations with them, and solicited comments from the community. > The details of that community feedback and those discussions with the > candidates are confidential, as are most personnel discussions. Let's stay away from "personnel" discussions (and I'm not really sure this qualifies as such - but we'll go with that for now), and instead go to what should be public information: 1) What experience in Publishing and Editing does Eliot bring to the table? 2) Why didn't you appoint co-chairs as appeared to be the community desire? I can see at least two reasons to do so: a) To spread the load and ensure the program is successful, and b) to provide for more than one point of view in the chair position. This is a question irrespective of the "personnel" discussion of who you might appoint. E.g. tell me the things that argued against appointing multiple people? Later, Mike > While I appreciate Eliot's attributes, I would have thought Neville - > who has substantial experience as the ISE, or John - who was a > substantial contributor to the original process that led to us hiring > Heather or some combination of the two* would have been a slam dunk > choice. I may not have all the details on Eliot's experience > related > to editing and publication. > > *AIRC, there was substantial desire expressed by the community for > this > program to be led by co-chairs rather than a single person > > > This selection was made by the outgoing IAB > (https://www.iab.org/documents/minutes/minutes-2020/iab-minutes-2020-03-04/). > The next IAB may decide that a second chair selection round would be > useful, and there has some discussion among the large group (outgoing, > ongoing, and incoming) on that point. > > Feel free to take this as a question (perhaps the first question) for > the Plenary. > > > regards, > > Ted Hardie > > Mike > >
- Re: [Rfced-future] Eliot Lear to Serve as RFC Edi… Eliot Lear
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Ted Hardie
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Leif Johansson
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Salz, Rich
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Jari Arkko
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Brian E Carpenter
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Salz, Rich
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Eliot Lear
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Wes Hardaker
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Wes Hardaker
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Mirja Kuehlewind
- Re: Eliot Lear to Serve as RFC Editor Future Deve… John C Klensin
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Brian E Carpenter
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Stephen Farrell
- Re: Eliot Lear to Serve as RFC Editor Future Deve… John C Klensin
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Stephen Farrell
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Wes Hardaker
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Wes Hardaker
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Michael StJohns
- Re: [removed] to Serve as RFC Editor Future Devel… S Moonesamy
- Re: [removed] to Serve as RFC Editor Future Devel… Wes Hardaker
- Re: [removed] to Serve as RFC Editor Future Devel… S Moonesamy
- Re: Eliot Lear to Serve as RFC Editor Future Deve… Mirja Kuehlewind