Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]
Jean Mahoney <jmahoney@amsl.com> Fri, 11 March 2022 00:00 UTC
Return-Path: <jmahoney@amsl.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 C201B3A0B91; Thu, 10 Mar 2022 16:00:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=unavailable autolearn_force=no
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 7vvA8VO295Ga; Thu, 10 Mar 2022 16:00:04 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 507073A0BB5; Thu, 10 Mar 2022 16:00:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B54FF427C643; Thu, 10 Mar 2022 16:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id en9cxcg34UQy; Thu, 10 Mar 2022 16:00:02 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 402D2427C641; Thu, 10 Mar 2022 16:00:02 -0800 (PST)
Message-ID: <777e0c64-fd7b-6c04-916c-a17cb211110e@amsl.com>
Date: Thu, 10 Mar 2022 18:00:01 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: Mirja Kuehlewind <ietf@kuehlewind.net>, Peter Saint-Andre <stpeter@stpeter.im>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Lars Eggert <lars@eggert.org>
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>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/YJBovqHyWC9_xK2qyOj9vRnhrjQ>
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 00:00:09 -0000
Hi all, (with my RPC hat on) On 3/10/22 2:57 PM, 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. [JM] The RPC doesn't feel that a liaison to the IAB is necessary; however, we hope the IAB will invite the RPC to participate in meetings as needed. Best regards, Jean > 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? > > > >> On 10. Mar 2022, at 21:13, Peter Saint-Andre <stpeter@stpeter.im> wrote: >> >> On 3/10/22 3:41 AM, Rob Wilton (rwilton) wrote: >>> Changing the title to help ensure that this comment is tracked against draft-iab-rfcefdp-rfced-model. >>> Still suffering from Covid, and I'm now way behind on email, so perhaps this has already been resolved, but I think that the issue below needs to be resolved before the document is published. >>> Regards, >>> Rob >>> -----Original Message----- >>> From: Brian E Carpenter <brian.e.carpenter@gmail.com> >>> Sent: 07 March 2022 19:40 >>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; The IESG <iesg@ietf.org> >>> Cc: draft-carpenter-rfced-iab-charter@ietf.org; rfced-future@iab.org >>> Subject: Re: Robert Wilton's No Objection on draft-carpenter-rfced-iab-charter-06: (with COMMENT) >>> Rob, >>> On 07-Mar-22 23:58, Robert Wilton via Datatracker wrote: >>> ... >>> >>>> Hi, >>>> >>>> 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]. >>>> >>>> It isn't entirely clear to me exactly who (as in which person or body) is >>>> actually responsible for appointing a liaison member to the IAB (given, as per >>>> draft-iab-rfcefdp-rfced-model, the RFC editor function responsibilities are >>>> split up into multiple entities). My assumption is that this would be RSAB, >>>> but perhaps I mistaken. Would it be helpful to clarify this - perhaps in >>>> draft-iab-rfcefdp-rfced-model? >>> Indeed, I don't think it belongs in the IAB charter. Hence I suggest that this >>> is really a comment that the IAB Program (in Cc:) should look at. >> This is a good question. >> >> One key assumption underlying version 3 of the RFC Editor Model is that the process for policy definition and implementation is no longer under the purview of the IAB. Therefore, I question whether the IAB still needs a liaison from the RFC Editor Function (whose responsibilities are now spread across multiple entities) and I would defer to the IAB (cc'd) on whether they think this is needed. (If so, we'll need to figure out who does the appointing, but one step at a time.) >> >> Peter >> >>
- [Rfced-future] Comment on draft-iab-rfcefdp-rfced… Rob Wilton (rwilton)
- Re: [Rfced-future] Comment on draft-iab-rfcefdp-r… Peter Saint-Andre
- [Rfced-future] RFC Editor liaison to the IAB? [wa… Mirja Kuehlewind
- [Rfced-future] IAB liaison [Comment on draft-iab-… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Lars Eggert
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Peter Saint-Andre
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Lars Eggert
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Jay Daley
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Peter Saint-Andre
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Jay Daley
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Jean Mahoney
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Eliot Lear
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Lars Eggert
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Eliot Lear
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Lars Eggert
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Peter Saint-Andre
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Jean Mahoney
- Re: [Rfced-future] RFC Editor liaison to the IAB?… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Martin J. Dürst
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Eliot Lear
- Re: [Rfced-future] RFC Editor liaison to the IAB?… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Salz, Rich
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Martin J. Dürst
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Peter Saint-Andre
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Mirja Kuehlewind
- Re: [Rfced-future] RFC Editor liaison to the IAB?… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Mirja Kuehlewind
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Mirja Kuehlewind
- [Rfced-future] A broader look (was: Re: RFC Edito… John C Klensin
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] RFC Editor liaison to the IAB?… Brian E Carpenter
- Re: [Rfced-future] A broader look (was: Re: RFC E… Martin J. Dürst
- Re: [Rfced-future] A broader look (was: Re: RFC E… John C Klensin
- Re: [Rfced-future] A broader look (was: Re: RFC E… Martin J. Dürst
- Re: [Rfced-future] A broader look (was: Re: RFC E… Carsten Bormann
- Re: [Rfced-future] A broader look (was: Re: RFC E… Eliot Lear
- Re: [Rfced-future] A broader look (was: Re: RFC E… S Moonesamy
- Re: [Rfced-future] A broader look (was: Re: RFC E… John C Klensin