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) **

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 29 November 2020 20:36 UTC

Return-Path: <brian.e.carpenter@gmail.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 67E063A0E2D for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 12:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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=gmail.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 rw-PSEsvga6q for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 12:36:01 -0800 (PST)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 0A73D3A0E2C for <rfced-future@iab.org>; Sun, 29 Nov 2020 12:36:01 -0800 (PST)
Received: by mail-pf1-x435.google.com with SMTP id w6so9072186pfu.1 for <rfced-future@iab.org>; Sun, 29 Nov 2020 12:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=xtSch0XIcz5kNAJCo9JBe1rWEdSaYqgNb/tN/nWqYB4=; b=cA5KZBbXoZMoZDuSEXpzUoaQlfp6bRHNKSyB0eviuXY5O3tVJ8xpdxpvrnWpK3w19g DmQUxDHM03mRpjl2uDbSL5OEE9Rsxzebiba2uPYcxYXXnJEuEQVVWyL1s9nqyPnQdoKH XbdHW4PAzJs9QL7X75VQwp8KV5ciBhIXBN+AjYUdLetPiEEStrWESvCihReGew8KTS+O XGRLY131IwbLZkV1XcfhRBWoo+mkzzxKUgPhsO0H7uKGs+21YxtkHnTByZkdscUa0x/k 60ksHXzrN1Lne3hI/9LiIJqOvJkuHX9tFdKPqSBXI7K9E/mvef1rSI0vRrhORBsxHyic 0p1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xtSch0XIcz5kNAJCo9JBe1rWEdSaYqgNb/tN/nWqYB4=; b=NGvC0A9QH1Y19dNnDfQ+U9KRWPM5UDmTQ2SRu7wl3RIT6rzb8S7oInclU4dsCW/9Am U8kzmP5t2s61gM7L72o5qUO/5asWJkDc0xtFq37H2atumxnkyzL/IdH6Kg8taBXoPYIF EydsIVz9wM2LXNgRbmMLLwgawFa9GilP9FdebaPTi/MMbxlOIyvFNcoy8mzUKUhHbkor rifS6W2bRpa667BeaMqmL5p/qzlZjzfWehB1/NROv/R+qQ7Dl1KPTU1gJr+X0f+jGkbP H8qWrc5mVhveK9HFc9ESA1r4+z2dYdIDyJu1Kh/tc5jwy/g94j50BXP171umD9Kk3olt DavA==
X-Gm-Message-State: AOAM5311fBKtF+rdL5vZgFER4oO9dy1EhUzya+WoUfHM5aiUkFMdHPog cd3L2/x8nS16f1bBHC8oR/E5StxS2k9aUA==
X-Google-Smtp-Source: ABdhPJwg5EB51pwC2PBv6UNc4kn1TWRTshNjfICxF4RIAcZffgX2jBAXLzD8mvLmszaAHjty/j7byw==
X-Received: by 2002:a62:8f03:0:b029:18c:968a:4cf9 with SMTP id n3-20020a628f030000b029018c968a4cf9mr15490209pfd.59.1606682160037; Sun, 29 Nov 2020 12:36:00 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id e21sm14169655pfd.107.2020.11.29.12.35.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Nov 2020 12:35:59 -0800 (PST)
To: Christian Huitema <huitema@huitema.net>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: rfced-future@iab.org
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> <CABcZeBOAYL+VvHxmzQVkhmf-7t1qFr+1-zn82Og8OmZpE2i8AQ@mail.gmail.com> <EFF69E77-6E03-4117-B237-410C59CA5139@tzi.org> <4056534f-38a1-6127-23ea-7c97b8d1bd89@huitema.net> <a1b41bd6-ef74-224d-73c0-47dbdbf07966@joelhalpern.com> <10a60d4b-0bc5-c6d3-905c-6ddaecb98737@huitema.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <ee52269d-54c2-9736-48f6-2d56393321c0@gmail.com>
Date: Mon, 30 Nov 2020 09:35:54 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <10a60d4b-0bc5-c6d3-905c-6ddaecb98737@huitema.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ydWPo_qEb0NCm4atTIU04ryw_6Q>
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: Sun, 29 Nov 2020 20:36:02 -0000

On 29-Nov-20 19:47, Christian Huitema wrote:
> On 11/28/2020 10:42 PM, Joel M. Halpern wrote:
> 
>> Depending upon what you mean by "look exactly like" below, the 
>> statement is either irelevant or does not match what I have seen as 
>> existing practice.
> 
> I mean content and general organization. I do agree with you, Joel, that 
> the same style guide applies to all streams.

Agreed, but when it gets tricky is if there's disagreement between the RPC and the stream (or authors) about interpretation of the style guide. There's no doubt that having an RSE provides a definitive tiebreaker in such a case. If we have an RSA model, I think we'd have to specify who would act as arbiter for style disagreements.

   Brian

> 
> -- Christian Huitema
> 
>>
>> We go to significant trouble to create and maintain a consistent look 
>> and feel across all RFCs.  there is an argument that they should be 
>> more distinguished, as some people think / hope that would reduce the 
>> all too common confusions.  (Of course, one would then want I-Ds to 
>> look more distinct as well.)
>>
>> But untill and unless we agree as a community on making that change, 
>> our existing practice has been to work for and value such consistency.
>>
>> Yours,
>> Joel
>>
>> On 11/29/2020 1:36 AM, Christian Huitema wrote:
>>> On 11/28/2020 10:12 PM, Carsten Bormann wrote:
>>>
>>>> On 2020-11-28, at 23:07, Eric Rescorla<ekr@rtfm.com>  wrote:
>>>>> 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.
>>>> Agree completely.
>>>>
>>>> But the RFC series may actually be better able to serve their needs 
>>>> if there is a way to have actual push-back on some not-so-good ideas 
>>>> of a particular stream manager.
>>>
>>>
>>> I agree with EKR that having the RPC escalate "author disagreements" 
>>> to the stream manager would quickly resolve most of the issues. I am 
>>> not too concerned about "uniformity of the series" arguments, since 
>>> by definition research papers from the IRTF will not look exactly 
>>> like proposed standards from the IETF, or individual contributions in 
>>> the independent stream. If that's really becoming a problem, then the 
>>> "strategic" body looks like a good place to discuss it.
>>>
>>> -- Christian Huitema
>>>
>>>
>