Re: [Rfced-future] Scope and IETF 108 proposals

Mark Nottingham <mnot@mnot.net> Mon, 29 June 2020 00:23 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4F7C3A0FE4 for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 17:23:50 -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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=KXqkQ2ga; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Sc3iVq2L
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 0D-5AFCONFyl for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 17:23:48 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99F823A0FE3 for <rfced-future@iab.org>; Sun, 28 Jun 2020 17:23:48 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 966A04BE; Sun, 28 Jun 2020 20:23:47 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 28 Jun 2020 20:23:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=b 5Bhn7M+y6c7ZbaqVbGY/5VR6Cc+1fKnUqjVaLolBaI=; b=KXqkQ2gafQjZGaIhs lEDxLgKU4hyaxOK92FcGlfcA0RFDzRUbYgzGnlGsKMwXySRrXLu3WB9T2OsM+bxY vWs+84jbjX2qu9L5yxG0sAqpQjgg/iK7P614Ova5s9B13KNQsLRbIkQ0MnBff/cl zzgo7zEwXpqC+guQJcnvAamMH9yjNKsZJPg90xUVxfSbYR7TQAHEDs+1CMOpprXH QaGWxc8YhfF0tsZGYrGssbLb9bZxwsXaYKzRVNMOV/jTyGJymU3jzzAYdVAAQLpq XL2oP7kCcnlfYg75b4swk7JEraCHFN/QrHar1fv3nQzwY1CLe/Meb8L2XRiNEGoi JfiuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=b5Bhn7M+y6c7ZbaqVbGY/5VR6Cc+1fKnUqjVaLolB aI=; b=Sc3iVq2LLKRhUrnxekHL6BbP0GAj9SOowPH4qnluXvRfZXJ+TaPoQFOzN f9GpdZc6PD5YL3wNwAGpRhaiQjy80UUBtaSuhCQJ1yBaPbr8CkZfx7OAEkJlgg/1 iQdOaYqqj5GJLcP/mtXp/bb7d2E3lX+rj9TRK1fgrrgoel5i0+GLH+ftZEr/LJyp y94PTB6EIXLSE65M4xjaKNPT/B4TFL95wMp/yPf6soIGOh+wHmO5RwuzIqFKKKSM hnn9l/9iXjC5f/mJ0U0kHwxuWA+VZnfbaRfrn0EwvuM8QsMnFCbhGOxbb1F0wTnP 9I03gs0/itbks6iI7k8hi1KuD1poA==
X-ME-Sender: <xms:kjT5XjPJtKUVV3mHbI5rZ7xT5wtC7i3ChSHH3VhY6_LMS7HwJsY9bg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudeljedgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepieetudduvdduffettdduvdeghedtue ehheejgeeltdelkeevgfffheefffeffffgnecuffhomhgrihhnpehivghtfhdrohhrghdp ihgrsgdrohhrghdpmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehud enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhho thesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:kjT5Xt-Yt_cFplTh4WrGbVKuuwphSu6h6ChkoFH7qF9UJIUk67MyXQ> <xmx:kjT5XiTJeLNoIUSCnB5DK1jDzcjHPccLIpefL5FHxF9jpfRyydxFNg> <xmx:kjT5XntoN9n4qavr4XUVn0CMxT4IKd1E4L2dJfqWCNlpvu1dZVvDjg> <xmx:kzT5XjHoJgTXWoXqQJW-LKNw334QpMGzaTVUnku_fagbp_7ERGQjmQ>
Received: from macbook-air.mnot.net (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 30E4E3280059; Sun, 28 Jun 2020 20:23:44 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <dc41e1eb-35c6-b678-65e2-db638f330018@nthpermutation.com>
Date: Mon, 29 Jun 2020 10:23:42 +1000
Cc: rfced-future@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EDDC9C7-BA91-4E18-AB1C-8E77E95627B2@mnot.net>
References: <62A4C70D-419A-4DE3-8A54-60EB2B064EF2@brianrosen.net> <8c626e3e-1700-46fe-90b3-26b9c1296788@www.fastmail.com> <1b6cf5e6-2c16-d839-08dd-d005d4fdbc60@gmail.com> <3678427d-6496-45c7-bd1b-14d7f860c971@www.fastmail.com> <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com> <cfd9512d-b61e-4438-9ce3-102f6ddaebe7@www.fastmail.com> <befe8914-996a-d4f0-f9ef-cc49d882839c@joelhalpern.com> <dc41e1eb-35c6-b678-65e2-db638f330018@nthpermutation.com>
To: Michael StJohns <msj@nthpermutation.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/v6IwXxsQNSwBecKl-Y8BYkBW5Ks>
Subject: Re: [Rfced-future] Scope and IETF 108 proposals
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 00:23:51 -0000

The suggestion was to have more than one more specialised role, not to promote 'leadership by committee.' This has been discussed a number of times previously, due to the very high bar created by the combination of requirements we current place on the position (as Martin mentioned).


> On 29 Jun 2020, at 10:14 am, Michael StJohns <msj@nthpermutation.com> wrote:
> 
> On 6/28/2020 7:50 PM, Joel M. Halpern wrote:
>> In my view, the reason we need a person to do this is that leadership by committee is essential equivalent to a recipe for disaster.  And I do think we want leadership. 
>> 
>> Yours, 
>> joel 
> Strong +1 here.   One of the reasons for having a senior person in this role is so that the attention paid to the strategic evolution of the series does not wax and wane based on the current hobbyhorses of the leadership or their companies,  or upon other loud voices.   I have no problems with those voices influencing strategy, but I have strong problems with those voices directing strategy - especially if they change directions every 6 months or a year.   
> 
> We've had at least 4 people with the "rare and difficult" [Aside: difficult?] combination of attributes so I'm not sure where Martin is coming from here.   It may be that he doesn't agree that those are the right attributes for the role, but that's a whole other discussion.  I would expect with some luck, and with an IETF that respects what an expert can bring to the role, we will be able to find someone who won't run screaming into the night after they meet us.
> 
> Mike
> 
> 
> 
>> On 6/28/2020 7:47 PM, Martin Thomson wrote: 
>>> On Sat, Jun 27, 2020, at 13:01, Nevil Brownlee wrote: 
>>>> I've updated my Internet Draft to include a suggestion of what an RSEB 
>>>> (RFC Series Editorial Board) could be structured. Take a look at 
>>>> https://www.ietf.org/id/draft-brownlee-rfc-series-and-rse-changes-01.html 
>>> 
>>> This is very much not what I had in mind.  We should not insist on having a role that depends on finding an individual with a rare and difficult combination of attributes.  And I don't think that you can support that function by taking a program with open participation and consensus processes and reduce that to 5 people (+stream manager ex officio) who are responsible for approving strategy. 
>>> 
>>> Perhaps you can start by explaining why you think we need to have an individual perform these functions. 
>>> 
>> 
> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future

--
Mark Nottingham   https://www.mnot.net/