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

Mirja Kuehlewind <ietf@kuehlewind.net> Fri, 07 January 2022 11:38 UTC

Return-Path: <ietf@kuehlewind.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 285D53A19A4 for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 03:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 pwxx_2aVjNE6 for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 03:38:22 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5FC33A19A3 for <rfced-future@iab.org>; Fri, 7 Jan 2022 03:38:21 -0800 (PST)
Received: from p200300dee733e70034e89fbd8d38e960.dip0.t-ipconnect.de ([2003:de:e733:e700:34e8:9fbd:8d38:e960]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1n5nZX-00042U-8p; Fri, 07 Jan 2022 12:38:15 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <95dd0e5a-c5f4-09d1-98b4-327978e21316@gmail.com>
Date: Fri, 07 Jan 2022 12:38:13 +0100
Cc: Peter Saint-Andre <stpeter@stpeter.im>, "rfced-future@iab.org" <rfced-future@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net>
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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1641555501;2ee8e49a;
X-HE-SMSGID: 1n5nZX-00042U-8p
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/R4Dn1tr9FZQ-VaExKdAJ4WBDDkc>
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 11:38:26 -0000

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