IETF Logo Mail Archive

Re: [Rfced-future] Who initially convenes the RSWG and the RSAB?

Eliot Lear <lear@lear.ch> Fri, 18 February 2022 09:08 UTC

Return-Path: <lear@lear.ch>
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 494993A0C10 for <rfced-future@ietfa.amsl.com>; Fri, 18 Feb 2022 01:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level:
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 yaq8GrTFyUDj for <rfced-future@ietfa.amsl.com>; Fri, 18 Feb 2022 01:08:13 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EF8F3A0C3C for <rfced-future@iab.org>; Fri, 18 Feb 2022 01:08:11 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::8] ([IPv6:2001:420:c0c0:1011:0:0:0:8]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 21I986SQ310245 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 18 Feb 2022 10:08:06 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1645175286; bh=j2O/5XIsoMvlXNmdXyy0PpdX0NqoZem7Ikthd3xEt7s=; h=Date:To:References:From:Subject:In-Reply-To:From; b=ImOheUjQ94Wi+uknU86hLzHfIRUSDG0TI3StnGAjVxfYTLbxMx3CIP4nljPpt4b+c rCGw9IvOHytZN6yK9/q6HE4AwToYOp0PTcWw+xEEEadSoup0TcEsGQrTJLWgxF/MmA 7z628XvbcKIqlyKj5fO8um9j6lcE+usPpKVGHWPQ=
Message-ID: <b53a7f46-10ea-8a02-f9bd-64b34a78dfad@lear.ch>
Date: Fri, 18 Feb 2022 10:08:04 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "rfced-future@iab.org" <rfced-future@iab.org>
References: <4ad40a10-b7ad-f8cc-b1c4-a460f94e1997@gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <4ad40a10-b7ad-f8cc-b1c4-a460f94e1997@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------hZ2N2Z0q0OExllvQsVBh7ehb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/lGTILcAi-aDsOl0QLJFfeseThJo>
Subject: Re: [Rfced-future] Who initially convenes the RSWG and the RSAB?
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, 18 Feb 2022 09:08:19 -0000

Hi Brian,

With regard to the RSWG, my read is that the actions rest with the IAB 
to have a plan in terms of how they will appoint chairs, but I don't 
think we can ask them to execute on that plan until 
draft-iab-rfcedp-rfced-model is approved.

The RSAB is formed by the approval of the document, and we should just 
allow that they will take the action to appoint a chair.

The chairs can then convene the groups.

Eliot

On 17.02.22 23:36, Brian E Carpenter wrote:
> Hi,
>
> It just occurred to me that I don't believe we say anywhere in the 
> draft who will take the actions to convene the RSWG for the first 
> time, or the RSAB for the first time.
>
> I don't think we necessarily need to add this to the document, but 
> would be good to know that *somebody* owns those two actions.
>
> For the RSWG, it would presumably be the co-chairs, once appointed. 
> For the RSAB, it's arbitrary, since the RSAB picks its own chair, but 
> I think somebody should be identified.
>
> Regards
>    Brian Carpenter
>

v2.23.0 | Report a Bug | By Email