IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 03 March 2022 19:41 UTC

Return-Path: <brian.e.carpenter@gmail.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 1E1243A10E7 for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 11:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FX8YkeuLdIwP for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 11:41:48 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEC013A1060 for <rfced-future@iab.org>; Thu, 3 Mar 2022 11:41:48 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id u2so5030407ioc.11 for <rfced-future@iab.org>; Thu, 03 Mar 2022 11:41:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=zo3w6Pta1b2uKnBGRUo30Jd93HGQ3vX4oCY29tb5BRI=; b=fvP4JoBJHLTt1nemy3aTKT48kij6BixhhgDcTPUbhSSWusSzjUssdIZVfBvh43YfVo vlCI/ntl9yB4VVjbc9IT74mqfbA8i0FqXVruip/bt7Kqt8axcs8oJRzfazSLve6AFMzH TSbHpu4XRBHNFR9glf/BKEHKyeqYqN8j1FOSHNHQM9cpIVo3KV/6+d4cri6IEoYOHDYe HFjOKF7LSEWirTui2ZgF1jrUpfQIiQg+z8HpbkV2ZLGB1G90e7zgtxIFpbPzb0ATjlUm 7w7npS/+yXriHWuRWfLbqY0YuXqCAbuEIVpA3RYMzZsrKqTTYrmKG8Fivmh0nkInDe5j HXCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zo3w6Pta1b2uKnBGRUo30Jd93HGQ3vX4oCY29tb5BRI=; b=GmMne+gz5NRY9utmynH1hj6HxKxqGP+6HZMITR6ux56agxNcuvYGxMUaCbfTdeHgN6 TkBsIv84xNJHBoAaNKx7fTr3g3NnlTFFSWPyM3M6BMF9H61Glaarcmkk4tZQ/fn8DEW9 YGKOleh77Co30U5fA5FLMpUrionSmeoOTJ37BUXWep8d5+pWWyK6wpr8B4OtpEPmJ2bL LqOJ5JtyS1kzp9y1IrfoChqGWj3RFor9eyzSNiAQDJK9ifL79ENk4dK/4o/mjgI01jZM jpz6bn/GzwZ4oHoAu5IbJBDbANLFAnAs6fyZzOitlht5cbCHLwzJ/dRRrHrlUBvZmtT1 fcQw==
X-Gm-Message-State: AOAM532h7WBl1m/TeZYAkc/vy7k63DPdr5vTT1WW/zK7E1yvM/N54ZdU tZ2nsjRpmdQRme34e9MVDP0=
X-Google-Smtp-Source: ABdhPJwzj8UMMMN8jel8uk0ot+v6Vh/tNDIQKbT9gnxynjTI9TKtF3N9v9c6bDXYuZN3DfvBoycjkw==
X-Received: by 2002:a05:6602:1594:b0:640:7236:e6ea with SMTP id e20-20020a056602159400b006407236e6eamr27639273iow.23.1646336507541; Thu, 03 Mar 2022 11:41:47 -0800 (PST)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id x7-20020a056e021ca700b002c5f9136a2dsm3219891ill.36.2022.03.03.11.41.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Mar 2022 11:41:47 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, John C Klensin <john-ietf@jck.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, rfced-future@iab.org, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <512f28ab-47d9-b7a2-dc74-192e931edcab@gmail.com>
Date: Fri, 04 Mar 2022 08:41:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <b047225c-4b4d-4151-445e-65afc11427d1@stpeter.im>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/wn0JX-tATrWcgO7CB0mErqJtyGM>
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: Thu, 03 Mar 2022 19:41:53 -0000

On 04-Mar-22 04:52, Peter Saint-Andre 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.
> 
> ###

Looks good to me.

    Brian

v2.23.0 | Report a Bug | By Email