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

John C Klensin <john-ietf@jck.com> Thu, 03 March 2022 04:08 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 DA9A93A11D1 for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 20:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 Y2mjgiXunTJg for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 20:08:15 -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 55B9C3A11C5 for <rfced-future@iab.org>; Wed, 2 Mar 2022 20:08:14 -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 1nPcky-000Cm8-Dj; Wed, 02 Mar 2022 23:08:00 -0500
Date: Wed, 02 Mar 2022 23:07:55 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@lear.ch>, Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org
Message-ID: <339D634A9F7E88D5FECFFE9A@PSB>
In-Reply-To: <2f7fc97e-b28e-b1fa-f583-726c30c3ddb6@lear.ch>
References: <5231BEDE2E5FB8C502855970@PSB> <46de5830-990a-30bf-57fb-ddbc78cbb1fc@stpeter.im> <3c4497ed-d476-16bc-9aa1-354cd082830e@stpeter.im> <2f7fc97e-b28e-b1fa-f583-726c30c3ddb6@lear.ch>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/lW9UKvqnA1VFnCFSGlJQ2XZe1BQ>
Subject: Re: [Rfced-future] 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: Thu, 03 Mar 2022 04:08:20 -0000


--On Wednesday, March 2, 2022 06:55 +0100 Eliot Lear
<lear@lear.ch> wrote:

> 
> On 02.03.22 01:02, Peter Saint-Andre wrote:
>> 
>> Although I agree that internationalization issues can be
>> especially  thorny, I wonder if this document should say
>> something more generally.  (For instance, another example
>> might be YANG modules, which AIUI in  the past have caused
>> some adjustments to the editorial process.)
>> 
>> This could be defined in a new RPC responsibility within
>> section 4.3,  such as:
>> 
>>    8. Conferring with relevant experts regarding particular
>> kinds of       content when publishing RFCs or helping
>> to define policies for the       Series; such topics
>> might include internationalization and      
>> localization [RFC 7997], graphical formats such as SVG [RFC
>> 7966],       and structured content such as YANG modules
>> [RFC 7950]. 
> 
> 
> That is one reason to have an RSCE.

Independent of the other issues and text -- which I think is now
under control...

While I agree that it is a reason to have an RSCE, assuming the
RSCE will have even moderate levels of knowledge in one, much
less several, of those very specialized areas calls for a much
more in-depth description of requirements for the RSCE position
than is in the draft and that I think was the plan the last time
this was discussed.

best,
   john