IETF Logo Mail Archive

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

Michael StJohns <msj@nthpermutation.com> Thu, 06 January 2022 17:20 UTC

Return-Path: <msj@nthpermutation.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 EBD143A1354 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 09:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_NONE=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=nthpermutation-com.20210112.gappssmtp.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 przhTXp_gw22 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 09:20:50 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 6A3823A1353 for <rfced-future@iab.org>; Thu, 6 Jan 2022 09:20:50 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id f138so3314490qke.10 for <rfced-future@iab.org>; Thu, 06 Jan 2022 09:20:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=3t6VCCCM+ImmH38DYNtuTTtnrdh3Qmbb2mT9F91mnKo=; b=liMP+hcI5eL7uGMMrWorV0TDnKeOpkpp3wfYhzZKE1F0Kg6cyarKm0A6fAGfoHobeA EmybpSXYiLJqLEdiiAdaDaxdjFZAdVOG1LJcTeY4XVQ8OAjGZ8HnDDkBTa6Zhs7FtNYu 5BwiruylwK1vEEQSi/t9lhp10FmKxUYkfXVhuvpk6ScFhon7k0rIfT1Pl/k4806n8yvJ 3MOz0x5cLEhsD8VdhqyguUKiV4Ex5477f4w0W/2Wnf6GX5vckVNbHtF9IxAhqyZd4RBT BR8urv9cX9ZRWl1ZuJTCK3ZjC9fC+Gs3Z2xlLsjTFMnGpDCbluwHPsy/cTPHz9x6+inm eAUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=3t6VCCCM+ImmH38DYNtuTTtnrdh3Qmbb2mT9F91mnKo=; b=2eeLdRfJfCQ7vL6COKZCAb3kWYVp3JsQZtOxCP15w0+bdl55F7f19MscuEquyyymiw 7tTnfHMJJwTjWgAcOec7QnlBMjcxpbWZE8H8OYe22HrqVteJFPY+4x4U3XHnvmu8+qfP JPcXDUgG2YubzQK7ZG2/DvnrCsEhs5fHEFeNj0IVfkDiEbKsn5/iRRvNXZAIJNEkrIDI Jn6BFLp7dx22/MdDeRMxdW0oTL6p2imyKa5qTuLrC8O6wIisnqnksVoml61pKOy/lLdk U8SCCdgzuP8YR3i/DduflEAi4qZJfBL12G2IxBgDiBcUci4HECiSSq5BqnRXvWC2Y+qz bq2w==
X-Gm-Message-State: AOAM53218fFDJO/ZKLDr6srJc9hRZqx77THsYOlt8+whZT4Pr42pg9DH 4MQkx8cs2u0/ExzP4T4RiDDdAhc/22+IgLpesLE=
X-Google-Smtp-Source: ABdhPJw9lvoYsBGjJyq+cEQ0M+ZuHXbAuqKQZ5t/UOkoebzPgMYSNYTRAoJ/iavFxD7z1uLVo9EUyQ==
X-Received: by 2002:a05:620a:1a27:: with SMTP id bk39mr39938500qkb.258.1641489647676; Thu, 06 Jan 2022 09:20:47 -0800 (PST)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id v12sm1858266qkl.50.2022.01.06.09.20.46 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Jan 2022 09:20:46 -0800 (PST)
Message-ID: <3c0ca0a0-ba13-9876-87f2-2cb954906d06@nthpermutation.com>
Date: Thu, 06 Jan 2022 12:20:44 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: rfced-future@iab.org
References: <3e1fe494-c86b-5181-6afb-128b05fec882@stpeter.im> <2B6CBEBC-0BA5-4F3A-A195-F1C42760BB04@akamai.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <2B6CBEBC-0BA5-4F3A-A195-F1C42760BB04@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/sdQGO3tVeVKRYg0KJHFOchMdFjM>
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: Thu, 06 Jan 2022 17:20:55 -0000

On 1/6/2022 9:22 AM, Salz, Rich wrote:
>
> On 1/5/22, 8:37 PM, "Peter Saint-Andre" <stpeter@stpeter.im> 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.
>
> Similar to what I just posted, can't we just say this group MUST follow standard IETF practices for transparency, notification, etc etc?
>
>
Because this (RSWG) group is not an IETF working group, and because we 
don't want to have to special case this stuff so that changes to IETF 
processes can't cause changes to RSWG processes in a manner that are 
unexpected.

The RSWG will be more like the Nomcom which has its own set of operating 
instructions, but adopts things by reference that are less likely to 
affect its remit (e.g. general IETF harassment guidance) than an IETF WG 
that must change its behavior if the IESG changes an applicable BCP or 
Informational document.   In the instant case, the record keeping, 
meeting schedule, etc are all going to need to be RSAB/RSWG specific.

So copy by value is fine (EKRs note and Peter's draft text), copy by 
reference could be problematic later.

Mike

v2.23.0 | Report a Bug | By Email