Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 13 March 2022 19:28 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 400433A1555; Sun, 13 Mar 2022 12:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, SPF_HELO_NONE=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=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 FWdH8Mq-5RDL; Sun, 13 Mar 2022 12:28:32 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 8E1BC3A0902; Sun, 13 Mar 2022 12:28:32 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id t187so11998297pgb.1; Sun, 13 Mar 2022 12:28:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=wBIk9/XKS0UvBkdWbCOl95F5FZJpgY52qs432PsB1VI=; b=WDJiBOi9LsqT2+Sd9j1xFFSljc1iie/NzoKxou3o/9JBF8hjaN3pf9EuEnSxvLEfEx AtNVg7u1+rgkhIlplbIxv7/mCfEcT0zmdkDE2rwbzZfahil/dfLk9ETMEjxb6J7CvA8r JPVCYzqDdbXxnRJdhXXjf0XlVsVkP4nzqvyEUwA9CJqr+SyQ+WerDujY76nr/6y02dxI IoBEM6+NeQi2yxGp7no8a/O/HoJehWqB4N7vrQFDZEwUE+GJ6y+ndk+nggAT0AH//h3R ByWZWFnPJafffVo4HKyliPGibcH0Yz+F28kTvrSoLOPmPmKrqmDAsCG841uILMgFkbe4 BLag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=wBIk9/XKS0UvBkdWbCOl95F5FZJpgY52qs432PsB1VI=; b=jqyce1MjCyCsRGBK2ygNll3rhclDURGyC7k5DFoQ65MJ2BBJJJdL3pOH3Qpk2DrOqu +B78kenkKWmjLzAhoyatsYOrY2pYcZg/M5qypt5KqVpzZAi5uoc/DHiSHsjxpb3XB0sR mIqwgEOWq7YO3nRkRc5M40mkbBA/JUmPi2dVewX9AGQRLwWRgC/AQg93CvjEtO2nIXvh jFe8SnE6BpSsSXN/ywZP2kBJvwOVkPTjskvBSl9xGJAeuE9mQUACMUbOwqS2MVPeQKFH Vug+W/GpVaepJSsDvbCpgNH48dEEU9zAg08vsI+9s0LEWPm9YAPUvZL9uvfYib1P8W6m EIzg==
X-Gm-Message-State: AOAM530KUufAWgpWzvsyKZHPpgQ1E7Nmz2Dte3U7oFlajebXvLFsovm+ moUZCNIo7Y1SrGVDwD8S4B0=
X-Google-Smtp-Source: ABdhPJxj8jPhMTVgchk7POXsraC2b4Ywdxg1BRd6Zt55Yzbb5Igd7LotZOrekIFscupKsmybv/SCBQ==
X-Received: by 2002:a65:6b8c:0:b0:380:4725:2e26 with SMTP id d12-20020a656b8c000000b0038047252e26mr16932148pgw.78.1647199711195; Sun, 13 Mar 2022 12:28:31 -0700 (PDT)
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 3-20020a17090a030300b001c17851b6a1sm11150283pje.28.2022.03.13.12.28.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 13 Mar 2022 12:28:30 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Eliot Lear <lear@lear.ch>, Lars Eggert <lars@eggert.org>
Cc: rfced-future@iab.org, Internet Architecture Board <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com> <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im> <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net> <bf702de8-a876-3d9f-23d8-4ba49f86bd05@gmail.com> <E8C97678-AD00-402B-9646-DEFF6E76263D@ietf.org> <d4ac965c-65b1-e909-864c-cb14e27a3b0f@stpeter.im> <040d9aac-04be-2bef-fad4-b41f2af271e9@gmail.com> <B87EBCF2-16FB-4A22-86FF-20603200E749@ietf.org> <e012452a-61d1-f499-f19e-6d3ff9863901@gmail.com> <4AD933FC-4032-4A10-92DD-A34ADEDD557F@eggert.org> <CANMZLAZmrdxQuGT=W36gUf3gEd3d1C_0c-hfdO2-gpFUOQf7sg@mail.gmail.com> <AB5E3E46-D450-4E21-B67B-D639F67734AE@eggert.org> <e4b25205-af63-aff5-dbcc-9a16aa86b07d@lear.ch> <C2E0E777CD125A1439F4AACD@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3dabfc01-dfb6-0398-a9a1-5e9ee7e98dc8@gmail.com>
Date: Mon, 14 Mar 2022 08:28:24 +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: <C2E0E777CD125A1439F4AACD@PSB>
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/qPZpxS7OAboDuI9837s1DxwGuGQ>
Subject: Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]
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: Sun, 13 Mar 2022 19:28:38 -0000

John,

But you're proposing an addition to the IAB charter that is not
concerned with the RFC Editor model. Regardless of whether this
is a good idea, surely it is out of rfced-future's scope to
decide that? So I think Eliot is correct *as far as his remit
goes*.

Lars, instructions please.

Regards
    Brian

On 14-Mar-22 07:53, John C Klensin wrote:
> Eliot,
> 
> I have posted an objection, not to removing the liaison, but to
> prevent reinstating some variation on it without going through a
> long and time-consuming process of document revision.
> 
> More explanation in a note I hope to finish and get posted
> within the next several hours, but the amount of uncertainty
> about details and implications of the new model -- uncertainty
> that seems to have been illustrated by questions or comments
> within the last week or so -- strongly suggests that, where
> there are not strong arguments to the contrary, we should build
> flexibility for efficient small corrections to the documents or
> their interpretation rather than locking options out.
> 
>     john
> 
> 
> --On Sunday, March 13, 2022 14:46 +0100 Eliot Lear
> <lear@lear.ch> wrote:
> 
>> At the moment, I am not hearing any objections.
>>
>> Eliot
>>
>> On 11.03.22 10:34, Lars Eggert wrote:
>>> Hi,
>>>
>>> On 2022-3-11, at 11:29, Brian Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>>> I have no problem if there's consensus to remove the liaison,
>>> I think it would be good if others in the program spoke up on
>>> this, so the chairs can take consensus.
> 
>