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

Peter Saint-Andre <stpeter@stpeter.im> Fri, 18 February 2022 16:02 UTC

Return-Path: <stpeter@stpeter.im>
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 2C9E53A11B0 for <rfced-future@ietfa.amsl.com>; Fri, 18 Feb 2022 08:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=BSbP3bLK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=krkcDgQ7
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 k5NpcvHBIoTY for <rfced-future@ietfa.amsl.com>; Fri, 18 Feb 2022 08:02:10 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BAAF3A11B3 for <rfced-future@iab.org>; Fri, 18 Feb 2022 08:02:09 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 1DD583201D5E; Fri, 18 Feb 2022 11:02:09 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 18 Feb 2022 11:02:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; bh=JPs97ElNUqyxVh R3RmMSRdzrXe5tPlwEWwE11mPE/vE=; b=BSbP3bLKZuNcVywQnCAvLYvy+ltC9K Gsepx4dMq53xi05mM5a8L1fZL71cMjtPNGHFImPDs6T5vRmdjGluZR6gDkTgrQEE yhhItlVxK52t2/sbM+Hvdx2JxXnymBaMU341xAMDkrDaOGgiFkUUZ6J8DRemxjAU LEFYndJqRcfHdpzhZ8wZR/jR5k1jQHqN9vvZ0oFzX0X47NBsRmoKB6incjv9X9R0 TImR7rB0G9hxQZa5gHZQksNZx9XssCxzmImp/SfRkundXaRfC0wZ0/ZrliA2B8Gg aehjxmVPgH8o1R17Kz91L61WTuhCcectEgXKXrqCz86pk3qly+Ge7DxQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=JPs97ElNUqyxVhR3RmMSRdzrXe5tPlwEWwE11mPE/ vE=; b=krkcDgQ7Or0FZ/mt082wZcld3PJBmmKgFtdX7/f1q5S5sgKAKbM+Mf2cc ZogJ13NLljW2xCuuPME4Y9ECxSOPVI5SJQeCqitq70ZB4S/flc3U2TSS/+QgA7WP 5kBfeMWHvks/wACAHWtgO0YzOswnMyd8nhJhT94A2YWzG9IzS2U+Bm5OQ6gX4zWc J146RHikVdd3qv6uYNQV6jL31D+yPHVguCsbYG5yfdCRWKL6mq+mAuFXzVPQ0QAV +qTpeB4SScHVN+98wbCqMcEZ1jw/mSsjoYnPe3X1eGZOXVxVyyiRYD2IgLmFv/sC OhXqdSFU+G93zzPk44D8oCbFp++rg==
X-ME-Sender: <xms:_sIPYp6ZlqOkPhv1Axyb-7QvDFdkZPhQO7-4z9wLZME7CWnv53EjRg> <xme:_sIPYm54wd5VUCvut15tBr1D7H6PBflh3253fROiK6ySxu32iSeO1SL9l0vjaFxNZ lLFLx8iCANyw2QUAQ>
X-ME-Received: <xmr:_sIPYgdzWwty3Yis5tvlAHXcThLLKZbuGLz8rw9MD83cNU_AXKkMoz5hSrVkhc72Xw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkedtgdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtgfgguffhjgffkfhfvffosegrjehmrehhtdejnecuhfhrohhmpefrvghtvghr ucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqeenuc ggtffrrghtthgvrhhnpeegtddvteevfffgheejjeeludejjeehuedtteffheejgeffledt tdfgjedtveeuudenucffohhmrghinhepihgrsgdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghr rdhimh
X-ME-Proxy: <xmx:_sIPYiKwn2Bah7eNWQMxZzX6eaCXVowXkaw4kAup8a4zpcT_T86vrg> <xmx:_sIPYtJO2LP-PQ0Ms5MTDO1fNkd10cBarndlzlesi6E_YlrNs27uew> <xmx:_sIPYrzXaDDYXzvBcv6SgA4E7ka-uNTYqkbJTcDAVwMemHQFOeaCSw> <xmx:AMMPYkWk-xYqHaSsflc8kmx9MynvzIROMquJIbGSc7HpKHx-STabkw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 18 Feb 2022 11:02:06 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail-C4DFF485-9243-45D1-9283-71E326561C18"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <CANMZLAbkKMwVCkjFWqrSvSHNwWgO1JKbDmcQ0Ak+byATHdXKaA@mail.gmail.com>
Date: Fri, 18 Feb 2022 09:02:05 -0700
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, rfced-future@iab.org
Message-Id: <CE03239A-5C28-483B-B6D8-E52464562D18@stpeter.im>
References: <CANMZLAbkKMwVCkjFWqrSvSHNwWgO1JKbDmcQ0Ak+byATHdXKaA@mail.gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: iPhone Mail (19C63)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/UUjTTbJWuWycET-3xlIntS8zi1Q>
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 16:02:15 -0000

Yes, this seems reasonable.

> On Feb 18, 2022, at 2:21 AM, Brian Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 
> wfm
> 
> Regards,
>     Brian Carpenter
>     (via tiny screen & keyboard)
> 
>> On Fri, 18 Feb 2022, 22:09 Martin J. Dürst, <duerst@it.aoyama.ac.jp> wrote:
>> On 2022-02-18 07: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.
>> 
>> The people on the RSAB should all have quite a bit of experience with 
>> getting organized, so I don't worry too much. If we need somebody 
>> formally, it could be the IAB chair, as this would be the hand-off from 
>> the IAB to the RSAB.
>> 
>> Regards,   Martin.
>> 
>> > Regards
>> >     Brian Carpenter
>> > 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future