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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 10 January 2022 19:41 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 AC0C33A0EF3 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.813
X-Spam-Level:
X-Spam-Status: No, score=-2.813 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gwi15pRitNxc for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:41:42 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 A2C803A0EF2 for <rfced-future@iab.org>; Mon, 10 Jan 2022 11:41:42 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id l8so11335425plt.6 for <rfced-future@iab.org>; Mon, 10 Jan 2022 11:41:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=GrZHgnrLbYu7DGd9Ph46GLx2qsWGxKGGZMQ5ZbHF+iQ=; b=ezEkQy65otYdAFfLf8nluZQYOlVTtoYjuE/pl3U+9OiQ5iuc8LNbdZcxw6do3dPufG I/Am83VGmvez4n2dAKR/AbJBHvPOXN5xIj4VoGJ3cPCRSEklcTFm/h3+YFj7oNykw4E7 pMOImJjsi/5pwUJWQHl4U3u/6WNqRrCiHrpDfdcxFl4KiTAdAUyIwSYVf9CmYOuf00G9 8d2BE/9xadfYMReMfwetqw2+iALKDKnd5W53O9mRZ4DG7LZV7ifGRs1EFfAIwCtLO9B6 RkQlouaoX1Jvgeo42O6s9WQPoImi8TTb3tiYOv72OHf4NOlVWp2kJ4aiIpKIJGrQHsdF lhGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GrZHgnrLbYu7DGd9Ph46GLx2qsWGxKGGZMQ5ZbHF+iQ=; b=b6LY1x+zqgPvl17QqLcFPkcppI0fM5bZMNcJUACnRKVMGh1IacVpvx91t4zmls0R83 6L/+OgdHjm4XVQbH90H810eiKClC8jH5vfZPR01buKgoi+jrVG3svwG7EkHRMLM+pjBj hs4XOr99Yq3XK044vvKaML1MX1xeObownidpK6x8vb+P1CjvWyFywLHr0X3s3/2KtwDI E7RBuNL/Dlnbxz1Fzn01rM3vynxzTZxsErQF4klw83m5UZlGn1bvqkjJu2F8vDT+aUc/ rK2cRrv+EIzcQa77VfqZZHzZYExjTKPZXRfuGtdcgA73MIvmyLMp45UTkzFXI4VscDF1 A2eA==
X-Gm-Message-State: AOAM53054tXAZdoVzhketTiCYV4QPBypWih9G4Oi4mCT6UXImA10Uwsz cLV+cVSvdWPxxQ6JPqxwnE7wW4j4qRYeBQ==
X-Google-Smtp-Source: ABdhPJwiakZf0HbQZrcprtqdBqlI6fpKEi5GA1TO5WkYEdIOspgyS+VNgtK7x4z6XvLNKYxPMf8R6Q==
X-Received: by 2002:a17:90b:1bc9:: with SMTP id oa9mr32037423pjb.241.1641843700805; Mon, 10 Jan 2022 11:41:40 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:80b2:5c79:2266:e431? ([2406:e003:1071:1701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id ls6sm10418590pjb.33.2022.01.10.11.41.39 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Jan 2022 11:41:40 -0800 (PST)
To: rfced-future@iab.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> <34626d6f-9503-4be6-ac6c-08e14c71d4dd@beta.fastmail.com> <5A4271DD-8F92-443C-8AD2-B869CA33109A@akamai.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f7f8b03f-3735-c58f-d77d-04f7633f0bf5@gmail.com>
Date: Tue, 11 Jan 2022 08:41:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <5A4271DD-8F92-443C-8AD2-B869CA33109A@akamai.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/LZRNuVRz0xOGXgakBTYgMgctroA>
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 19:41:44 -0000

On 11-Jan-22 03:23, Salz, Rich wrote:
> Lars:
>      > This may be an acceptable tradeoff for this particular list, but it's
>      > also setting a precedent in the IETF, which makes me nervous.

I understand Lars' hesitation, but I dispute that this sets a precedent
in the IETF. This is not an IETF discussion. The RSAB is not comparable
to either the IAB or the IESG and the arguments are totally different.
I'd be happy to discuss any questions about IETF lists over on an IETF
list.
  
> I think it's a good -- nay, excellent -- precedent to set. There are well-understood mechanisms to be used when conversations need to be private; executive session, off-the-record, "off-list" emails, etc. etc.

As I've already pointed out, the RSAB *will* use such mechanisms when they
need to, whatever we do or don't write in the present document.

> Martin:
>>     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.
> 
> Completely agree.

Neither will the RSAB need to discuss legal, contractual or financial
details. Its remit is really quite narrow, and as Wes said, referring
back to earlier discussions may be very useful.

To be complete, there's one issue where privacy would matter:
Issue 151: Consultation / Approval for RSCE Selection committee.
That would be a case where off-list discussion would be needed.

Regards
    Brian