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 22:08 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 C7F523A03F5 for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 14:08:34 -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 TmUjpCTyUpMo for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 14:08:33 -0800 (PST)
Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (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 989113A03F3 for <rfced-future@iab.org>; Sat, 28 Nov 2020 14:08:32 -0800 (PST)
Received: by mail-lj1-x243.google.com with SMTP id 142so10483342ljj.10 for <rfced-future@iab.org>; Sat, 28 Nov 2020 14:08:32 -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=NcHW2WSPeC5ywCraXvHMOns+SrpaIRehP2DypObDijk=; b=j11XmpD15QfCWHEpmTAEWAwL4pwsPy7SREHq1vUQxDp6HsxkhVsBAIY1V8HacKJSzi wLbJ3vwE0Z6WeRa7DeFcalaY0iDfGPekQUaMe7TcNJ+Z10fZBG0OI3HvUiIjgQ47c0G1 RWfbha22vKgD/5mQdNjarzfXrNOUy4e9Cz/WXTRJS8+cjZQsQaLX+VWL2/DHKRZ5Wxjr 0uah+TvoGYzB6NPUM9tqVjFNuClEt8OKQ8RlW/UotaNyRinCNx0Wccn1kCDAr0KVL6ld fGScQlbAXUv6HAamNlTv8noK+mGLRWHUdJMO3+9rsr1aen6QjK/0/AC7/w+oynDlegUE UCRQ==
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=NcHW2WSPeC5ywCraXvHMOns+SrpaIRehP2DypObDijk=; b=V3Q1jwiJqb3zhEvaf4pptgT+u7S0/zOE4gmKuHx8ASVIiJ01X/4fgsaMEcejeXTjKx EFdxszxfeOzM0bnd85izJhk2aQobH0XYaxMSWfHEQ2MFHHljfHUd5CDRQdEMAlgVOnSA G1Xcr7krse/zi4iqpLmViA3M9BtdE318+5T3MT3q+092ZEpltEm4CE6t40TGibSVA65I ZpIGQEwrhX1vqidgbmWx3bLJiPPwnHkoNhbPIXPM8dv1pYlURjHehErynielx4NktCTd 8FoWEmaaabhKa4spk/Z7XSGobwBD5pdXKOKvawhwAExrZN8GygFAz2MhDMRD7lpyXzkn CMCg==
X-Gm-Message-State: AOAM533uosO0SVBw8ABSsPcdCPfaPuFh6d596wggqV7YkPBU2zhs9XYr U9NBj8HaMNCzXM+yuUspF+phP8AszspH/Im7xa/l4F+eAQcVgoqD
X-Google-Smtp-Source: ABdhPJwdGY6Jeh2eyOq9hEpiD82FLaGP3d6DUxSeAEB8YEL4nn5logrzn6MpK3A+a2QMpdoFIEVFV/JM7i6AqO3IEB0=
X-Received: by 2002:a2e:50c:: with SMTP id 12mr6020949ljf.371.1606601310614; Sat, 28 Nov 2020 14:08:30 -0800 (PST)
MIME-Version: 1.0
References: <058501d6c576$43e4cfd0$cbae6f70$@olddog.co.uk> <ebaa0212-267a-b863-05a2-9a0d18d7ff1b@huitema.net> <CABcZeBP=Vfbw_Xj+pVrbXeagOiFrLjiETOCpvy_tZ3+dG6JxOw@mail.gmail.com> <ecc477fd-6d5b-9071-0b14-19f53d7883cc@joelhalpern.com>
In-Reply-To: <ecc477fd-6d5b-9071-0b14-19f53d7883cc@joelhalpern.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 28 Nov 2020 14:07:54 -0800
Message-ID: <CABcZeBOAYL+VvHxmzQVkhmf-7t1qFr+1-zn82Og8OmZpE2i8AQ@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: rfced-future@iab.org
Content-Type: multipart/alternative; boundary="0000000000006a70d305b5320429"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/lG_Vah3NXXSdWum3e6qtlaSuBks>
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 22:08:35 -0000

On Sat, Nov 28, 2020 at 1:58 PM Joel M. Halpern <jmh@joelhalpern.com> wrote:

> 1) If the stream managers are the final authority, then different
> streams will get different answers, reducing the coherence and
> consistency of the series.  That does not seem beneficial.
>

I suspect that we're simply going to disagree here, but I'll make an attempt
to lay out my reasoning. While I think that coherence and consistency are
a value, they are not the only value. For instance, we do not encourage
the RPC to rewrite the documents extensively to make them read the
same. Indeed, the style guide does not standardize British vs.
American spelling across the series as a whole [0].

As I'm sure I've said before, from my perspective, the various streams are
customers of the RFC series, and ultimately it needs to serve their needs.
I believe that this includes allowing the streams to decide not only the
technical
content but also to a large degree the editorial content. While one might
imagine
some dispute about style which would be so large that it threatened the
character of the series (e.g., the stream wanted to have all its documents
published only in Esperanto), in my experience disputes between authors
and the RPC are not generally of this nature, and therefore IMOthe stream
ought to decide.


2) As a minor matter, the individual ADs are not the stream manager for
> the IETF stream.  Traditional, the IETF chair has been the stream
> manager.  I hope that the IESG has adopted a policy of appointing a
> separate individual stream manager.  But there are not 13 stream
> managers for the IETF stream.  And there should not be, as it would
> render the notion of "stream manager" rather odd.
>

Yes. This is why I said "the AD on behalf of the IESG". I think this is a
practical approach given that the AD already is involved in making
publication time decisions such as which changes to the text require
extra IETF processing, such as being sent back to the WG. However,
I wouldn't object to having this as the IESG's designate if people prefer.

-Ekr

[0] https://www.rfc-editor.org/rfc/rfc7322.html#section-3.1

On 11/28/2020 4:51 PM, Eric Rescorla wrote:
> >
> >
> > On Sat, Nov 28, 2020 at 10:53 AM Christian Huitema <huitema@huitema.net
> > <mailto: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
> >
> >
> >
>