IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Mon, 10 January 2022 07:20 UTC

Return-Path: <lars@eggert.org>
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 06BCC3A0B11 for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 23:20:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=eggert.org
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 O8rbf6J9MvaI for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 23:20:46 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B9693A0B0C for <rfced-future@iab.org>; Sun, 9 Jan 2022 23:20:46 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:3861:f1d9:3418:9369]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 345421D255A; Mon, 10 Jan 2022 09:20:16 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1641799216; bh=G/UJPiN+y+v/M/X+xnk1QMP82Ho1SJ4VhJckcmZjgig=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Ifn0gQE9TWWyP67D/tMJ/5jm+jIOqIZe6LhjEhaRUeDm8JwpxwnpthT6KAnawzA81 o6hN3SJvjr4fK2pAYyULi/W/My7oVpC7W1SaA0wLBXau+i5NNP3k+eToeJRb9yw8l/ GN6cV+qHdHENiT/QAw0nABB7Wmrsv6rjBPMOYQYI=
Content-Type: multipart/signed; boundary="Apple-Mail=_72C81001-7D53-49A3-9B05-97263193F7B0"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <8a648870-03ec-b4c2-426b-357022e94c05@cs.tcd.ie>
Date: Mon, 10 Jan 2022 09:20:14 +0200
Cc: Wes Hardaker <hardaker@isi.edu>, Mirja Kühlewind <ietf@kuehlewind.net>, "rfced-future@iab.org" <rfced-future@iab.org>, Peter Saint-Andre <stpeter@stpeter.im>
Message-Id: <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>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-MailScanner-ID: 345421D255A.A29C4
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/znPdx51jPMK9N_RGGTPgb1gq530>
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 07:20:51 -0000

Hi,

On 2022-1-8, at 16:19, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> +1, I'd support whatever "main" list is used by the RSAB
> being publicly archived. It's ok if they have one or more
> private lists too (same as IAB/IESG "confirmation" lists
> and similar) but making the main list archive public is a
> good improvement.

I'd like to come back to Mirja's question: why do we think we need a public mailing list archive in addition to all the things that are already public, such as minutes, etc., is needed?

I can understand that the pendulum is swinging towards maximum transparency now, given the closed nature of the RSOC.

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.

Thanks,
Lars (as an individual)

v2.23.0 | Report a Bug | By Email