Re: [Rfced-future] Sectiion 4.3 on RPC Responsibilities (was: Re: Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11_

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 05 March 2022 00:14 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 37FA43A136A for <rfced-future@ietfa.amsl.com>; Fri, 4 Mar 2022 16:14:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 Pj1nlsLkUDdE for <rfced-future@ietfa.amsl.com>; Fri, 4 Mar 2022 16:14:00 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 5C79E3A1373 for <rfced-future@iab.org>; Fri, 4 Mar 2022 16:14:00 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id m11-20020a17090a7f8b00b001beef6143a8so9327015pjl.4 for <rfced-future@iab.org>; Fri, 04 Mar 2022 16:14:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=067FEspGbVnl4mi/MYbAYkjCPLDIPXyRn2JsAKoAWjI=; b=ABeAi1G1HVvj26aaa/G2ns27eBxgLkLPA38U1OEYYkDP+E3qmFhbo4Jf4oZGKJboR8 lABFVQJdb4fEhkGYK42cM5mZrA9Cl7N8klhOhp7b9kubjfZDiVPChkiztDMZC2zD324S 99b2wWGjVfwvgmgLcwJ8p4yEQtlsmiRd9wb+xmMUfOCN7FRf7THHaWpjqM3n+Xgew/S1 J3xjOwiKtBRxlM/EPdm7qvHnA1HN3ewFP8HDI63eFIWCCYOO4cpybilt1GlIarkZS8Xz FQ1S4oZeDiaK3WXyvQbpTKDRGAb6AhVrl8ppFmPsfEgp3flJN35t0PNQGzenwb4ABpml K5Tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=067FEspGbVnl4mi/MYbAYkjCPLDIPXyRn2JsAKoAWjI=; b=I8ZWt3OKz/RgvZaDzBUjYDAsolnG1IbdozqWrV4lIqOPJU/of9Zsc+TVHYNaz1kjEE tm6g1+O52HNSLALQQea/OXbOwfUEEki8n0F+XY0sIc696hVJ/6AXPHq+W5vFA4U5qtCU wAcAi/Ex5nOVMWhnGSM9xNMXagvMSuHNRN7XoaCAOVTtgQ03FnWDnjWBKYEbWYZNNbKA LmpGJmJbHHdviTZxuiRr9jmj4hXKKgJx90ywAUT1Yw5+E63p672DM7GbpbDu9VUF0IbQ FbnDOUGbVW/Zm9WVWwJFXCrGy4Yx8RXQRCD3IsQtJyQA8pFi3UhaseQ3iAcUxEQNNJGu rWag==
X-Gm-Message-State: AOAM531YhR/uetNwLgfQjSYB7TIP0T/f9wnGszpWTKNdTrDRwwtniIEa QgPqEL+jk9yrMgIczn3HeaCFZxwSeG6LTQ==
X-Google-Smtp-Source: ABdhPJzukZpgdCASwUT2PLUcVt7HQ2jgPkyZ6o6COZBxgJ+buD5KmXzfiw0TUbq8Uc2nxUeiw2wUoA==
X-Received: by 2002:a17:902:e80f:b0:151:bdd2:cabc with SMTP id u15-20020a170902e80f00b00151bdd2cabcmr932160plg.31.1646439239444; Fri, 04 Mar 2022 16:13:59 -0800 (PST)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id z2-20020a17090a170200b001bf2d530d64sm2607495pjd.2.2022.03.04.16.13.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Mar 2022 16:13:58 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, John C Klensin <john-ietf@jck.com>, Eliot Lear <lear@lear.ch>, rfced-future@iab.org
References: <0DD984849353AF88D72E54B7@PSB> <7fd23143-dd24-295b-2912-32abc6e89579@lear.ch> <1CF8B6A11A07D3178C873256@PSB> <2dbdc67c-18a8-8c21-9f2b-7a8dc37d9860@stpeter.im> <2292F272F651D2E9C53B9075@PSB> <e9313719-8da1-ea05-b8d7-98485310d6b2@gmail.com> <a38e1bdf-36f1-79ea-cf37-8451cac0958f@stpeter.im>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7a2be7af-0cdf-6a30-985b-ba4f4bf24691@gmail.com>
Date: Sat, 05 Mar 2022 13:13:53 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <a38e1bdf-36f1-79ea-cf37-8451cac0958f@stpeter.im>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/LMwdB27pmUEYpgbyLKnBT7NZwWk>
Subject: Re: [Rfced-future] Sectiion 4.3 on RPC Responsibilities (was: Re: Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11_
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, 05 Mar 2022 00:14:12 -0000

On 05-Mar-22 12:51, Peter Saint-Andre wrote:
> On 3/3/22 8:53 PM, Brian E Carpenter wrote:
>> On 04-Mar-22 16:39, John C Klensin wrote:
>>>
>>>
>>> --On Thursday, March 3, 2022 19:30 -0700 Peter Saint-Andre
>>> <stpeter@stpeter.im> wrote:
>>>
>>>> ...
>>>>>>> (i) 4.3(1) implies that editing it done only to bring
>>>>>>> documents into conformance with the Style Guide.  That may
>>>>>>> be inconsistent with other points that imply other reasons
>>>> ...
>>>>> The term "conformance" is a bit odd in that context ("comply"
>>>>> even more so) and, IMO, "general", "intent" or some other term
>>>>> is helpful.  One could even say:
>>>> ...
>>>
>>>> I propose:
>>>>
>>>> 1. Editing documents originating from all RFC streams to
>>>> ensure that
>>>>       they adhere to editorial standards specified in the RFC
>>>> Style Guide.
>>>
>>> Still feels over-specific given the (IMO desirable) flexibility
>>> of the past.  Think about replacing "that they adhere to" with
>>> "consistent with" (the collective documents that make up the
>>> Style Guide actually allow more than enough flexibility).
>>
>> Yes. The words "guide" and "must" do not sit well together.
>> I'm sure there will always be exceptions to any style rule,
>> and I think we need text here that allows for that.
> 
> I see your point. So (under Working Practices):
> 
> * Maintenance of a style guide that defines editorial standards for
>     RFCs; specifically, the RFC Style Guide consists of {{RFC7322}} and
>     associated documents and resources listed at {{STYLEGUIDE}}.
> 
> and (under RPC Responsibilities):
> 
> 1. Editing documents originating from all RFC streams to ensure that
>      they are consistent with the editorial standards specified in the
>      RFC Style Guide.

Yes, that sounds reasonable to me - firm, but does not read like a mandate.

    Brian