IETF Logo Mail Archive

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 21:55 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 2A4103A0E6F; Fri, 11 Mar 2022 13:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 4lZNPO5WQWa4; Fri, 11 Mar 2022 13:55:16 -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 65FC23A0E67; Fri, 11 Mar 2022 13:55:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 38952427C640; Fri, 11 Mar 2022 13:55:16 -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 1-DAjTR8vdzC; Fri, 11 Mar 2022 13:55:16 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id B2A98425C195; Fri, 11 Mar 2022 13:55:15 -0800 (PST)
Message-ID: <c029ed78-8754-f213-3cdb-5d0a151fc905@amsl.com>
Date: Fri, 11 Mar 2022 15:55:14 -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: 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>
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: Jean Mahoney <jmahoney@amsl.com>
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/iwz31SdB2ezmFLzVPBmhJLpIxWg>
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 21:55:21 -0000

Brian,

On 3/11/22 2: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.

[JM] The new text looks good to me.

Thanks!

Jean


>
> 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
>>
>

v2.23.0 | Report a Bug | By Email