Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 31 March 2020 20:55 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 13C503A0849 for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 13:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=cs.tcd.ie
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 1KrvUbIiFihd for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 13:55:16 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2777B3A0848 for <ietf@ietf.org>; Tue, 31 Mar 2020 13:55:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A30A2BE20 for <ietf@ietf.org>; Tue, 31 Mar 2020 21:55:13 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85cLy4jBRZ_Z for <ietf@ietf.org>; Tue, 31 Mar 2020 21:55:12 +0100 (IST)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E62F7BDCF for <ietf@ietf.org>; Tue, 31 Mar 2020 21:55:11 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1585688112; bh=oJdNgpmPGJnmQh89F2i0GtF7CK6VMIrt4eNf7+DNWGY=; h=References:To:From:Subject:Date:In-Reply-To:From; b=btMiydbCVNsuRA80AI4BBA20lO9vYO+QAgoVUG3KvZ+3DrQpPdTo2Ehg3kpCJ4oSG 92OPuTbuDH5rBp6RUyBRPoQ8yyPiTu/UPvmLLV9YXQFDnQwx+K4dSpnW4r/8JCaen2 Icfewqu3e4rc0vvwsXYjkahEcytU/sHaxNPIKMCE=
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> <0E3AE8F4F693BE011BBF77F8@PSB>
To: IETF <ietf@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Subject: Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
Message-ID: <e245c096-2449-858a-2ed9-097589fa7864@cs.tcd.ie>
Date: Tue, 31 Mar 2020 21:55:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <0E3AE8F4F693BE011BBF77F8@PSB>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="Ss6n5sVvcURZjdS9K9HaZQAqX5VznYYjW"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZVHDrkevOfdASLM5YnNlDjYosG4>
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: Tue, 31 Mar 2020 20:55:20 -0000
Hiya, Not directed at or to John only, and this is just from me and wasn't discussed with rest of the IAB... On 31/03/2020 05:58, John C Klensin wrote: > if > the "future development" effort (when did it change from > "evolution"?) starts off with the same level of distrust that > characterized some of last year's discussions, clear and useful > results would seem rather unlikely no matter how much effort > Eliot and others put in. That's a pity and I'm sorry that we didn't decide to explain how we ended up where we ended up. Not grokking that we needed to explain ending up with one chair was an error, and one I was part of. Apologies for that. It's difficult to say much more though as this was a straightforward IAB appointment aka personnel decision, so I doubt that we'll be able to satisfy Mike's query really, but fwiw: - As far as I know there is no IAB skullduggery related to the chair selection going on at all. I know that's a bare assertion to just trust the IAB, and in a situation where that's far from a given, but I did say fwiw;-) - Please bear in mind that there were shifting logistics as the IAB was processing the feedback. At one point we were mostly focused on ensuring a session could happen in Vancouver with a non-IAB person as chair at the front of the room. That of course was OBE in the end, but did factor into how things played out. (Please also believe me that that says nothing about the capabilities of any of the folks who volunteered, I'm only saying that there was a logistics aspect.) Again, I'm sorry that it's kind of impossible to say more about this, hopefully those of you who've done IETF personnel stuff might be able to understand that opening the kimono at all is just really hard. And as Mirja has said we'll be getting a co-chair for Eliot - hopefully one positive outcome of this thread will be that people consider again taking on the role. Lastly, (and again more in hope than in the expectation that people will just believe in the IAB;-), every indication that I've gotten tells me that the IAB collectively do want to support, but not control, this activity. I do expect individual IAB members will get involved (incl. me) but there hasn't been any collective IAB attempt to put a thumb on the scales that I've seen. Cheers, S.
- 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