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

Eliot Lear <lear@lear.ch> Sun, 13 March 2022 13:46 UTC

Return-Path: <lear@lear.ch>
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 9CDD13A1792; Sun, 13 Mar 2022 06:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 DUnQbkPCvpx3; Sun, 13 Mar 2022 06:46:32 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 501AC3A178E; Sun, 13 Mar 2022 06:46:26 -0700 (PDT)
Received: from [IPV6:2001:420:c0c0:1011::9] ([IPv6:2001:420:c0c0:1011:0:0:0:9]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 22DDk9xg002970 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sun, 13 Mar 2022 14:46:09 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1647179170; bh=47pDLJD8uHhR8Ni2CfqTFlnPvD1MLo3AVT2x2Hdsqw8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=bW9GwfI6IUAKPhheuaDxnGg/0sGFJJhpSE3T+DvzWby8fnTWgwXLf6LxdC65uLDEO DXU1KQoahQtDdoolKH26kABi4iK6Hi0nDttbyiCcrOFkHA69ueNFCC0fMXCDKKj0+/ js1OQhYWE/Fx0d3wgOHoUnj+tBFxPUUcyAF/GQxE=
Message-ID: <e4b25205-af63-aff5-dbcc-9a16aa86b07d@lear.ch>
Date: Sun, 13 Mar 2022 14:46:08 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: Lars Eggert <lars@eggert.org>, Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org, "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, Jay Daley <exec-director@ietf.org>, Internet Architecture Board <iab@iab.org>, Mirja Kühlewind <ietf@kuehlewind.net>, 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>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <AB5E3E46-D450-4E21-B67B-D639F67734AE@eggert.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------MmusCkczrkas9Y3s5LR82neg"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/FO6Calv6a43LmhWFeKRkaNn5pIE>
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 13:46:38 -0000

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.