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

Jay Daley <jay@ietf.org> Sun, 29 November 2020 07:11 UTC

Return-Path: <jay@ietf.org>
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 4C1493A128E for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 23:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 AIlPBhX5ys4P for <rfced-future@ietfa.amsl.com>; Sat, 28 Nov 2020 23:11:51 -0800 (PST)
Received: from [192.168.1.101] (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 72E683A11A4 for <rfced-future@iab.org>; Sat, 28 Nov 2020 23:11:51 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-A5799FF9-84D3-4896-B8C5-531B09418431"
Content-Transfer-Encoding: 7bit
From: Jay Daley <jay@ietf.org>
Mime-Version: 1.0 (1.0)
Date: Sun, 29 Nov 2020 20:11:49 +1300
Message-Id: <1E1942C0-E4CF-45A6-8DD2-0BDEC44F8D09@ietf.org>
References: <10a60d4b-0bc5-c6d3-905c-6ddaecb98737@huitema.net>
In-Reply-To: <10a60d4b-0bc5-c6d3-905c-6ddaecb98737@huitema.net>
To: rfced-future@iab.org
X-Mailer: iPad Mail (18A8395)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/OX2gkEsmqAAZ2xyFc5X4Umwwi74>
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 07:11:53 -0000

I’m a bit confused.  Are we saying:

A1) There is a single style guide agreed by some process yet to be determined, that each stream manager is responsible for ensuring compliance with; or

A2) There is no single style guide and each stream manager is responsible for setting the style for their stream.

I’m guessing A1, and that is being recommended as an alternative to 

B) There is a single style guide and the RS[E/A] is responsible for ensuring compliance with it.

Sound right?

Jay

-- 
Jay Daley
IETF Executive Director


> On 29/11/2020, at 7:47 PM, Christian Huitema <huitema@huitema.net> 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.
> 
> -- 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
>>> 
>>> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future