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> Fri, 11 March 2022 20:08 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 265F53A0121; Fri, 11 Mar 2022 12:08:33 -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=unavailable 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 70CMBg6Lo1vU; Fri, 11 Mar 2022 12:08:26 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 B4ADE3A02BB; Fri, 11 Mar 2022 12:08:26 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id e2so8534119pls.10; Fri, 11 Mar 2022 12:08:26 -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=abb2+3frJZsw/9r5ic3gSjIcr5E3y87Mjj4Yp90kNmg=; b=MRnEvFKhhRu9csKzGhdd8r1z/P9BlDd0qgqjsNfSsl0mMLXGxVF3b9N/nYLqCrB6qS rc12ImjPQcXmFvZoUMmUZJqgmP2AxA+FvOvXQomjiyHM+dfD1FXK2fEH58UuG47prYHG oMtPONYSVp0edmsUjaG5eElk5YnFRHi1qM6rNz1kx0+yaKnTxAZrY9rLpXtNn0qeV8rT He8oEIN9O5RJpSIGXb4egZcLz4D2gO2zWMsw39qo+caroBOstpYMvUhUTrLqeaCy0564 seqqulY17i5+FVMMbk1HJ3AnAxD0ZJ6bpqGUWAsxDzcySghH0HrpIMku/Sx3uz1DGtaf XtNw==
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=abb2+3frJZsw/9r5ic3gSjIcr5E3y87Mjj4Yp90kNmg=; b=KRIYwLJwZhWt9bq0CYg7TURm+Q+2z5MWQnqbSVhUZEYiVF1tEMP+oWsi765u901Kq9 x6aaaoJQAk/XOT95h0H5mpNbFLge0h4JlslcR9oDUpT9jK/diOCBkd9LX2ptZ/cMMt5s g4CaM+7lYZxnLBDjxRNwYhMa++7HwnMOxQML53QOJRZxlK6spsAGnyYrSzWkFaCx8HJa mVIVhm10GUyUBAkev71ABjw0xpnBOlI9W3SgTwAP1lfBprDSGjiI4fxRUoSYI4Lpm9pD jm9LlsbEfxYzslmldFANuCVA0uQOuzzDzUkZD+52+0bdWh5B071DYsg/QSKagE6cbO+B vJqQ==
X-Gm-Message-State: AOAM530q7KTW5s+eeWcIh1UPOQRoQ9sEV5Xmf+6yxYZ9ANFZFgUZb1yw tyQOxnfGYZLpl7LVnWZf/0I=
X-Google-Smtp-Source: ABdhPJwAnlagYwgr0mUSv7KeEJuBtofZOWMR7Pj1ZjzSo8khKFqVln0nv/LDkgE4cSCjZ5/DN4HR+Q==
X-Received: by 2002:a17:903:2490:b0:14d:57a5:a472 with SMTP id p16-20020a170903249000b0014d57a5a472mr12085620plw.17.1647029305596; Fri, 11 Mar 2022 12:08:25 -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 s21-20020a63dc15000000b00378c9e5b37fsm8853879pgg.63.2022.03.11.12.08.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Mar 2022 12:08:25 -0800 (PST)
To: 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <8b51b14e-7342-7336-2d3a-e163bf640c89@gmail.com>
Date: Sat, 12 Mar 2022 09:08:19 +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: <AB5E3E46-D450-4E21-B67B-D639F67734AE@eggert.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/r3LW6ocoYpS1QMYZgqYypy64rRg>
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 20:08:33 -0000

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