IETF Logo Mail Archive

Re: [Rfced-future] Fwd: [IAB] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11

John C Klensin <john-ietf@jck.com> Fri, 04 March 2022 02:17 UTC

Return-Path: <john-ietf@jck.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 B703D3A0C2A for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 18:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 qwvP0NWKTRsx for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 18:17:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A48E3A0AF7 for <rfced-future@iab.org>; Thu, 3 Mar 2022 18:17:16 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nPxVG-000EwO-0Y; Thu, 03 Mar 2022 21:17:10 -0500
Date: Thu, 03 Mar 2022 21:17:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, rfced-future@iab.org, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Message-ID: <444F3E263B85D8FDFBA95097@PSB>
In-Reply-To: <b047225c-4b4d-4151-445e-65afc11427d1@stpeter.im>
References: <164579171829.24424.11911193648846995596@ietfa.amsl.com> <D68950D9-7010-46FA-8E3C-6B1C5D6AA734@kuehlewind.net> <9188ee67-2362-7fc7-931b-4fcde832d706@stpeter.im> <5718207C4063BFA2300BAF8C@PSB> <6cfb203e-5d6a-81cb-3fc6-3dfd97c0808d@gmail.com> <5C8E2753644329CDF00158B8@PSB> <b047225c-4b4d-4151-445e-65afc11427d1@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/mZVd5kxFKe_95kpb1f6XTpiaLiI>
Subject: Re: [Rfced-future] Fwd: [IAB] 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: Fri, 04 Mar 2022 02:17:22 -0000


--On Thursday, March 3, 2022 08:52 -0700 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

> On 3/2/22 8:06 PM, John C Klensin wrote:
>> 
>> 
>> --On Thursday, March 3, 2022 08:57 +1300 Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>> 
>>> "RFC Editor Function" is used in other drafts too. I think
>>> that dropping this phrase would have many repercussions and
>>> we should just keep it.
>> 
>> In case it was not clear, I agree.  I just think that a
>> definition --probably a deliberately vague one-- in the model
>> document might be helpful.
> 
> Perhaps something like this:
> 
>### 
> 
> The overall framework for the RFC Series and the RFC Editor
> Function is described in {{RFC8729}} and is updated by this
> document. Under version 3 of the RFC Editor Model, various
> responsibilities of the RFC Editor Function are now performed
> alone or in combination by the RSWG, RSAB, RPC, RFC Series
> Consulting Editor (RSCE), and IETF LLC, which collectively
> comprise the essence of the RFC Editor Function.
> 
>### 

Not quite what I had in mind, but probably more than good
enough.  Wfm.

   john

v2.23.0 | Report a Bug | By Email