From nobody Mon May 9 09:48:33 2022 Return-Path: X-Original-To: ietf-announce@ietfa.amsl.com Delivered-To: ietf-announce@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FECFC14F744 for ; Mon, 9 May 2022 09:48:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 A5YSDSajd3Ks for ; Mon, 9 May 2022 09:48:31 -0700 (PDT) Received: from smtpclient.apple (mail.eggert.org [91.190.195.94]) (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 92EFCC14F742 for ; Mon, 9 May 2022 09:48:31 -0700 (PDT) From: IETF Chair Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Reply-To: The IESG Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Public archival of AUTH48 communications for IETF-stream RFCs Message-Id: Date: Mon, 9 May 2022 19:48:28 +0300 To: ietf-announce@ietf.org X-Mailer: Apple Mail (2.3696.80.82.1.1) Archived-At: X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "IETF announcement list. No discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2022 16:48:32 -0000 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/). 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