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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 03 March 2022 15:54 UTC

Return-Path: <stpeter@stpeter.im>
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 590FF3A0D58 for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 07:54:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 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, NICE_REPLY_A=-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=stpeter.im header.b=A9a5zFZ4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gD/ni3PO
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 vUWB2C7rWPTK for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 07:54:13 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD1613A07EA for <rfced-future@iab.org>; Thu, 3 Mar 2022 07:54:13 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id E20A8320157F; Thu, 3 Mar 2022 10:54:12 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 03 Mar 2022 10:54:13 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; bh=EBDi39vkYVuS14 8FuaWGd6WnDqAWUIr1dXw5YdNPbI0=; b=A9a5zFZ4bcuCeuZ2KoptVtVXK4E207 Z4Nj17DjGszFU/gqLf1oLYLtO2H6r7drITN92HIrrQ5mr3hLuK36gZKLBLdh60hK znQkZfhuxC7JSQUWkfTnJ9oCIFatI84nqMUEsWju90n0Vnnwr+avsKFqeMafsluN Y3vVLVfPtg9HVOoHzS1xC+s5BD5GJGZ2C/ihJx09TlHr0ZmNvi1IT4DKy9Zxpvsx maYvKNHyHvvx2ketv1NLz6FUB6p+aGZCYFWg8qv9LL4diJfbstimodkR1qsKtoNH gaxLUUvz8J5ey0ylVzXwasxpNKswn8fWZMqXw5xFLZKiWFbQ/cpBRrZA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=EBDi39vkYVuS148FuaWGd6WnDqAWUIr1dXw5YdNPbI0=; b=gD/ni3PO a/1m6x5ZxtzhTPlnaVRzTunU9rwMQJJ3Zx3MY+oQ4zB+6o6jX4YR1obxrv6z5fMr Or8h9ikBGoFsNLwDN2u1Z2W9J0VP1t78NXHK5j1YO9lOUVwo3y/X8/VxEoIQWT5n CuM2kdXXw0xkSM+UKvMZRUbEtnMmjL7xA6afysC/IJMmJmlAY/PRGQU0UqT8noWw HUI0eMHOocfonN8AxPUf9aQ8UAxZ/5qx30Lhn/EjV0x8VYekzJPnLgrOCsV2OpyF A0EeX7hrJ30/ntPB0PT4f+ic+fG1U64c90X8v8Mnj8PjOh7JW0rGHtQa3SiKQd+O aZcC+U/iXmg3Lg==
X-ME-Sender: <xms:pOQgYtGKo4FaV7f73BowfLmmlqgAqKAFQ9M9OO2TmIWA43ZLhi6vqw> <xme:pOQgYiX9-5_ou_8tcaQ2St3VCStdmdZbQL8zDDoKLfzZEetVzcWfV9ssauwCtZmcS -sGGwNgPulmRh7vhQ>
X-ME-Received: <xmr:pOQgYvJeNu8knb64_CfQ5bO4wKaHs_zu6ZeVA05kLXHQeiGyRufnYyFrwJBPq37HUjl9uZ4ivEqlJOProumrq_hrg3kPr2BjwbAt1jk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtiedgkedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpefrvghtvghrucfurghinhhtqdetnhgurhgvuceoshhtphgv thgvrhesshhtphgvthgvrhdrihhmqeenucggtffrrghtthgvrhhnpeevtdfgteetgfffve ehtedvudegudfgleevfedtleevtefgfeeggffgfeeludekheenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvg hrrdhimh
X-ME-Proxy: <xmx:pOQgYjFFb1u0lZxfro1f3QhzJfqlBEaOppykP6hyH7jJKqic3WZE2w> <xmx:pOQgYjVA-mlrwS4YopXqnyCmVXA6jY1mzFy93vskdwcHZSsKw4H1yQ> <xmx:pOQgYuOQ_5wIsc27y1hQ_7W9yW28rBczwJ-9QoxwjD-Y2siA91eHwQ> <xmx:pOQgYgg_lwZbUb3RnmTscuVViV0r_0gselCvOaC_71YokWuumkrXjw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Mar 2022 10:54:11 -0500 (EST)
Message-ID: <11a600ed-e879-34a3-e429-64cc1247a3d2@stpeter.im>
Date: Thu, 03 Mar 2022 08:54:10 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, "rfced-future@iab.org" <rfced-future@iab.org>, John C Klensin <john-ietf@jck.com>
References: <5231BEDE2E5FB8C502855970@PSB> <46de5830-990a-30bf-57fb-ddbc78cbb1fc@stpeter.im> <3c4497ed-d476-16bc-9aa1-354cd082830e@stpeter.im> <84360fe2-a8a8-c0c4-83e4-f59d958b4792@it.aoyama.ac.jp> <aa3a17c9-af09-531e-4617-45722d4da005@stpeter.im> <e2bc3ad4-facd-795f-1c52-ebd1ebf00cfb@it.aoyama.ac.jp>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <e2bc3ad4-facd-795f-1c52-ebd1ebf00cfb@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/WOfbeSfbq-qA_x7y8y46lpVFKO0>
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 15:54:18 -0000

On 3/2/22 5:17 PM, Martin J. Dürst wrote:
> Hello Peter,
> 
> On 2022-03-03 00:19, Peter Saint-Andre wrote:
>> On 3/1/22 6:54 PM, Martin J. Dürst wrote:
>>> Hello Peter, others,
>>>
>>> On 2022-03-02 09: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].
>>>>
>>>> Peter
>>>
>>> This looks like a very good direction. However, I'm slightly 
>>> concerned that this includes "or helping to define policies for the 
>>> Series". I think the RPC should reach out to all the help it thinks 
>>> it needs or can benefit from. What I would definitely want to avoid 
>>> is to create the impression that input on I18N,... to the policy 
>>> definition process has to come, or is mainly coming, via the RPC.
>>
>> Oh, that's certainly not the intent.
>>
>> Perhaps "when publishing RFCs or contributing to the work of the RSWG".
>>
>> Peter
> 
> That would be fine with me.

Elsewhere in this thread, John Klensin suggested:

    Identifying topics and issues that they encounter while processing
    documents or carrying out other responsibilities on this list for
    which they lack sufficient expertise and identifying and conferring
    with relevant experts as needed.

Would that meet your needs?

Peter