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

> On 5/03/2022, at 1:13 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 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.

I agree.  

(fwiw, I am commenting here because i want to ensure the role of the RPC as defined here is clear, consistent and achievable).

Jay

> 
>   Brian
> 
> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org <mailto:Rfced-future@iab.org>
> https://www.iab.org/mailman/listinfo/rfced-future <https://www.iab.org/mailman/listinfo/rfced-future>
-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org