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 21:19 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 3CBD93A0E14 for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 13:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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] 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 vRujRtwNnOCm for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 13:19:19 -0800 (PST)
Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) (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 4D19B3A0E09 for <rfced-future@iab.org>; Sun, 29 Nov 2020 13:19:19 -0800 (PST)
Received: by mail-pf1-x441.google.com with SMTP id e8so9116532pfh.2 for <rfced-future@iab.org>; Sun, 29 Nov 2020 13:19:19 -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=Sten/CFA+MKVlBmcStgAcC5EXWgpyVa/huQYndWWYT8=; b=POLUBYKqI7j0Etttc7o14xBhlSkRbUBWVqe0oOKc1ZwWTDDP2CDtuBCZMordqFAH0X 7j9+o2Q7R9Bd76KFRATfAcwLB+/oQAAK/WgBVbglWUdr6mvpfioVlnuyKbQj2s5dNMoj J9cvyRttyw7DPOmdQgMpcdjUkhs8GKh8B9F7CTtFhH7K/GfX/srwcmphzVgavKJoAzug Y4JvHk2L2xqZZ1VN2aRt1Wafrr3o7IIDQN6OBTHX3t5FLtuhaxLnNCxpqUnayKlSp1Ym KlpY7MxrmayeVZDggIPRxu7wZqbmKjBqrsZ+Tkdk9Smwe0dxKAE1OKoWwGzIBeS8rGWE VNfg==
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=Sten/CFA+MKVlBmcStgAcC5EXWgpyVa/huQYndWWYT8=; b=EGtOgeYpTP3rECcHty6MxXEUSFIUgETPYhI+Xi/dK1cxhmki7+qgJrnK4FoyjKWhX8 OyKygclMji9+BXTdDDlVsrcnR9C0veT4ANcuSKylL1EMEA7ODEpVxlF8QK0H0Y0U+dSG oxwDOBKCwS4B7doDqr3ECzr91XV0QI4QRihPqjr/y48RSzN4i1UA79RSlYUmmMe+tnPB 8L1OKpY4TiFXn6hUgf6BlKOuFzDjMGSjVfgIaFN/unrNRY0ZDENg2E5nbDOWvOP6WL+l 2R712JBMyZCTb6hUI7vxsFxlRXgP1l24bu5YdtUViORbtu5u/cb5sH6V02OkVvQTqfwB Wdmw==
X-Gm-Message-State: AOAM531kKa7drVNs8f2G5ikNH+d35JaWOiLNoKWyoPyLlfY6EQgltFO0 v5hga2x3WIGfJ9YpBgRrgTDYK9bOs3Bomw==
X-Google-Smtp-Source: ABdhPJyWykZRR8vas0ntTOokfcdbW054F6ctwMJnIuiMXMVkk6T2kP00kGRQUVPLddYoULEjRK4FPQ==
X-Received: by 2002:a17:90a:578f:: with SMTP id g15mr22053316pji.3.1606684758462; Sun, 29 Nov 2020 13:19:18 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id g3sm14040397pfr.145.2020.11.29.13.19.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Nov 2020 13:19:17 -0800 (PST)
To: Adam Roach <adam@nostrum.com>, 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> <ee52269d-54c2-9736-48f6-2d56393321c0@gmail.com> <ecc8d50b-7205-643f-e7df-e865e7e60e3d@nostrum.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b79a3484-cffa-19c9-214f-daf0c44f9092@gmail.com>
Date: Mon, 30 Nov 2020 10:19:12 +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: <ecc8d50b-7205-643f-e7df-e865e7e60e3d@nostrum.com>
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/_BhPt805VNf6FAyHw81rXcC-_kc>
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 21:19:20 -0000

Yes, good catch, although I was more thinking of aesthetic questions like comma placement.

Regards
   Brian

On 30-Nov-20 10:01, Adam Roach wrote:
> On 11/29/2020 2:35 PM, Brian E Carpenter wrote:
>> 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.
> 
> 
> "No doubt" overstates it a bit: it's not exactly that clear-cut, even in 
> today's system. See, for example, RFC 4714 Section 3.3:
> 
> 
>>       In specific instances, where some or all of
>>       document text is the result of a careful negotiation of
>>       contributions (within or between working groups, reviewers, etc.),
>>       the technical publisher may be required to publish that text
>>       verbatim.  In the IETF standards process, verbatim publication may
>>       be requested by the IESG.  It is the expectation of the IETF
>>       community that this will not be done often.
> 
> 
> /a
> 
>