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

Wes Hardaker <hardaker@isi.edu> Mon, 10 January 2022 16:46 UTC

Return-Path: <hardaker@isi.edu>
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 0870E3A157D for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 08:46:59 -0800 (PST)
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=isi.edu
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 IwGAb1vJw-SP for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 08:46:54 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (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 178673A15A3 for <rfced-future@iab.org>; Mon, 10 Jan 2022 08:46:53 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id i37so3617661vkr.8 for <rfced-future@iab.org>; Mon, 10 Jan 2022 08:46:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isi.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L8K4Mxq4dNe/tOmVFvDB9oyJjR3VEReEh/ERb5Znees=; b=GSAGEnra0RGxM4tVI0wkKlpcbnOD26E+kHWjclAl7Hs20kN2U/Yc/uUn5DF8oBYyzB IP7QLyD3e1FB63NdgZascOILdS5ii8ecPnd+9EUBf0WRNEKadyGUSSTW6gVa+GRVlKPn 6HgdpLIKChuFAyvsUQAeY5vboTLsRSvY2DOtRiOTQB2kKvb+124TIAg+ciC4fAubtw9R Vdrspt+i+ZIqVOusS2SHbG7bognm4QDWEaLVbkWf4ZOBDGYVkRiuXBNAhcDLn/X3vLkF jo4Kxb8m+XoYC9SohsS1iUVxVqqjLM0vP3m2lzPS4sFvi8bQRSKgZVbBqRIGixzWw01O zhPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L8K4Mxq4dNe/tOmVFvDB9oyJjR3VEReEh/ERb5Znees=; b=WfvRQwT0Ux0bKKx1KJntKNL57wsIuDAhcFLdn2lDvG6VPUYMHxhTjFAfpW/QIWs2M1 7VelTr1ip1OL+gXY6Et7eOU2nJD9p0irRYa6u8G1T3ch4pzdBpalNiX5oadIkQorNAva jLrjQK/NEYjkRkFx/xlVSrD4cfgnta76LTweolYeYd1Hb4hzFP99+gNMv+ZLWzc9XaYu /UVxh3BBZNeqfHDMT0QFpGDgjYXs7qb+L6jq09O+yJwWQtn+tAEkMuw+MqgYfXGQQ5nV LENV+NoQlqO7GBT6JBrWSbABPj6b/wJnevS14B2tGlL7AgNZlLcdN46WWH1Iwz4X//GM 2wsg==
X-Gm-Message-State: AOAM530BDGLBtp9tUiZBLRyjvi0y8kf3d6ESNJyKwuUzhznKv77Nv4Fp BRgLI+URn8f1vHNA90cmcwaoVfDr/9v/0swk8n1ZhQ==
X-Google-Smtp-Source: ABdhPJz6x2J39z3GoiK91lPgtdWljyQSjcRXtWG6vdyewUbA6i/prMFMGOgXqMhbRZ4PBFsKt8lE5+zgFmvgPM3+lTY=
X-Received: by 2002:a05:6122:d10:: with SMTP id az16mr131664vkb.8.1641833211453; Mon, 10 Jan 2022 08:46:51 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <548366C9-4581-4D4F-8638-7A5F7B754D13@eggert.org>
From: Wes Hardaker <hardaker@isi.edu>
Date: Mon, 10 Jan 2022 08:46:40 -0800
Message-ID: <CANk3-NA1+-46Q0QkV_cr7SNB_nKU3+vEqqK7dMtwmf12Efyaog@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Mirja Kühlewind <ietf@kuehlewind.net>, rfced-future@iab.org, Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary="00000000000059759205d53d153a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/bvxP7sJxjBch8FFkwY9zhuRxlLk>
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 16:46:59 -0000

Top posting because... phone...

One major reason for needing public archives is to document discussions for
referring future questions and people back to discussions where topics have
already been discussed. We do this in ietf working groups all the time.

-- 
Wes Hardaker
USC/ISI

On Sun, Jan 9, 2022, 23:20 Lars Eggert <lars@eggert.org> wrote:

> 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)
>
>