Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 12 March 2022 00:41 UTC

Return-Path: <brian.e.carpenter@gmail.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 5EBAE3A088C; Fri, 11 Mar 2022 16:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UGgLl4etHFbT; Fri, 11 Mar 2022 16:41:07 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CED183A085B; Fri, 11 Mar 2022 16:41:06 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id g19so9262742pfc.9; Fri, 11 Mar 2022 16:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=IOPNmwZGGvizFZommSABj/drpQeKsbXyUNYWkoOjHNk=; b=au8HINYjfO12GqoQtBL53NqGj4jD6HGd90Hp4c+TeiK4nSMBcaYbYALcVGghKSqssI wh8p6C8K9GjjrEgcHO5w29K3UW02o2ndOFiG7Edia+IMKkId9UdFLZldH+lJ00hkTiDp d8O/Ttmda1WluDaajjRWSUwOSypAwlbKCGZ0b8lHMNwEGDMlxnLPvQ13cXzX7wa6chHm q0h63NhUbNHZfdwc4mPDAXgXqlmglDNnEEpAxOTHv9Tks9B61RIupZWgdArTH6GcuMZT mCZFrDjh8mwDmArOBzsZhn5oE7C4MHkorM7ehJeuJYe7zVgZTlGUnyoRPZ/vMQytoomm pGYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IOPNmwZGGvizFZommSABj/drpQeKsbXyUNYWkoOjHNk=; b=Z7H9THBO6YDr6127kyc4b8yD+oFV/w63ni4SpNjuYwMreG+HwOZEpS45KcmfhC20wB Pau5oobKcAKKaA7+zGYrrdJ+wgbb3iIoxRnjjHAm+vJh0yTiHtxBnahpJX1prn9yjoXu NSfMFlTyIBQg+94KqLwf1WyLUPM8LTcW368kS9NminqdGPSsxXKT3ztp3SAj/Y6Y6UxI JKMZaMJnUdY/EXgwn1GiywLRjkEKU40v8teSG9lvPGi6p0W0DKrhWukLyt2i8Z4Hg3lX YZ8m0ztxmnuDnFM6+MvZ1hElXbjcibMI86pguObAjsRtmN8Ofe+r5i9Gj3NJWrsn593L /PMQ==
X-Gm-Message-State: AOAM530mGwG9QidL1FEGDByjXz2RDDcE+cHLVpdqi6CfysWnV/l5t12V UFrRE51oOrCd3o3QJqhhiqQ=
X-Google-Smtp-Source: ABdhPJzDj9xcUW3p9sIQO7d5p4YRbOSVEMSE3VCp8ZnVrgqL+HRNhqcGp7T+aEnn9MD0A5vc1T1tYw==
X-Received: by 2002:a05:6a00:2181:b0:4f6:f1b1:1ba7 with SMTP id h1-20020a056a00218100b004f6f1b11ba7mr12502483pfi.73.1647045665754; Fri, 11 Mar 2022 16:41:05 -0800 (PST)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id p128-20020a622986000000b004e1366dd88esm11340717pfp.160.2022.03.11.16.41.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Mar 2022 16:41:05 -0800 (PST)
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Peter Saint-Andre <stpeter@stpeter.im>, 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>
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> <066b58ac-ad6c-e5f0-5260-1b9e0267f198@stpeter.im> <242ecf9f-f7c7-7ff6-4199-ad8875b7ac6d@it.aoyama.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b17d4b9d-9456-41a7-0a62-45d35d2fbb07@gmail.com>
Date: Sat, 12 Mar 2022 13:40:59 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <242ecf9f-f7c7-7ff6-4199-ad8875b7ac6d@it.aoyama.ac.jp>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/XhRTgEDx_ODDMd9JIce3ALClGvY>
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: Sat, 12 Mar 2022 00:41:10 -0000

On 12-Mar-22 13:21, Martin J. Dürst wrote:
> On 2022-03-12 05:40, Peter Saint-Andre wrote:
>> +1 to removing the liaison (no one seems to think it's needed) and +1 to
>> the proposed text.
> 
> +1 from me, too. I'm also okay if John Klensin's text gets included, but
> I don't really think that text is necessary. The IAB can talk to anybody
> they like at any time anyway.

Another point is that the rfcefdp program would be stepping outside its
role to propose a generic change to the IAB charter. I'd expect that sort
of change to be proposed by the IAB itself.

Rgds
    Brian

> 
> Regards,   Martin.
> 
>> On 3/11/22 1: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.
>>>
>>> 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
>>>>