Re: [Rfced-future] Issue 143: RSAB mailing list archives

Martin Thomson <mt@lowentropy.net> Mon, 10 January 2022 08:46 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 094003A0773 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 00:46:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=OSWvUlOo; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WGKTLnG2
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZ6Hvf5rg0A2 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 00:46:07 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 641DB3A0763 for <rfced-future@iab.org>; Mon, 10 Jan 2022 00:46:06 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 05FC95C00C4 for <rfced-future@iab.org>; Mon, 10 Jan 2022 03:46:06 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Mon, 10 Jan 2022 03:46:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=N2cpBbG2XIJez8f7jeAchnZ+sC1Ws6I l9sSqJazdBP4=; b=OSWvUlOoJaYXciShPnqVklIGm4Qd5ihw1AoayWkPoNyuIKT kiFVZOZ9YmiYeKTt/PqebJrSqjasB2ZwzMfL79FEIqBa9v8usbPTPJ5UAFIKESRR biRyjIhRh7oLUOveiIVQfzFX4i5SCe9G0ikayNp68gu7CVpmGhE/s1y948mJRbPD TG2vGWN8qgubY6/kOGMbXxT1WpVWoY24zzhpj/PcLmjx2e5gURBQT1slDTCKmoFS 6IXmhPWAWfipxJMp8GK2wh+Fo+ig/QNrNGK3Q1X9gL+XhPTw9Dbo7uvLECPPn+CO V65QmbmRrCTlc0tVx5eHWKaI/Yc81Ts6t5lyBjQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=N2cpBb G2XIJez8f7jeAchnZ+sC1Ws6Il9sSqJazdBP4=; b=WGKTLnG2k+y9jN2FzKjuDh Ue31944wD/V3G2p8pHwwtp3T5VpdZtjHE6fVj9mc6eYHOPxE3M2bbxnzGR7O3N8O llHJ27Pw6L7XtMB5qwfvrDbc5jwA3EHjQ9s3P/MunjxrPEmv9wC90p4Gg1aLOXbi 5nbzJz7EpRQBfUQzroze0XctQFBYGPgB2t7IERoFKed7VztC2aDoUahjdr1x0YBb c41LjeVreUTStnB1kkjzRVRq2XHmdLBdBqEnRvcTycJZxODLu7vjZhFKo6hRc/Kv jS0/F4/2sW/8DWxDjVeVqHvWNlgG0UQ/E6Myh3C7JN8PU6cKo5647kSPm6J2Z7OA ==
X-ME-Sender: <xms:TfLbYUfFSCnxGNTlLSPYtHi6ycvL5IexY43xlPWMCdy79BUZuwLBGw> <xme:TfLbYWPlo6yDjvQh9n1TfxeQDtk43aEh0mOlgIumFnbOB56huXAC5LDMpIRFZ4HxJ 1M9M9HidxGjXtQ_Y8o>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegledguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfe ekvefhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:TfLbYVj1gwpKh20dQRh0f0pnIpICs-nukw884v7btrPAIxQxfG0DCQ> <xmx:TfLbYZ_yn8rHWOnidgcO81TUgPvYWCWdhgkx4zn-0-TnfMJBnjIfKg> <xmx:TfLbYQvs7MIUeVj9pBJhRM5fUSkK5OozdguKWSW2vnBugG99qgHwsw> <xmx:TvLbYe7xe62RComflgBCNfrjTOTIerBAnIJ80PRN977e3kls_V04lQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A772D3C0146; Mon, 10 Jan 2022 03:46:05 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4527-g032417b6d6-fm-20220109.002-g032417b6
Mime-Version: 1.0
Message-Id: <34626d6f-9503-4be6-ac6c-08e14c71d4dd@beta.fastmail.com>
In-Reply-To: <548366C9-4581-4D4F-8638-7A5F7B754D13@eggert.org>
References: <3e1fe494-c86b-5181-6afb-128b05fec882@stpeter.im> <48043fa8-eb37-2f97-942c-500492664bb0@gmail.com> <e708572f-b678-f60c-ab84-c48e039926a7@stpeter.im> <95dd0e5a-c5f4-09d1-98b4-327978e21316@gmail.com> <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net> <CANk3-NCkDCqz2m5X0aLGXKYttZ3U8LK-YppsyHYK6TT0RDYgHw@mail.gmail.com> <8a648870-03ec-b4c2-426b-357022e94c05@cs.tcd.ie> <548366C9-4581-4D4F-8638-7A5F7B754D13@eggert.org>
Date: Mon, 10 Jan 2022 19:45:45 +1100
From: Martin Thomson <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qFtmYFcixyX66ERqoVTExQwsbUg>
Subject: Re: [Rfced-future] Issue 143: RSAB mailing list archives
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 08:46:12 -0000

On Mon, Jan 10, 2022, at 18:20, Lars Eggert wrote:
> But as Mirja has outlined, a public archive does put somewhat of a 
> burden on the operation of the RSAB, because one will have to much more 
> carefully word each message to the list.
>
> This may be an acceptable tradeoff for this particular list, but it's 
> also setting a precedent in the IETF, which makes me nervous.

My opinion only: this is not a group that deals with personnel issues in its normal course of business.  There are few other reasons to conduct private business.  Public archives seem totally fine here.