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

[Peter Saint-Andre <[e-mail]>]

On 3/7/22 5:08 PM, Martin J. Dürst wrote:
> 
> 
> On 2022-03-08 04:31, Jay Daley wrote:
>>
>>
>>> On 5/03/2022, at 1:13 PM, Brian E Carpenter 
>>> <[e-mail]> wrote:
>>>
>>> On 05-Mar-22 12:51, Peter Saint-Andre wrote:
>>>> On 3/3/22 8:53 PM, Brian E Carpenter wrote:
> 
>>>>> 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.
> 
> I agree, but shouldn't it be "{{RFC7322}} or its successor"?

I'm not a big fan of saying "or its successor" everywhere because the 
point of specifying that a new RFC updates or obsoletes an old RFC is 
that the reader should be able to follow the trail and find the new one.

Peter