Re: [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) **

Eric Rescorla <ekr@rtfm.com> Sat, 28 November 2020 21:52 UTC

Return-Path: <ekr@rtfm.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 DB60C3A0317 for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 13:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.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 ErkblU_x2PKg for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 13:52:10 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 949423A02DC for <rfced-future@iab.org>; Sat, 28 Nov 2020 13:52:09 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id v14so12632412lfo.3 for <rfced-future@iab.org>; Sat, 28 Nov 2020 13:52:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IeTaX8GzuFcTKnIQgzM/p08hVc4MgiT4DehWwZZx/8I=; b=eK6qMcLBkEjqAI6QruxDdny1XwmmUyclTBPLRpvyq8Uz3NZoJ56a7YcqOXFhlla1nv BJRniNQQChZUp+Ts/e5ELYBlZd7m8UDI54Y0C/1uRZK8XmDCHa4TnlY/3AA4Afi8mFME M+3TTyjZIbZm7ZO0Lj/Oo6WLSGNn2xT4dDwdCYY8TwJEzt2BJ5CnDR5lTZnk7HtAgt4z 5f3YCp2oQKKPJGGF0Ju8Ry/6whXFIipOLl/jfK7obWP5CuUgwz2k1jRS4cp5DOWX8txd BXssIJy/a9Gq0MzPPFPoiSKwQmOWII8XckOz4wBkQehUR2pRaKVLftCSk3wyLW4Ww0b0 MoDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IeTaX8GzuFcTKnIQgzM/p08hVc4MgiT4DehWwZZx/8I=; b=DyvlNnT9uZ+eI1EEKPqtxMGf+roitA3TyTsSEnKW3jX53jxcezhqz8m9FfmCKOnax3 rm9cyOav2AbfbH1qCYNWHfOoytqYuF1+IFsc+JgnlP69cC/b1hKApDru/iQJAwRBJEOh ihyGkPABy6+w4fgzS+4G/90W69G/TYfhHmdcmOhhceEh0PWHlHDAxQK2oRrBjRZfkjCX acwu7xa3+EiLdDaSW2HPtS1fte3tttaPo78LLOc9W+dK95fmyLEU2W6HTTqkVrZigcvy TEE9xmtkyHMj2ORDzwlqJuji52COGLnN+9WUzhHcZ+hQT2Fi/wtF4bI6Ep9gpPry3aL4 wZMQ==
X-Gm-Message-State: AOAM533gpI/gg4HvsY9YKY/xl7QdGMxM4EBN9/U+hk4pwNzKZ0ll6BNf d6hzIilLRZl3HvZCnS/RHrE0JqKM2ya3Djc49ZFFYA==
X-Google-Smtp-Source: ABdhPJxhYYEsxuEbEJ8T7gCwEZBT1H6MZl+i1dNgQbz/T2CCU6mEynwFPl8SC4UoF6CgK4etbJCPSN6lRj5GwaBsZcs=
X-Received: by 2002:a05:6512:1090:: with SMTP id j16mr6244607lfg.543.1606600327672; Sat, 28 Nov 2020 13:52:07 -0800 (PST)
MIME-Version: 1.0
References: <058501d6c576$43e4cfd0$cbae6f70$@olddog.co.uk> <ebaa0212-267a-b863-05a2-9a0d18d7ff1b@huitema.net>
In-Reply-To: <ebaa0212-267a-b863-05a2-9a0d18d7ff1b@huitema.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 28 Nov 2020 13:51:31 -0800
Message-ID: <CABcZeBP=Vfbw_Xj+pVrbXeagOiFrLjiETOCpvy_tZ3+dG6JxOw@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Eliot Lear <lear@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="000000000000d3cb8d05b531c929"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/VHxwVXR4K1sUhOeGxAH_EjuwyJc>
Subject: Re: [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 21:52:12 -0000

On Sat, Nov 28, 2020 at 10:53 AM Christian Huitema <huitema@huitema.net>
wrote:

>
> On 11/28/2020 3:04 AM, Adrian Farrel wrote:
> > 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.
>
>
> That's a good way of framing the issue, Adrian. I personally lean
> towards the RPC holding the line, because it makes the overall workflow
> simpler and does not dilute responsibilities. Also, I am not aware of
> past cases in which the RSE had to overrule the RPC. Do we have examples
> of such incidents?
>

I actually prefer a third version: the stream manager should be the
ultimate decision maker, just as they are about the technical content of
the document. For the IETF stream this will typically be the responsible AD
on behalf of the IESG.

-Ekr