IETF Logo Mail Archive

Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair

Michael StJohns <mstjohns@comcast.net> Mon, 30 March 2020 21:17 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 8E97C3A1343 for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2020 14:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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 HUI1XzCa0Ggv for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2020 14:17:13 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 052B63A1341 for <ietf@ietf.org>; Mon, 30 Mar 2020 14:17:12 -0700 (PDT)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id J19YjqSPbQCNTJ1mRjcKEU; Mon, 30 Mar 2020 21:17:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1585603032; bh=U0YKeibox+XaABOR1puXhi9hhXrvI/55cnwRk+z/cGg=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=LKBdvrrq43J4MrqbyTjxsHDH+aSXPl827NB+4xrVeKu7JttlH5XhwicUMrK7nCB9c gVJQ5qehaAwVhLA0jcTbWx40rcopqAOVcWgzb8ZbBG3Xkvb8ccONGQ7FPSB4gEqVER vO2az/QbKZwLqxlvEI8jMXh1FDhY4KxjTq03vj6rzPyrEhA4T1gA1b6mU1phQxOdTV UYJ9t3ryhNOnhJTG9ss9T2WfF91h31M4zXbB0OXktND4ZdHaHTavnR6Ul2ufqVO6fE 3tdZzfGh67aDhHZ8ftksluDnWcWUO0+mVSPYmaKAv9uk3atmmg7aSMUd+iDoNHfCba P+qZ5PxQCcGiA==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-14v.sys.comcast.net with ESMTPSA id J1lUjar90QkuIJ1mCjTxQx; Mon, 30 Mar 2020 21:17:09 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedugedrudeihedgudehlecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucffohhmrghinhepghhoohhglhgvrdgtohhmnecukfhppeejuddrudeifedrudekkedrudduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduhegnpdhinhgvthepjedurdduieefrddukeekrdduudehpdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihgvthhfsehivghtfhdrohhrghdprhgtphhtthhopehtvggurdhivghtfhesghhmrghilhdrtghomhdprhgtphhtthhopehjrghrihdrrghrkhhkohesphhiuhhhrgdrnhgvthdprhgtphhtthhopegsrhhirghnrdgvrdgtrghrphgvnhhtvghrsehgmhgrihhlrdgtohhmpdhrtghpthhtohepfihjhhhnshdusehhrghruggrkhgvrhhsrdhnvght
X-Xfinity-VMeta: sc=-100.00;st=legit
Subject: Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Jari Arkko <jari.arkko@piuha.net>, Ted Hardie <ted.ietf@gmail.com>, 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> <2375d191-dd72-3e09-6417-5bcae5ba1d4b@comcast.net> <C6F6A4AB-3515-4E11-961B-66B87EDA995A@piuha.net> <b01bc927-e9e3-0b43-0247-aa4ebfc098e4@gmail.com> <ybl1rp9ipyz.fsf@w7.hardakers.net> <f1725be1-ccd6-423e-4ec7-9e34eb9c02bb@comcast.net> <yblpnctfu3w.fsf@w7.hardakers.net>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <f53f6743-674f-87db-a487-0b0d266c31b4@comcast.net>
Date: Mon, 30 Mar 2020 17:16:12 -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: <yblpnctfu3w.fsf@w7.hardakers.net>
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/e6tEY_Y8pm_E3zvopiYMwEfjN54>
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: Mon, 30 Mar 2020 21:17:15 -0000

On 3/30/2020 4:47 PM, Wes Hardaker wrote:
> Michael StJohns <mstjohns@comcast.net> writes:
>
>> Given that you were part of the outgoing IAB as well as the incoming
>> one, can you give us some insight as to why that didn't happen
>> already?
> I'm afraid that conversation was in executive session, and it would not
> be prudent of my to share any discussions related to the final decision.
*sigh* Let me try this again.   Per community discussion and announced 
intent the IAB should have come back with 2 or 3 chairs, or it should 
have re-opened the call for chairs.  Neither of these happened.  What 
caused that IAB to fail to follow the rules - again?
>
> Personally, I'm actually happy that we only appointed one chair, but
> probably not for the reason you think: this way, with the large turn
> over of IAB members, it turns out that the incoming IAB members will
> have a voice in potentially selecting a second chair.
>   

I don't mean to pick on you, but this seems to be retconning [1] what 
actually happened.  If this was the intent of the IAB, then it should 
have been announced and action taken transparently.

Seriously, if this is a mistake, say "oops", apologize and explain what 
actions are being taken to fix the problem.

Mike

[1] https://www.google.com/search?q=retcon

v2.23.0 | Report a Bug | By Email