[Rfced-future] Style guide and other non-strategic things ** Consensus check on part of Issue 12: Is the person an advisor (RSA) or an Executive Editor (RSE) **

Adrian Farrel <adrian@olddog.co.uk> Sat, 28 November 2020 11:04 UTC

Return-Path: <adrian@olddog.co.uk>
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 ADC783A0A87 for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 03:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qXToPEgnXFxZ for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 03:04:47 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 A5A793A0995 for <rfced-future@iab.org>; Sat, 28 Nov 2020 03:04:46 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ASB4eJj031478; Sat, 28 Nov 2020 11:04:40 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3115F2203B; Sat, 28 Nov 2020 11:04:40 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 1C1E82203A; Sat, 28 Nov 2020 11:04:40 +0000 (GMT)
Received: from LAPTOPK7AS653V ([195.166.134.111]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ASB4cO1012049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 28 Nov 2020 11:04:39 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eliot Lear' <lear@cisco.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org
Date: Sat, 28 Nov 2020 11:04:38 -0000
Organization: Old Dog Consulting
Message-ID: <058501d6c576$43e4cfd0$cbae6f70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdbFdkHy85U6SeOtQl2OgLR5tlLUrw==
Content-Language: en-gb
X-Originating-IP: 195.166.134.111
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25816.007
X-TM-AS-Result: No--11.859-10.0-31-10
X-imss-scan-details: No--11.859-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25816.007
X-TMASE-Result: 10--11.858900-10.000000
X-TMASE-MatchedRID: Eouh3vgZL4pq0U6EhO9EEyEyJ8xFEVolkW0zU11KKK07S7kQJT05JFiq Ayk7LkbkVhi48c2D9TeBRNVuc6Ppa226mUgLn3m/jrcVcgNMnovg02I3oyGU8CATiLvsSv4cDE1 Y/wJPx0sqegugNzsJfXH5R0bnYPNvhnBMPbxjCXR9r3RiYxSnPct3zHe6QppeIFWQH/JudNgqdH ODFD1EcnKvZBcntMqp9ims4cVMXfI6k8DwKL1tBIxwx0FSBgmNAp+UH372RZWWX300fYYVq70R7 AVPYalKmmgWMJS+ZT66j782+DQgoWl4Bykl/FQe2bpX2XJNwqEEa8g1x8eqFwg2kgWdt3qaP1P+ cNLm2bhuG10X5NZAwIlDrJWpFiaIp/RCY+priR6h4ILTlgBL0fg/s23WPBIpUHcBn70iJQfj9MX Trwp7Rfi/h8b7a0vRZV33nMkX4spvN14bTs89YPlZlPYYWH6d4B4Qje1seFVawoq5zq9PrNNZnq bwOWHjEuJtD6Cp80OjXgj0HIY8Aoxpy4UOhqKryf21YeIsPYYHmzHO3TfA+MuSXx71bvSLZshp/ ob4pluRkwGirjQk298fGcd5SSodJie+OrUoVcdgqbvjZaUg3gHgke2JqaQs3SL+X3YJA7WYpuG7 kpoKR9xQHjHEE9Oi6QWSh/rmuC3X/CwwaUemurXkpFHAEbgzF9s8UTYYetVrvf5eVgMu7MqEPxI kcXd02kAb/mrv4wtftuJwrFEhTbew1twePJJBKzfM9B6IRt76C0ePs7A07YVH0dq7wY7uGf3MS5 o4yLfX7YH+OGOLJH2yHnX4/lCALf3HBTG3pBTitqfCydAvbg==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/UBQtT8Fu7ZCDh525R5eRVc_PIa0>
Subject: [Rfced-future] Style guide and other non-strategic things ** Consensus check on part of Issue 12: Is the person an advisor (RSA) or an Executive Editor (RSE) **
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: Sat, 28 Nov 2020 11:04:50 -0000

Tweaking the subject line since I *think* he have travelled out of the "strategic" zone.
That is, the style guide is something with long term effects, but its implementation is very much document-by-document.
Let's take this a step closer to the everyday...
The RPC edits a document, the authors object to one of the edits claiming the RPC's understanding of the English language is incorrect: who arbitrates or makes the final decision?
I can be happy with many answers to that question, but would point out that historically, someone has been paid to do that work.

There is, IMHO, a difference between having a go-to backstop who ensures consistency and is responsible for decisions, and having someone to whom you can go for advice. In the first case the RPC is paid to try, and the backstop is paid to hold the line. In the second case, the RPC is paid to hold the line, and someone is paid to give advice. 

It's a small thing, but it is a realignment of 'powers' and should have a consequent redistribution of financial resources.

Cheers,
Adrian

-----Original Message-----
From: Eliot Lear <lear@cisco.com> 
Sent: 28 November 2020 10:12
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: adrian@olddog.co.uk; rfced-future@iab.org
Subject: Re: [Rfced-future] ** Consensus check on part of Issue 12: Is the person an advisor (RSA) or an Executive Editor (RSE) **

Good morning/evening both of you,

> On 27 Nov 2020, at 21:37, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 28-Nov-20 05:46, Adrian Farrel wrote:
>>>> I found this just a tiny bit ambiguous. I think that, in the context of the subject line, I can work it out. So, to be clear...
>>>> 
>>>> • The chairs think that there is likely rough consensus that role of the chair and the RS[EA] should be split.
>>>> 
>>>> • The chairs think we have consensus that the RS[EA] can raise issues to the strategic group
>>>> 
>>>> • The chairs think there is likely rough consensus that the RS[EA] does not make strategic decisions but that those are decided by the strategic body
>>>> 
>>>> • The chairs think there is likely rough consensus that the RS[EA] does not direct the RPC/REP.
>>>> 
>>>> Right?
>>> 
>>> Right.
>> 
>> Good, then I'm OK with the first three bullets, but unsure about the last one. It covers a rather large area since there are number of things on which the RPC need advice, guidance, and direction per the helpful email from Sandy.
> 
> I think there is some ambiguity about the word "direct". Does it mean "give orders to" as in "the policeman directed me to put my hands behind my head", or "give authoritative advice to" as in "Heather directed Sandy towards the new edition of the Chicago Manual of Style"?
> 
> If the former, I'm sure bullet 3 is correct, as orders come from the customer, which is the IETF LLC. If it's the latter, I'm sure it's wrong.
> 

Yes, just to be clear, we are talking in the negative here.  So… “The RS[EA] does not direct me to put my hands on my head” ;-) or perhaps more apposite: “The RS[EA] does not order the staff to take specific actions.  That person may offer guidance in specific situations, but is not in the chain of command.”

Is there general agreement on what I just wrote?

As to the style guide, perhaps that’s a separate issue or a good more-than-hypothetical to work out.  Is it maintained by the RPC with guidance of the RS[EA]?  Is it maintained by the strategic body?  Is it maintained by the RS[EA]?  Does that need to be specified here or by the strategic body?

Eliot