Re: [Rfced-future] Model proposal

Martin Thomson <mt@lowentropy.net> Tue, 07 July 2020 04:19 UTC

Return-Path: <mt@lowentropy.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 BE8E83A07B1 for <rfced-future@ietfa.amsl.com>; Mon, 6 Jul 2020 21:19:04 -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=lowentropy.net header.b=DJ4DU1WA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=b4Xfz5aH
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 szhFh5OXhj9H for <rfced-future@ietfa.amsl.com>; Mon, 6 Jul 2020 21:19:03 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51D613A079D for <rfced-future@iab.org>; Mon, 6 Jul 2020 21:19:03 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 924055C0136 for <rfced-future@iab.org>; Tue, 7 Jul 2020 00:19:02 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Tue, 07 Jul 2020 00:19:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=pMzoTrU6SpIfot3RIftU/aAj6i003/a j8A8798+GzuY=; b=DJ4DU1WALTGoIwV3TNydfbpU7uvZ7MhASgUtyAe5cFzg+qo 1Ymio+49t+Czf/wNw1y/BXAyvEI4yxYya1wMx0dKUSeYDUaQWGNLQhGVIQDlLK7j Uv6uYgYyNbc4wnfyWKluwrtyDja/4d2NvA8MAY4Q2rgt14igDULo/h8g70iXvDoG XdhjGBNAeuA9NuzeEPgSp8e8h+pH8wAeTIjGOoxEtqAFaZFVi6qUIqhpZHFneX5I 8SHzlgk/apLUuNy0Djglczp/hUpmMifAXOqqbpESqII9m6kKUiXa6Zm0S1Ixbw0A c/ag7gaGXC1sXTvZB8E3BqXhEMoyUgxBJGbAOkw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=pMzoTr U6SpIfot3RIftU/aAj6i003/aj8A8798+GzuY=; b=b4Xfz5aHzaRZgJUauxmNyd GxwUohPz5JdP8UyVbIHCW3ybNLw5aRCGET5i+htVNqRqcZbH2shKHT4bAZSNVMsz gH+2Qo7yxIUQiFezqKJGmORImNvdKgJpQ5qrm6NSxPuu4+wy0O1V3UAhu43VKPqH Xcb3Uwp7wFIm/LqkIoH3+9qr5Ghl6a85hVir4/NRtI9+r3pRhqMq7paixXgEWUbc yMSVJcgTLHt/KqH5ARnXRERphbMBFuJpU0zk1XxHLFVHtPjwRU0Xb3EUvngY2+fZ GJbmClaNmBPJaRxo/JkuLXoTsq6EYeWgxc6o+4CntZuvfuMMaJ1tjpMCwx5rmLeg ==
X-ME-Sender: <xms:tvcDX5ejtmsDeOTfMQvJTbSMPGSGsibdd7o-RNlDuFk20FJGJsPDRQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeggdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:tvcDX3Nt5_w-ZN1gMY_Y6-rCLJbIs1G48KUuZW3iatIx1V-TvO23zg> <xmx:tvcDXyhEQzIwGJ54NIwhxvMWIEZvTLL40KbNRa91JcVMc0oVvHvg2A> <xmx:tvcDXy9ho5-rxN0QNCHkTyv2mhJd84Wm4E1XWDKn-r6XkLgfvzHkJQ> <xmx:tvcDX-OPKtNu6CUImHZZR9Vm1Y20zhVQ5xg8PRd_-YPt2wfYeTRa-w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 45C9FE00B3; Tue, 7 Jul 2020 00:19:02 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com>
In-Reply-To: <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com>
References: <d4d1cd2d-6df2-4cb4-b63a-f9bba45b48c0@www.fastmail.com> <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com>
Date: Tue, 07 Jul 2020 14:18:42 +1000
From: Martin Thomson <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/1pFXtOsj6LkV8Tm7xVQ6WUmDIOs>
Subject: Re: [Rfced-future] Model proposal
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: Tue, 07 Jul 2020 04:19:11 -0000

On Tue, Jul 7, 2020, at 13:14, Brian E Carpenter wrote:
> The basic problem is that this focuses rather narrowly on the RFC 
> production process and short-changes the strategy issue. 
...
> So your proposal [...] is a radical change that abolishes the Series Editor role and leaves 
> this set of worries on the IAB's plate, but without having a senior 
> professional with relevant knowledge and experience in charge of the 
> community consultation.

I think that this gets at the crux of the matter, so I'll address these together.

Yes, this proposes that we allocate fewer resources to the strategy function.  That is based on my experience with how much actual strategizing was performed in the time I followed this process as opposed to other things.

In my time on the IAB (and just preceding it), the bulk of time spent on "strategy" was spent on the v3 format, though there were other things like minting DOIs for RFCs.  These strategic items did not consume inordinate amounts of IAB or RSOC time then, even though the v3 format was a relatively intensive process at the level the work happened.  The IAB involvement was, as you might expect, executive level: we determined whether the process was functioning and approved the outcomes.  What dominated RSOC time was largely related to operations - or execution of strategy - reporting on document processing, monitoring costs and workload, discussion of tools development, and so forth.

I do recall several lengthy discussions about the number of authors on a document, but as these were recurrent and inconclusive, I am of the view that these are perfect for a working group to strategize on.

So I don't see this shifting more onto the IAB plate, either in terms of time spent or the extent of what we as a community might be asking of the IAB.  On the contrary, separation of operational duties from the strategic allows us to properly scale the resources we dedicate to each task.  As operational matters dominate, then finding a lightweight process for managing strategy is best.

Cheers,
Martin