From nobody Mon May 9 11:04:43 2022 Return-Path: X-Original-To: irtf-announce@ietfa.amsl.com Delivered-To: irtf-announce@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDEEC14F73A for ; Mon, 9 May 2022 11:04:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.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 t-8YXYIYcn-h for ; Mon, 9 May 2022 11:04:34 -0700 (PDT) Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4B3DC14F739 for ; Mon, 9 May 2022 11:04:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=FMZn37s+Ua/xr+6jGxt5TjgSAuMM6lqu0x15rXfHvjo=; b=2OzRrTWRgtvfZONvXTG4kE+mpV ffCJ/ru+WByS27KJAfJJjHfxe1XXV4uFbOkMpCSZa9EJr4WHnkZi7nIk2lpX6C9l4nQxfR2p1scJn xZLbbASEkMmnVX7OllWp1AvxRJjR7GgLdnss2Ws0abL29u6UW2oJljDURZwdc2XqaS17u9p0ZnMs+ qdem85uvk8HEDyJVsnoqRJ6VITY+wXAmC1Sf0dVS4rsC74ALYKaKx61+VKhzb7pinecdegrBLCWwa Pyk7VnPWyJnpPXwD9xdmc+yCj/cGD4aZNyflYnZ5SUkm8T1+jAF3qeIHdg1gH+8Wn3qoXisbE1GzT 4f1X5vIA==; Received: from [130.209.254.22] (port=65237 helo=vpn22.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1no7kC-0002JB-Cb for irtf-announce@irtf.org; Mon, 09 May 2022 19:04:32 +0100 From: Colin Perkins Content-Type: multipart/alternative; boundary="Apple-Mail=_C5ED1D3A-2726-414C-8552-6F42BE575CF4" Reply-To: The IRSG Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Date: Mon, 9 May 2022 19:04:25 +0100 References: To: irtf-announce@irtf.org Message-Id: <40B81018-BE98-4074-8E8A-FB80F424CE68@csperkins.org> X-Mailer: Apple Mail (2.3445.104.21) X-BlackCat-Spam-Score: 14 Archived-At: Subject: [IRTF-Announce] Public archival of AUTH48 communications for IRTF-stream RFCs X-BeenThere: irtf-announce@irtf.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: IRTF-Announce List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2022 18:04:39 -0000 --Apple-Mail=_C5ED1D3A-2726-414C-8552-6F42BE575CF4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 =E2=80=9CAUTH48=E2=80=9D = 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.=20 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: >=20 > From: IETF Chair > 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 >=20 > We=E2=80=99d like to thank the community for all the feedback on the = IESG=E2=80=99s proposal to create a public archive for AUTH48 = conversations = (https://mailarchive.ietf.org/arch/msg/admin-discuss/eFfx9ylrIafZc1R1hgsZH= MYD3Wg/). >=20 > 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. >=20 > 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. >=20 > We=E2=80=99d 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. >=20 > Francesca Palombini and Lars Eggert > on behalf of the IESG --Apple-Mail=_C5ED1D3A-2726-414C-8552-6F42BE575CF4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
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 =E2=80=9CAUTH48=E2=80=9D= 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=E2=80=99d like = to thank the community for all the feedback on the IESG=E2=80=99s = proposal to create a public archive for AUTH48 conversations (https://mailarchive.ietf.org/arch/msg/admin-discuss/eFfx9ylrIaf= Zc1R1hgsZHMYD3Wg/).

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=E2=80=99d = 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
= --Apple-Mail=_C5ED1D3A-2726-414C-8552-6F42BE575CF4--