Re: [Rfced-future] ** Consensus check on part of Issue 12: Is the person an advisor (RSA) or an Executive Editor (RSE) **

Eliot Lear <lear@cisco.com> Sat, 28 November 2020 10:12 UTC

Return-Path: <lear@cisco.com>
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 383963A09CF for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 02:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 KgFXNs611Asp for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 02:12:03 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48A7A3A09C4 for <rfced-future@iab.org>; Sat, 28 Nov 2020 02:12:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3323; q=dns/txt; s=iport; t=1606558323; x=1607767923; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=8c9e/3Rix61IIbtAHTuJ9ho6qt+AnW70ipA9oXvdGe4=; b=jz4VacLayfI1kUfUwvDCaTNNtzzDAdc1IwauKytkRY6XVLiluxRxXcvE BUMGisFqrY0kyalZyvu+jWpQh2sAZy6ds8nWWNT/5+Eubj7UsWvkoVevk C0LecGNylTq2H04sT7QOgQukY4mha3KpYfXu3X3pV6lH2sWwuWG9llpfJ g=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BdAAAXIsJf/xbLJq1iHAEBAQEBAQcBARIBAQQEAQGBfQUBAQsBgimBSwEgEi6EPYkFh3onihaQHhSBaAQHAQEBCgMBAS8EAQGESgKCKiY2Bw4CAwEBAQMCAwEBAQEFAQEBAgEGBHGFbYVyAQEBAwEjVgULCQIYIwcCAiE2BhODJgGCVQMOIJMTmxJ2gTKFV4I4DYIUEIE4AYFSjAiCAIE4DBCCJy4+ghuBbgESAYM4M4IsBJxgmzNXgnqDHYE3iyyGFYUXAx+iFKFfjwuDagIEBgUCFYFcATNncDMaCBsVZQGCPj4SGQ2OWI4TQAMwAjUCBgEJAQEDCY9sAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,377,1599523200"; d="asc'?scan'208";a="31472920"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Nov 2020 10:11:59 +0000
Received: from dhcp-10-61-102-28.cisco.com (dhcp-10-61-102-28.cisco.com [10.61.102.28]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 0ASABw9Q018601 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 28 Nov 2020 10:11:58 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <108359F4-D858-4617-8AC7-3ECF4809833B@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_ABC6D8D8-74BC-496E-A5B5-F153B1AD0AE4"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sat, 28 Nov 2020 11:11:57 +0100
In-Reply-To: <457f9ee9-be00-0aa4-dc1a-5cb2fc003b16@gmail.com>
Cc: adrian@olddog.co.uk, rfced-future@iab.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4A34B713-E013-4A36-9296-694F07EC5AC5@cisco.com> <04e901d6c4da$192afa90$4b80efb0$@olddog.co.uk> <AADEFD92-5873-4D0E-A798-1C31328FF8BC@cisco.com> <04f701d6c4dc$e7968960$b6c39c20$@olddog.co.uk> <457f9ee9-be00-0aa4-dc1a-5cb2fc003b16@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.102.28, dhcp-10-61-102-28.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/XM7VvI0fZWjumyTqRytY82e8RNk>
Subject: Re: [Rfced-future] ** 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 10:12:05 -0000

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