Re: [rsab] Bringing forward next steps

Cindy Morgan <cmorgan@amsl.com> Thu, 26 May 2022 20:32 UTC

Return-Path: <cmorgan@amsl.com>
X-Original-To: rsab@ietfa.amsl.com
Delivered-To: rsab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBACC157901 for <rsab@ietfa.amsl.com>; Thu, 26 May 2022 13:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-xRBIVxzuCV for <rsab@ietfa.amsl.com>; Thu, 26 May 2022 13:32:11 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C1C2C15791C for <RSAB@rfc-editor.org>; Thu, 26 May 2022 13:32:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 02F91427C641; Thu, 26 May 2022 13:32:11 -0700 (PDT)
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 LiRfPSYtiLCh; Thu, 26 May 2022 13:32:10 -0700 (PDT)
Received: from [10.0.1.10] (c-24-6-24-199.hsd1.ca.comcast.net [24.6.24.199]) by c8a.amsl.com (Postfix) with ESMTPSA id D8FA5425C195; Thu, 26 May 2022 13:32:10 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Cindy Morgan <cmorgan@amsl.com>
In-Reply-To: <F73C7749-8CEC-4860-9500-0CEFF3E933D5@ietf.org>
Date: Thu, 26 May 2022 13:32:10 -0700
Cc: RSAB@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E87EC9E-3066-437E-8886-587EF914FC79@amsl.com>
References: <F73C7749-8CEC-4860-9500-0CEFF3E933D5@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/bpmqIo45WXDS9tpvJPMHvyHn8V4>
Subject: Re: [rsab] Bringing forward next steps
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "RFC Series Approval Board \(RSAB\)" <rsab.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rsab>, <mailto:rsab-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rsab/>
List-Post: <mailto:rsab@rfc-editor.org>
List-Help: <mailto:rsab-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rsab>, <mailto:rsab-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2022 20:32:15 -0000

Hi all,

I know that we had originally targeted May 27 for the RSAB announcement, but looking at draft-iab-rfcefdp-rfced-model again, I think it would be cleaner to wait until the RSWG chairs have been named so that we can announce RSAB and RSWG together. Section 3.1.2.6. says:

   The RSAB shall announce plans and agendas for their meetings on the
   RFC Editor website and by email to the RSWG at least a week before
   such meetings.

Given RSAB's role and how it ties into RSWG, I think the announcement will need to refer to the RSWG list, but I don't think we want to actually point people at the list until there are chairs in place to moderate it.

(The IAB and the IESG have interviewed 4 of the 7 RSWG Chair candidates. 2 more interviews are scheduled for next week. One candidate had to cancel earlier this week and we're trying to find a new time, which at this point looks like will likely be during the week of June 6.)

Thanks,
Cindy

> On May 18, 2022, at 6:51 AM, Jay Daley <exec-director@ietf.org> wrote:
> 
> Hi all
> 
> Lars and I were hoping it would be possible for us to bring forward announcing the RSAB and this list, and to get on with arranging our first meeting.  Currently the announcement is scheduled for 27 May and no date is set for our first meeting.  While we are still waiting for the Datatracker page to be set up (some tools work is needed for that) and the RSCE recruitment is not set to complete for another couple of months, I don’t see any reason to wait for those.
> 
> Any thoughts?
> 
> Jay
> 
> -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> 
> -- 
> RSAB mailing list
> RSAB@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rsab