Re: [rsab] Bringing forward next steps
Mirja Kuehlewind <ietf@kuehlewind.net> Fri, 27 May 2022 15:45 UTC
Return-Path: <ietf@kuehlewind.net>
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 F36D3C15EB5E; Fri, 27 May 2022 08:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 eBDJT2AfMuaz; Fri, 27 May 2022 08:45:41 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B4E1C15AE3E; Fri, 27 May 2022 08:45:41 -0700 (PDT)
Received: from dslb-002-206-011-005.002.206.pools.vodafone-ip.de ([2.206.11.5] helo=emb-w4epjhc9.fritz.box); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1nuc9h-0005pJ-Ii; Fri, 27 May 2022 17:45:37 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <4E87EC9E-3066-437E-8886-587EF914FC79@amsl.com>
Date: Fri, 27 May 2022 17:45:36 +0200
Cc: Jay Daley <exec-director@ietf.org>, RSAB@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6816F68B-8B5B-464C-B58D-D3CF52CFECF2@kuehlewind.net>
References: <F73C7749-8CEC-4860-9500-0CEFF3E933D5@ietf.org> <4E87EC9E-3066-437E-8886-587EF914FC79@amsl.com>
To: Cindy Morgan <cmorgan@amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1653666341;ac4bbfe4;
X-HE-SMSGID: 1nuc9h-0005pJ-Ii
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/ZC2rw7q4H9u8gu27eKnw0JHwhSQ>
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: Fri, 27 May 2022 15:45:46 -0000
Hi Cindy, Thanks for the update. I’m okay to wait for another 3-4 weeks as long as we can it announce at leats a few weeks before IETF-114. But otherwise I don’t see any reasons to rush. Mirja > On 26. May 2022, at 22:32, Cindy Morgan <cmorgan@amsl.com> wrote: > > 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 > > -- > RSAB mailing list > RSAB@rfc-editor.org > https://mailman.rfc-editor.org/mailman/listinfo/rsab
- [rsab] Bringing forward next steps Jay Daley
- Re: [rsab] Bringing forward next steps Mirja Kuehlewind
- Re: [rsab] Bringing forward next steps Eliot Lear
- Re: [rsab] Bringing forward next steps Cindy Morgan
- Re: [rsab] Bringing forward next steps Mirja Kuehlewind
- Re: [rsab] Bringing forward next steps Lars Eggert