IETF Logo Mail Archive

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> Thu, 10 March 2022 21:24 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 9F1DB3A1C13; Thu, 10 Mar 2022 13:24:12 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=YipF6xdZ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=INkwEmGd
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 SEURFkLuf6KT; Thu, 10 Mar 2022 13:24:08 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32E33A1C17; Thu, 10 Mar 2022 13:24:07 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id CC4A93200F72; Thu, 10 Mar 2022 16:24:06 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 10 Mar 2022 16:24:07 -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=Hc9HGM8TnioeIF RQ5+Qyb4Md4+zNljhWAp0Ju2H7mZ4=; b=YipF6xdZpciHtPP1qkeeVXwSARJeSY fvh5I0EKcnTLv+4oEXzxJb7bazvfswq6GBWGUftx6UJto4pdi9H2DgMhn8nEIZ1X c40eaT85wyPFyZPs8/GSYOZaM7q7ZK1oAcWWy6psEwkslxrXgMLzsV3GQ2rVY/ED Jxa6ka3zFxIIsjYY4cYLFIjuoNSFO8/O2Bx+gW2PF3yg2N8hoa2JO5rIs/mviYBL Kq0qJ6jd62jS/P4TwZEfPc7ez5JfWtfeV3whuzQuhiRCwdFvjHVwYYprSk8bao5N JqkQ96zhYwkvdcou4P8b0FPouAVrMyKbz6k5rY0sJH2zhHI+/TEr9cjQ==
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=Hc9HGM8TnioeIFRQ5+Qyb4Md4+zNljhWAp0Ju2H7m Z4=; b=INkwEmGdRoVr9PVQZDKFCRogdNFhko/HZ3Knm1xGE5huUUr6mfKdxIRD2 FVeBTKVjag5VEX3bT/Iu3TKWT79kUkLocgLGuFE6YtQdcafaILVhMgNFjcFboXI5 WxE9oI7WWGuN6iGoqJEwqoHn48AimyTD/QPD95g7qTOO9np4ZBxSfsijYWMHXCGn Soon+vDMu6VUI4xN2W/t0jyrYP0azVEnnlLwYDKjP6gH0R58ACsS+QK8tf85/KEe 8DOAiFFVccmacIPQaJrJ4NVNCm9qFQINR2guNvyztBTRXBcWIg7tLeBD0Uwntwxu At28Gi2a5nxWstwrNuv3qwxKYU5QA==
X-ME-Sender: <xms:dmwqYnrbYqs9_HUAsKfQDF-d1o8iMTxtGXJMFWt0K7PlhYwps_l00w> <xme:dmwqYhortTLrgtlBS45pXFitW9gCmk6dyAW6DysabvLMQ8JhXKgi533mB0SEFd6EA fw5dgribyLuRCDADg>
X-ME-Received: <xmr:dmwqYkMONZuCAXyr0K8B9TEgnWdR-IcRxuqXT0Cn5OGOO8lsHfToEntGv64YJJaH2PUIwOpxINasXJQSykCeKR5IdbkSHqbWNt9F5K0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvtddgudehtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeehtefhvdejvdfhgeetgefhfeeuudefkeetvdfhkeelleeu heefleekkeekieffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:dmwqYq6wDkVdsHZCsLYHL5I_4IeL13UM0HKu25QjhnFqwLgpz0aW8A> <xmx:dmwqYm5SqZoBiBT3y7S4BP0OFLFOyQTCsDT1PBf9G8w8hop21TFDeQ> <xmx:dmwqYiiJddxuQ4PaipYeN-Kv0EuZB5zpEbcxvIC6gMraDsclUCrbHA> <xmx:dmwqYjsThig_So2AR6knlPJ5X9FfZ2K7tUb2eCLEgq2p8ne7LkApfQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 10 Mar 2022 16:24:05 -0500 (EST)
Message-ID: <833958c8-a12b-0f5a-4c66-30fa87549b8c@stpeter.im>
Date: Thu, 10 Mar 2022 14:24:00 -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>, Mirja Kühlewind <ietf@kuehlewind.net>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Internet Architecture Board <iab@iab.org>, The IESG <iesg@ietf.org>, "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com> <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im> <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net> <702330E0-0D47-47AD-8434-C6F1EF6CA40F@eggert.org> <6dabea27-8abe-4251-f9a1-8e8297c64fb4@gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <6dabea27-8abe-4251-f9a1-8e8297c64fb4@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/e27ybWABYLhNxpp4vnRYXHhDoKQ>
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: Thu, 10 Mar 2022 21:24:13 -0000

On 3/10/22 2:20 PM, Brian E Carpenter wrote:
> On 11-Mar-22 10:13, Lars Eggert wrote:
>> Hi,
>>
>> On 2022-3-10, at 22:57, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>>> It seems like this is actually something we might also want to update 
>>> as well in draft-carpenter-rfced-iab-charter. Brian? Lars?
>>
>> I agree that any changes, if the community or the IAB desires them, 
>> should be added to draft-carpenter-rfced-iab-charter. This would 
>> probably entail another IETF LC, but so be it.
> 
> No, I disagree. It's not the receiver of a liaison that specifies how 
> the liaison is appointed, it's the sender.

Right. So I think the question is, as Mirja said, whether the IAB and 
RPC feel that the RPC needs to have a liaison to the IAB (if so, the RPC 
would be the ones to appoint that liaison). [1]

Peter

[1] Because the IAB appoints a member to RSAB and appoints a chair of 
the RSWG, I don't think the IAB needs a liaison *from* those bodies.

v2.23.0 | Report a Bug | By Email