Re: [rsab] Bringing forward next steps

Lars Eggert <lars@eggert.org> Mon, 30 May 2022 08:13 UTC

Return-Path: <lars@eggert.org>
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 C73F5C14CF0C for <rsab@ietfa.amsl.com>; Mon, 30 May 2022 01:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, RCVD_IN_DNSWL_BLOCKED=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 (1024-bit key) header.d=eggert.org
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 p_PUn1xUxuaD for <rsab@ietfa.amsl.com>; Mon, 30 May 2022 01:12:57 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 36CA3C14CF06 for <rsab@rfc-editor.org>; Mon, 30 May 2022 01:12:18 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:4c33:861a:9e68:f822]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 1686F1F01FB; Mon, 30 May 2022 11:06:13 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1653897973; bh=U4dBI4wNuGnvYmPA3iO9j1iBfwiFiDxJJmKw77C13Lw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=jLO6Cn9JKfyTYV0pdg4ZbeHgYMlKsJzrgLhL/Ur+j1UAReUjBZByK+hZzd/uzgYmj khTMiI7anGGDA/9KlcWhFlru0ivqa9WAft3nPMyesnx4gHZMxGCM0jxRW6/6B4JJ8D zXTF66Vi7X40GKFTV3Y5LbYFVnw3tfdofIj5OLJg=
Content-Type: multipart/signed; boundary="Apple-Mail=_91350AD7-1890-437E-B72E-78FB9115D24A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <4E87EC9E-3066-437E-8886-587EF914FC79@amsl.com>
Date: Mon, 30 May 2022 11:06:12 +0300
Cc: Jay Daley <exec-director@ietf.org>, RSAB@rfc-editor.org
Message-Id: <84FAEFD8-B221-4F53-B0FA-9A5FCBB859D7@eggert.org>
References: <F73C7749-8CEC-4860-9500-0CEFF3E933D5@ietf.org> <4E87EC9E-3066-437E-8886-587EF914FC79@amsl.com>
To: Cindy Morgan <cmorgan@amsl.com>
X-MailScanner-ID: 1686F1F01FB.AC97B
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/QcUEnY9weqQU5q1xHMvIe8400i4>
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: Mon, 30 May 2022 08:13:01 -0000

Hi,

On 2022-5-26, at 23:32, Cindy Morgan <cmorgan@amsl.com> wrote:
> 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.

I don't quite read it that way. I think we can definitely announce in stages as things get set up, and then we *also* announce *again* to the RSWG mailing list more than a week before the 114 meeting, per the above paragraph. In other words, I think the text you quote sets a minimum bar for what/when we need to announce, but we can announce other things and at other times.

Thanks,
Lars