Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]
John C Klensin <john-ietf@jck.com> Fri, 11 March 2022 23:19 UTC
Return-Path: <john-ietf@jck.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 F10033A130F; Fri, 11 Mar 2022 15:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 Kj3vKwurRxqi; Fri, 11 Mar 2022 15:19:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D9673A1304; Fri, 11 Mar 2022 15:19:44 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nSoXt-000It6-0X; Fri, 11 Mar 2022 18:19:41 -0500
Date: Fri, 11 Mar 2022 18:19:33 -0500
From: John C Klensin <john-ietf@jck.com>
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>, Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <0832CE84A09838F5F7426059@PSB>
In-Reply-To: <8b51b14e-7342-7336-2d3a-e163bf640c89@gmail.com>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/f1MhpF9kNtCFACThd3IfzsXvxIQ>
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 23:19:48 -0000
--On Saturday, March 12, 2022 09:08 +1300 Brian E Carpenter <brian.e.carpenter@gmail.com> 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. >... Brian, I would not presume to guess where the consensus lies but, I am concerned about backing ourselves into corners if things don't work out the way we (or, in the case, the RPC, anticipates) and requiring large amounts of effort to dig back out. So, at the risk of giving the IAB a little more authority over its own activities (something that should be no risk at all) and noting the liaisons to the IAB have to power to vote or otherwise make decisions as a consequence of those role, I suggest: (1) Using the text you suggest above. (2) Adding, as a new fourth paragraph to Section 1 of RFC 2850, something like: The IAB may, from time to time and by a procedure of its choosing, request that other bodies provide liaisons to the IAB. Such liaisons may be discontinued at the IAB's discretion by the same process. Liaisons requested and seated in this way will have the same status as those explicitly identified in this document. That way, should either the IAB or the RPC conclude at some point in the future that a liaison is needed (either long-term or temporarily), they just sort that out without the need to revise either your current document or RFC 2850. And, should the Internet evolve in ways we cannot anticipate today, we give the IAB the added flexibility to establish new liaisons as needed. I don't think it is necessary, but I would rather have this I-D (and hence 2850 revised) establish a place where the IAB keeps a record on incoming liaisons, what entities they represent and who the current representative is than to need to adjust the Charter any time a change might be appropriate. best, john
- [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