IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 01 March 2022 19:20 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 4A5D53A0AF4 for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 11:20:48 -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=Wt0jNwIC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=YlJUDKkq
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 DYdnqM_0TV3O for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 11:20:43 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90F1E3A0AE9 for <rfced-future@iab.org>; Tue, 1 Mar 2022 11:20:43 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id D0FD35C01E4; Tue, 1 Mar 2022 14:20:42 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 01 Mar 2022 14:20:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :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=IRXSk5zkUcou1p rA5maAUW1Xu2HfAbhj2eioRD8fu14=; b=Wt0jNwICgEL4madczwIGgyDAtoStJD NL2QWqHfaCC4xGjuzmtFPSEdqdeSXNEX+4LrSlw6/I4TY5bXOhk+p4p23Mdhq0Nb 4Y7ieFWqhmJyJzQCFHCTVa++ZxtixS/+DX5bH6z2mSYXRTAMvT14Xqpf3LRAZ+jd xPrsID5jtdQ+lBSSQoyiyzNAANJ04eJDagxR0c2cHy7sjf09UrEz8b51pP7w72+3 dCe1oRphjR3xwhXe1yL57QSv4gB9wLwx9i2S2/BVfrIRdl0n1Toc3cf1dcvU83R0 VQgQMkCox2dP6ImE8LKkZpSsuZ0mBguLNceNxgrAIP3SNQnvBorosHLg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=IRXSk5zkUcou1prA5maAUW1Xu2HfAbhj2eioRD8fu 14=; b=YlJUDKkq9492cLAPWHCqOebBHG7BXAGeNDxhojG4HFGb/xKK3/y/e4ZBD vAHYNfoMlYKuQZXFO9c8X+VvkjdlMCMsyhtnerirhRcVcIt6KF3euoYdC6nfauVz 0BVF4MmbGKX7CadD8Wo/mQCgrA69fmOscDGq4RR8dvDBWoykQV48uSMNBleHuuWD BoztzPGVUyG8Xm1hjIljT0De7C27eAikieZWDS14IY6lMFlsfFopWlWFkcadm6J5 Vl082nRk1xW1sul1SgHYpv9NhC5C8WL8grDai71mogZtkJ5A7N1SVZHbrUzTxCCI gCJ/+G6SLHjuHue5Yo0Q7nWJ/o6Sw==
X-ME-Sender: <xms:CnIeYr9lVjvSR6S17I8a_vox5ndZyEmi8DSMTktZdO2CwSF_2maZig> <xme:CnIeYnsIPZnlKSPfl-tTYpFdmE3PDbZttfoSuCdGKbAE-Cj4PmpWgYfk-Gmrb6Kni 6slFNS-Gt5Z-4NQCw>
X-ME-Received: <xmr:CnIeYpB2X4cL_ta-DFpPn5UR_LZ2NEkduJJ1uPoHhA6oel26Zlx9WkORDz8lZmfcRCbKLMw2COuBzEPRaO7C6CvS5Ad9eD6kkbADUSA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeehtefhvdejvdfhgeetgefhfeeuudefkeetvdfhkeelleeu heefleekkeekieffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:CnIeYndHztl0hIqhXJ8ANfEpiCThEjTCWa1NkbxgF_XHkq39DagFQA> <xmx:CnIeYgMcAWHZoIJTI2uJ7mMzz-4S806zAjVkz-Bj5tm3cthUQ9uKdg> <xmx:CnIeYpk7TjonNASIlCmGnQ8zD_R6wrNtcLZNvdMaRKYwPTmt8lZMjw> <xmx:CnIeYtogHcHEtdMdGzr6YuWdP2-0jf2DlNTF0IS8Mmt5I0tAxYNF2w>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Mar 2022 14:20:42 -0500 (EST)
Message-ID: <ae47e3d3-16d6-4e55-ff4d-d96c9011423c@stpeter.im>
Date: Tue, 01 Mar 2022 12:20:41 -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: Mirja Kuehlewind <ietf@kuehlewind.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Eliot Lear <lear@lear.ch>
References: <164579171829.24424.11911193648846995596@ietfa.amsl.com> <D68950D9-7010-46FA-8E3C-6B1C5D6AA734@kuehlewind.net> <5631b70e-51c4-fb85-a521-9740d8874c31@lear.ch> <12c75b25-2a64-dc51-1bed-d321c3bf2f5e@gmail.com> <30692162-D839-42A8-94DC-77C3A9AF3773@kuehlewind.net>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <30692162-D839-42A8-94DC-77C3A9AF3773@kuehlewind.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/yLqG9VqTzLM1DuZFIul8JHfJGUw>
Subject: Re: [Rfced-future] [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: Tue, 01 Mar 2022 19:20:48 -0000

On 3/1/22 2:14 AM, Mirja Kuehlewind wrote:
> See quickly below.
> 
>> On 28. Feb 2022, at 20:58, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> Responding to Eliot's direct question:
>>
>> On 28-Feb-22 19:30, Eliot Lear wrote:
>>
>> ...
>>
>>>>> 8.2.  RFC Series Editor
>>>>>    Implied by the changes outlined in the previous section,
>> the
>>>>>    responsibilities of the RFC Series Editor (RSE) as a person or role
>>>>>    (contrasted with the overall "RFC Editor function") are now split or
>>>>>    shared among the RSWG, RSAB, RPC, and IETF LLC (alone or
>> in
>>>>>    combination).
>>>>> In this list, the RSCE should also be mentioned, because the RFC
>>>>> Series Editor
>>>>> also had consulting/advisory roles, and these are now held by the RSCE.
>>> I think that's fair.  Others?
>>
>> Yes, I think that's exactly right and it's a factual correction, not
>> a change of intent.
> 
> The RSCE is indirectly mentioned as member of the RSAB. However, not real concerns to add this role here separately as well.

Agreed.

Peter

v2.23.0 | Report a Bug | By Email