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

Peter Saint-Andre <stpeter@stpeter.im> Fri, 11 March 2022 20:40 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 422D83A08F2; Fri, 11 Mar 2022 12:40:52 -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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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=nmC1pGb5; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e9Qzj1aR
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 S0jSFdvg6Ap8; Fri, 11 Mar 2022 12:40:47 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20B283A0933; Fri, 11 Mar 2022 12:40:47 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D01DF3200AC9; Fri, 11 Mar 2022 15:40:43 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 11 Mar 2022 15:40:44 -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=kC3gVwYjs/hUNm L5m/PBzyAxwPsDCzilrx3KwVx/iHo=; b=nmC1pGb5mhxPTLslKG9ltfc0mDh1BL xy/w9ddTqF9guv0FMmIGRjDh2En7wwkC+IQdmaGrVzRodricw9/fvNrJpl/NgxBW zSNGrcSJ6mO2Z0JmxLB80QS/+J+YO3Vx9Djpgv2YgeXnp+VkIgJDqHhyrVk0Ge6d TGwmUFR9wVBdmCBV6IWQXeDD0GoO2EktM2EpYiqmOkbohNGZiLc6p0yu7H2gQBwI 15YRtlZd71ReB68zJ9EXyVxkJvxUW6AbS0BAg+Tx0dACyllN0O3TiPXKD/Z6wTAF Ao4hdqJuZwufgw0YddYv8PICJFjKdRCHxXba02mk/iW/ZmnvkMx6OeXw==
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=kC3gVwYjs/hUNmL5m/PBzyAxwPsDCzilrx3KwVx/i Ho=; b=e9Qzj1aRw/UsFaHsCuVXV7cVhoVkPT7wn1OYPvbxNeQ3Nog9ZeS/1N0SJ O6qC7sgXttCzf9HutVJwQBP8I+czKiDc7lcLfwy7/UPsfkYmsMv9tEfmghrKrP52 +lNfzcyqE4Md0wnEAwolARlXudFIvz4cNbONv++kXS+q2FKfJvRifbWAah6ksp1G cK9MDerU1n7gCxm5VAKYMejgbYxXD1Z8p0MNlemtD3kJKA4YvFXKPNfehAsu0YZf iH0liVtxbwpbypdSkJRAg1iXCI6GwosOIoeSMV/tN9lxcS7RwM+bwQMp3/haKuYp 6BWMYL9zl7CP66eS+PlyLC6wBJM0A==
X-ME-Sender: <xms:yrMrYsIiE29K6alIwZzgXAUB5D0dS_8yGECPOVEaKZqwreJPdpJDug> <xme:yrMrYsI0LgutMpYI0_4i6IDBLo4s9Iy0_Pc45deagCDqLLSABwd9F16tpChxuduYN VVmFje5X0Yy_-l24g>
X-ME-Received: <xmr:yrMrYssaSxxkbmedDzcTQco_qBBljJDPt9jqA6A70xE6vbwYO2tuNs8VDeLCcvR4ymQAbBQcjx1pk6jPaiCiJQa2Jo-EP4srbQ7GWjw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvvddgudefjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeekgeeltdetueeujefhgfdvgfdvkeetheetfeeuhfetheeh jeejudduffekjeefudenucffohhmrghinhepihgrsgdqrhhftggvfhguphdqrhhftggvug dqmhhouggvlhdrnhgvfienucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:y7MrYpY2FIjDijoGaJO7ZzmRjBAduDD_X7F0i15s00Q5ctjriMqCfg> <xmx:y7MrYjbGMbwAOnLhmWkATSVihYiZltzu44HZrHVG49tAhBEbxpUNYg> <xmx:y7MrYlCF9OcBQEZvbsYRWVx7cYN3eXBfiavec3VmV4OA0VpwZd0fbw> <xmx:y7MrYn5zds1UEg0nSQg_dh_RzZfPtb828cRnsp5L23qVacOlVhMMwA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 11 Mar 2022 15:40:42 -0500 (EST)
Message-ID: <066b58ac-ad6c-e5f0-5260-1b9e0267f198@stpeter.im>
Date: Fri, 11 Mar 2022 13:40:37 -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: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lars Eggert <lars@eggert.org>
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>
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> <8b51b14e-7342-7336-2d3a-e163bf640c89@gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <8b51b14e-7342-7336-2d3a-e163bf640c89@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/hdIyfErJyrjQTi_1qO8RgrhFpIg>
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: Fri, 11 Mar 2022 20:40:53 -0000

+1 to removing the liaison (no one seems to think it's needed) and +1 to 
the proposed text.

On 3/11/22 1:08 PM, Brian E Carpenter wrote:
> *If* there is consensus to remove the liaison, here is is my proposed
> update to draft-carpenter-rfced-iab-charter.
> 
> OLD:
> Note that RFC 2850 states that the RFC Editor appoints a liaison member
> to the IAB. This does not change, but refers to the RFC Editor function
> as described in {{I-D.iab-rfcefdp-rfced-model}}.
> 
> NEW:
> RFC 2850 states that the RFC Editor appoints a liaison member
> to the IAB. This is no longer necessary.
> 
> ADD to the "Changed text" section:
> In section 1.2 of RFC 2850, entitled "Ex-Officio and Liaison members"
> the phrase "the RFC Editor," is deleted.
> 
> Regards
>     Brian Carpenter
> 
> On 11-Mar-22 22: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.
>>
>>> but will that need another last call? Awaiting instructions...
>>
>> I think - but would not mind to be convinced otherwise - that change 
>> would better be last-called. I can't recall of the top of my head 
>> whether a two-week repeated last call would be possible, or if it 
>> needs to be four weeks again.
>>
>> Thanks,
>> Lars
>>