Re: [Rfced-future] Issue 144

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 07 January 2022 00:54 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 5B1443A0C34 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, URIBL_BLOCKED=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 n7yOU07PN6d6 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:54:16 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 C51C53A0C29 for <rfced-future@iab.org>; Thu, 6 Jan 2022 16:54:16 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id n16so3695385plc.2 for <rfced-future@iab.org>; Thu, 06 Jan 2022 16:54:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=rCuUepCQjurAYqY2AntHx/yTznY6ID58pTw6InbfPzQ=; b=NxSdp0HPcvreOhpVAsTeVsCSRh5NGXLRtWYEmFinwh2ZWZb835oVRlDEXw/7zPjkbg ewtuRN/J7g+UKZkeM1PgYDGFqJ11pP4+nK7hCNSSBahctydd6qfuU2i7jo/vPG4+3b4p fAB6Y4U7itgMyngtVr6VeDDIBH3LWKp6tlRbSChkxQaXigA4tXtJmgTsjrTuM8mvV2Aj 6yTKFqh1uMnhcV8SpYv9H1VHwQv8UwyKiIXCC0mFLhA6Vbp6Oe/bZZtrJcstnXvuqGwQ xQIji7gQzhJT4zHBZUPhRl6fIvTrGWhRnNPgBaT+9CLeBiEH1bBMk9HhrfEih1EFWuNR fasA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rCuUepCQjurAYqY2AntHx/yTznY6ID58pTw6InbfPzQ=; b=Amc0diLupeb+KPUeJbUMZocs5SUPJS3VqbPBUp0QYr0HLH4pr3ae3KHZW01x3bA94W EEN64GMKz5yDzOge4M22H605SsN3TH0Sq8d84igbqYnUzhE92PKQJ04Gw/0Tk80SwZ4u JOAPE247tcjokQokU4zXLuGcPjT+YY3WewpkgsHn/v69IiMXLQQzMtOVTRYptNdep2Xy PJkBs01sV1kOkzDCrazqaHaACt/9miJKcxxW2G+1uHWnylv2QR+W0ut6fjqKVDiyolNW yI/UZpa/p8PxIDAtnGYCdfH8d8FvfSElVEMAuS9HaJfTaV+suY/n17jxpvti6im6tnFX Wj8g==
X-Gm-Message-State: AOAM533XXUnnjQ6O1MbQ1OhICYc5erfJ2IwjPn6dsFddTwOyF5n9wCLC HnyYt3P22Cuv9gO2u+wzzYIeNJVscv8R3w==
X-Google-Smtp-Source: ABdhPJwiiYh7QhRGRBzJAQrwQHY/oQ+TyHHUbHmDk8b8JDuPxfStAV9eF1ltDvqzuxdKi5rbKasvRg==
X-Received: by 2002:a17:90a:7a88:: with SMTP id q8mr7394108pjf.90.1641516854793; Thu, 06 Jan 2022 16:54:14 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:db7:d041:a2d:ce65? ([2406:e003:1071:1701:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id a16sm3748487pfv.160.2022.01.06.16.54.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Jan 2022 16:54:14 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <53497e97-ed65-93c8-5f4c-3f4ee9943501@stpeter.im> <FBE56AF3-8E2A-43D1-920B-F3F1EA6C6CD4@sobco.com> <8F21BC41-404A-4007-8436-AE2506C6A0A2@akamai.com> <CABcZeBNcuywBJfHAbL_5GYgLp6t+-pWWBbuCZKnQzqjp7BYxNg@mail.gmail.com> <DC6F136A-8FC4-4A6F-B42A-ED8BE3544999@akamai.com> <CABcZeBOGPsA7WmBcw_NwjLa60G1_8F0ZW4YzNNeyLy3rLNOhiw@mail.gmail.com> <D4D84AE9-17B2-4961-88B7-EE53FF4489E5@akamai.com> <0c4a8b22-9226-5539-9af4-f260e124b684@it.aoyama.ac.jp> <d2641ae0-36ea-90e4-fe20-cadae993d340@stpeter.im>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d61e7e3e-a84f-051b-f068-2ef3c74a3fd3@gmail.com>
Date: Fri, 07 Jan 2022 13:54:10 +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: <d2641ae0-36ea-90e4-fe20-cadae993d340@stpeter.im>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/vUTNRAIhvXOwleyS4VbBcHrm15E>
Subject: Re: [Rfced-future] Issue 144
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 00:54:21 -0000

Also wfm

Regards
    Brian

On 07-Jan-22 13:23, Peter Saint-Andre wrote:
> On 1/6/22 4:46 PM, Martin J. Dürst wrote:
>> On 2022-01-07 02:12, Salz, Rich wrote:
>>>> I suspect others may feel differently in that they don't want this to
>>>> be subject to changed IETF policies.
>>>
>>> I’d really like to hear from people who feel this as to what and why.
>>> I was just assuming this is like a WG in its behavior, and perhaps my
>>> assumption is completely wrong.
>>
>> I think in this case (advance notice), copy by reference is fine. In
>> others (RSAB mailing list, for example), copy by value may be better,
>> because as already said, the RSAB more like the Nomcom or so than an
>> average IETF WG.
> 
> If I'm reading the room correctly, we could say something like this:
> 
> ###
> 
> The RSWG is also empowered to hold in-person or online meetings,
> which should be announced with sufficient notice to enable broad
> participation; the [IESG Guidance on Face-to-Face and Virtual Interim
> Meetings](https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/)
> provides a reasonable baseline.
> 
> ###
> 
> Peter
>