[rsab] Preparing for RSAB's first document

Alexis Rossi <rsce@rfc-editor.org> Wed, 13 March 2024 01:02 UTC

Return-Path: <rsce@rfc-editor.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 E8C57C14F68A for <rsab@ietfa.amsl.com>; Tue, 12 Mar 2024 18:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 GEqYfODp_bSF for <rsab@ietfa.amsl.com>; Tue, 12 Mar 2024 18:02:49 -0700 (PDT)
Received: from smtpclient.apple (157-131-78-231.fiber.dynamic.sonic.net [157.131.78.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 49049C14F5E0 for <RSAB@rfc-editor.org>; Tue, 12 Mar 2024 18:02:49 -0700 (PDT)
From: Alexis Rossi <rsce@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <B1DDFB7F-C774-481C-A4B7-52C4E620AEFC@rfc-editor.org>
Date: Tue, 12 Mar 2024 18:02:38 -0700
To: RSAB@rfc-editor.org
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/f4okR8SPaUwtPfof9WWrdUvBXkg>
Subject: [rsab] Preparing for RSAB's first document
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.39
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: Wed, 13 Mar 2024 01:02:54 -0000

In anticipation of getting our first document from RSWG [1], it seems like we should start contemplating how the RSAB portion of the process will play out.



** Notice & Comments - where do they live long term? **

RFC 9280 defines some things about how notices and comments should be presented/archived:

- "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." (Section  3.1.2.6)
- "Notices are also to be made available and archived on the RFC Editor website.” (Section  3.2.3)
- "Comments will be publicly archived on the RFC Editor website."  (Section  3.2.3)

Since this was written, it seems like a lot of functionality moved to Datatracker, so the requirement that things be on rfc-editor.org may now be out of date (obviously we’re already not doing the first one for agendas). The spirit here seems to be “all records are publicly available where the community can easily find them.” I’m hoping the solution is to have a page about RSAB on rfc-editor.org that points to Datatracker, or something or similar (rather than needing to update 9280 to be correct/less specific about implementation details). 

As a specific answer to “where” notice and comments live long term, I think they live in the mail archive?



** Notice & Comments - which lists? **

Question #1 - does this document have "the potential to significantly modify long-standing policies or historical characteristics of the RFC Series” (section 3.2.3), thus requiring “extra care”? If so, what “extra care” is required?

Question #2 - To which email lists (or other places) should we provide notice? Rfc-interest is specified in 9280, as well as saying "RSAB members should also send a notice to the communities they directly represent (e.g., the IETF and IRTF)” (section 3.2.3). Are there other lists we should post notice to?

Question #3 - Should we require that Comments only be sent to one particular list for the sake of record keeping? Should that be rsab@rfc-editor.org?



** Balloting **

Jean pointed out that balloting should be implemented on Datatracker (per https://github.com/ietf-tools/datatracker/issues/4332). Having never used the balloting system before, I guess I’m assuming that this will work as desired (I don’t know where it is or how to test it). Do we need to do any testing to make sure it functions as needed?

Alexis

[1] https://github.com/paulehoffman/draft-rswg-rfc7990-updates