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 22:13 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 3CC633A1C7B; Thu, 10 Mar 2022 14:13:06 -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=q2jelmOB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GKEvjlQf
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 iGX-eJAgewc0; Thu, 10 Mar 2022 14:13:01 -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 977563A0C32; Thu, 10 Mar 2022 14:13:01 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 826FB3200564; Thu, 10 Mar 2022 17:13:00 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 10 Mar 2022 17:13:01 -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=OspJkTiE7ed8hy kYDjV+CJlO+xakWOpKO9JIf8bYclQ=; b=q2jelmOB0li4cveCPwIUcgDHd1oAGC qQVgoSjUlWyBzYATPD8IxvlDAS7qa3YevRfWcAeDT/qvGtaM9GC5824cicsfx9ct yywrilAEK+IJ95oKgnf16iOCaHOiZoR2/PZD1PXbzUVMY3LoZZf6XC3UyvOo5dsk L0YEazV6dYRMXC8brjwPvmMmPyyuTINcpaHJQRm2F1Y+qFWpv3vDnBVbHv03qWAQ VsLMgYsYu9KolhgeIwfSzjMrP5P+o4zGIyCJIi/+RbSlBxFyAJnKI+HikH3NgQ4b 24Ez9SBywDU7tk4lg+GMugMHlJaJZWlh1em6HHz+TNL4ZYxVRIib/PXA==
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=OspJkTiE7ed8hykYDjV+CJlO+xakWOpKO9JIf8bYc lQ=; b=GKEvjlQfVMnumSgHMKlApxfDDD8lryO07M9PLXOKsMQ4G/EwHD25aViqV v9gQ693uISMnXg6TL2Twnzo5MIK4TdL53T4pyp8N7h9Qxl3Fp7hZTc4uku1QkEBy ENoP7Afx+l0s51bGgTVJVxQKYTo8GnYULZrXYc8RSpSFOG9hZReylXXZSZRwevzQ yZZ1D8naFy6pHjgvm6shpD21W6uss/Xr1Q1Wr8VcwmT7LRtnG29obRG79KggH43Z oVWNjRa8QNVcC8mjqOPQrI+lGGphv3qt31AfpFtKePXjuk6E+N702VsDIgHAmKZ1 dYGbOJ69BNVsjiBRru5Ai556n6LIQ==
X-ME-Sender: <xms:63cqYhQf_-UN8I9jZi8LBEcpW-0gBhkeXtgQCYa8dfjS1yWFB1j4yw> <xme:63cqYqxP8mmQlXjZHreEYzbKiA_-EkizrcEf8YmDNjc-HAwkHWGonIrhD7hX7v0zc PHrZMUbg6S3-zUo-A>
X-ME-Received: <xmr:63cqYm3MsGFnXcC8vSstnpzmSlYBzLU_zb2swDb_f7PrAk_3xQYbgL8lOump0dMAPrWhVxi3IEYXZDvY7L2tCuSkksyoqhyzPW1JLl8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvtddgudehlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeevtdfgteetgfffveehtedvudegudfgleevfedtleevtefg feeggffgfeeludekheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:7HcqYpBkUK86otHD5gd7-YrYDDMvXM7_lu5Vs3CSkF5CbgWYgOJwWA> <xmx:7HcqYqj1l7AWIMCMzusR11xxUSTYj7wM8eOjSxqowU-3lU2rZIehuQ> <xmx:7HcqYtokL1-FD9A6WEzDYy4OhaBUQ7eb6MGLniC_tdMzSpc_CB94xw> <xmx:7HcqYugcf1cuWcG5oax7aW7aPYVsSkPWR81XkTJrZ6XkDiqYLsJpuA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 10 Mar 2022 17:12:59 -0500 (EST)
Message-ID: <d4ac965c-65b1-e909-864c-cb14e27a3b0f@stpeter.im>
Date: Thu, 10 Mar 2022 15:12:58 -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: Jay Daley <exec-director@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Lars Eggert <lars@eggert.org>, "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> <bf702de8-a876-3d9f-23d8-4ba49f86bd05@gmail.com> <E8C97678-AD00-402B-9646-DEFF6E76263D@ietf.org>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <E8C97678-AD00-402B-9646-DEFF6E76263D@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qGNXkU_EW8rsNPcUnPEu0GW2hTA>
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 22:13:06 -0000

On 3/10/22 2:32 PM, Jay Daley wrote:
> 
> 
>> On 11/03/2022, at 10:16 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> On 11-Mar-22 09:57, Mirja Kuehlewind wrote:
>>> This is indeed a good question. Thanks Rob for bring this up!
>>> I actually think there are two options here: either the IAB could have a liaison from the RPC or, if the RPC thinks this is not needed, we probably just don’t need a liaison in the new model. This seems like the only two option to me, given we definitely don’t need a liaison from the RSAB as the IAB is sending one of the representatives and I don’t think it practically makes sense to have liaison from the RSWG. Or maybe having the RSCE as a liaison to the IAB could be another option but I don’t think that would be of real interest for the new RSCE role…?
>>> It seems like this is actually something we might also want to update as well in draft-carpenter-rfced-iab-charter. Brian? Lars?
>>
>> IMHO, no. The IAB asks for a liaison *from* the RFC Editor function,
> 
> Asking the function for a liaison made sense when there was a single point of control that could make that decision.  Under the new model, there isn’t that point of control.  As the draft text proposed by Peter puts it:
> 
>> 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.
> 
> We’re going to need a whole new complex process just to sort out how these individuals parts are to agree on a single liaison, if "asking the function" continues to be the way forward.

Right, and I suggest that we avoid that complex process by not having a 
liaison to the IAB from the "RFC Editor Function" (if the IAB and RPC 
etc. feel that we need a liaison from the RPC then that's much easier to 
arrange).

Peter

v2.23.0 | Report a Bug | By Email