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

Lars Eggert <lars@eggert.org> Fri, 07 January 2022 14:50 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 1B6CA3A07A6 for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 06:50:38 -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 6YmFUIarnM8f for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 06:50:33 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 1D8CD3A077E for <rfced-future@iab.org>; Fri, 7 Jan 2022 06:50:32 -0800 (PST)
Received: from smtpclient.apple (mobile-access-2e8466-21.dhcp.inet.fi [46.132.102.21]) (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 651D61D255A; Fri, 7 Jan 2022 16:50:17 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1641567017; bh=cnXVMpAoIWIzEmZAI0LKC3Nb6SSBXn3QSBy8r7A0zLM=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=VmHmu2E+LpU65Tu+85/qidbjnEbY5QdgrWdNnKiHM6zc7/kwTfcuTCe/jZNdEYvsX uWTWIBJhAwmcql13b/uuRSoQaopWk6AocAM2Qz2BHkpsuxpSe8kYQfYUPzpcx8mJII Yk2wCoD/RE7AmBgQSLvhD0XspciN9hz1o8/J8ODw=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Lars Eggert <lars@eggert.org>
Mime-Version: 1.0 (1.0)
Date: Fri, 07 Jan 2022 16:50:15 +0200
Message-Id: <20E548FE-22A3-4B25-AB8C-AEC6AB9C689B@eggert.org>
References: <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org, Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-MailScanner-ID: 651D61D255A.A3DAF
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qz-SiXtgM1tFsNoy_jE2aUFboZM>
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: Fri, 07 Jan 2022 14:50:38 -0000

+1 to Mirja

-- 
Sent from a mobile device; please excuse typos.

> On Jan 7, 2022, at 13:38, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> 
> I don’t have a strong opinion but I want to note that is not what we do for the IESG and IAB. While there is not necessarily  anything secret on those lists, I always thought is makes the work easier because you can just freely send things without e.g. worrying too much about the exact wording. As noted by Brian and in the text below, there are always things that are confidential and need to be send to a list without public archive. Given such a list always has to exist, my guess it that people would just end up using that list more because it just easier than lengthly considering what to send where.
> 
> So why do we think that the mail archive for the RSAB needs to be open in additional to e.g. minutes which should cover all the important points?
> 
> 
> 
> 
>> On 7. Jan 2022, at 01:51, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 
>> wfm
>> 
>> Regards
>>  Brian
>> 
>>> On 07-Jan-22 12:45, Peter Saint-Andre wrote:
>>> On 1/6/22 12:58 PM, Brian E Carpenter wrote:
>>>> On 06-Jan-22 14:37, Peter Saint-Andre wrote:
>>>>> The draft says:
>>>>> 
>>>>>     The RSAB shall keep a public record of its proceedings, including
>>>>>     minutes of all meetings and a record of all 
>> decisions.
>>>>> 
>>>>> Brian Carpenter noted: "As far as I can see, we don't specify whether
>>>>> the RSAB's mailing list does, or doesn't, have a public archive."
>>>>> 
>>>>> Do folks have opinions on this point?
>>>>> 
>>>>> (Without my editor hat on, I think it's preferable to make the list
>>>>> archives public, in the interest of transparency.)
>>>> 
>>>> So, ignoring the copy-by-value vs copy-by-reference detail, my
>>>> opinion is that RSAB email should be in a public archive *except*
>>>> for anything that amounts to an "executive session" discussion.
>>> Proposed text:
>>> ###
>>> The RSAB is expected to operate via an email discussion list,
>>> in-person meetings, teleconferencing systems, and any additional
>>> tooling it deems necessary.
>>> The RSAB shall keep a public record of its proceedings, including
>>> minutes of all meetings and a record of all decisions. Email messages
>>> sent to the RSAB email discussion list or exchanged among all members
>>> of the RSAB shall be publicly archived, with the exception of topics
>>> that require confidentiality (e.g., personnel matters). Similarly,
>>> meeting minutes may exclude detailed information about topics
>>> discussed under executive session, but should note that such topics
>>> were discussed.
>>> ###
>>> Peter
>> 
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future