[IRTF-Announce] Public archival of AUTH48 communications for IRTF-stream RFCs

Colin Perkins <csp@csperkins.org> Mon, 09 May 2022 18:04 UTC

From: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C5ED1D3A-2726-414C-8552-6F42BE575CF4"
Reply-To: The IRSG <irsg@irtf.org>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Mon, 09 May 2022 19:04:25 +0100
References: <C2AD7054-3CE8-43BF-AB5D-C6CBECD7BB7A@ietf.org>
To: irtf-announce@irtf.org
Message-Id: <40B81018-BE98-4074-8E8A-FB80F424CE68@csperkins.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-announce/80sh0WoZMED0l4Zmv9sR7TLvrrs>
Subject: [IRTF-Announce] Public archival of AUTH48 communications for IRTF-stream RFCs
Precedence: list

In respect to the policy announced below, the IRSG has also considered the issue of public archival of conversations between the RFC Editor, document authors, and the IRSG during the “AUTH48” period immediately prior to RFC publication.

These are communications during the final review stage in the RFC publication process, where the changes made by the RFC Editor are reviewed. It is also the last time changes can be made to a document before it is published as an RFC. 

The IRSG believes the increased transparency brought to the RFC publication process by publicly archiving these conversations is valuable. Accordingly, the IRTF stream will also follow the policy announced below.

Colin Perkins
IRTF Chair, for the IRSG




> Begin forwarded message:
> 
> From: IETF Chair <chair@ietf.org>
> Subject: Public archival of AUTH48 communications for IETF-stream RFCs
> Date: 9 May 2022 at 17:48:28 BST
> To: ietf-announce@ietf.org
> Reply-To: The IESG <iesg@ietf.org>
> 
> We’d like to thank the community for all the feedback on the IESG’s proposal to create a public archive for AUTH48 conversations (https://mailarchive.ietf.org/arch/msg/admin-discuss/eFfx9ylrIafZc1R1hgsZHMYD3Wg/)
> 
> After carefully reviewing the feedback and consulting with the Tools Team, the IESG has decided to go ahead with the proposal, i.e., to set up a single public mailing list whose only purpose is to archive AUTH48 conversations. The RFC Editor, when initiating the conversation with the authors during AUTH48, will CC this mailing list. All further responses should keep the mailing list in the CC, unless sharing of sensitive information necessitates an opt-out by the RFC Editor or the authors.
> 
> The IESG is instantiating this process for the IETF RFC stream only; the stream-approving bodies for other RFC streams may decide to follow suit.
> 
> We’d also like to emphasize that the purpose here is to further increase transparency of the IETF standardization process. The standardization and publication processes remain unchanged. Most importantly, that means that any conversation during AUTH48 remains between the RFC Editor and the authors, with the responsible AD in the loop. If community members wish to express opinions about document changes discussed during AUTH48 between the authors and the RFC Editor, they may raise them with the responsible AD.
> 
> Francesca Palombini and Lars Eggert
> on behalf of the IESG

[IRTF-Announce] Public archival of AUTH48 communi… Colin Perkins