Re: [Rfced-future] Issue 144

Peter Saint-Andre <stpeter@stpeter.im> Thu, 06 January 2022 00:41 UTC

Return-Path: <stpeter@stpeter.im>
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 52A883A10B7 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:41:16 -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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=stpeter.im header.b=w1b9FBmu; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VVFdqtAg
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 G8Qr2Lv1r-vk for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:41:11 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80B323A10B6 for <rfced-future@iab.org>; Wed, 5 Jan 2022 16:41:11 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id B74CA3200D18; Wed, 5 Jan 2022 19:41:10 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 05 Jan 2022 19:41:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:to:references:from :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=+ AoxjOtPTdUd4/rmwRMNnjzghkoUqVZfHKPWI4P3ZJw=; b=w1b9FBmuReBJj1EsM /8aiCCxSralvlQIG/BKpusP+HtmJ7HccU005k73MqtsVTiO6pgooD/De1BQajNeX Ly2BFddkroq+4yuyFEJc5/vH0CEffQhV8SftsZhBlDiSnSa7lzkzzM0m10M0bKTZ yjxDa/PD9uj2Rsa9ZQmtFaStfDTAhKw6PUn7Ba/jzwjNSPXe0u0dW1mwOBzHDSv/ izA27pWZXWHht4f3JOR7N1zymQelz6Fxl5b1hMyk5h1pamXbC8Rlvv5MS0uxhKiP pbyMXT5VbmUO1zXsrVfbfTv5UInibwFoo2cUDJIzltQm4VLdsUwSPvbbksUolcFH KNVqg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=+AoxjOtPTdUd4/rmwRMNnjzghkoUqVZfHKPWI4P3Z Jw=; b=VVFdqtAgSpFm615yf1ORxBdloU1tCxPOR9950pJDg1puFH5IrOBrDp+XR BwFhvLjXCdgvH6XhNjdAukp9Fifybnm7Hqi6Yfe1shcZuowRXLbIKnZFVAeXkSL7 lEpGlxR21F5Cj1o4zoWtm/IDElhpeni+WD4dnLkUGq7B3co4rJgxjAwC7jBOYOfJ y3zOUJWzxFPAdj1VIlgqiGpL1XGtfv5MaFrlfSgl/DjI3345Jg0DveFhpNYFVPwC D34ePpX7HCzXYpGV/9D/ynIp1l0F6IbLpxoogL7YPGGjX3oYeXv9442OW7g2hftl PX/tzajQEL5NfNt2D0mP+dQ+Wdb8A==
X-ME-Sender: <xms:pjrWYYQCYQCIdMkgvORlaOvvq9PEqI79Exvs5N1lWRSrDCJ6NgJA3Q> <xme:pjrWYVzGNmNDJAR9ojjtgQTLQ5NnqAbF62B5FuhkWz7ZMnK9weGEhX-azDtK7Msn2 chriHF2bWxxQHW6MA>
X-ME-Received: <xmr:pjrWYV11uRCDyilW6M3cBqYRVJqOx5ARL1Hht2FsEQ0t380WiYeRe_4bIMZCCCdX9pNpGOSCfsW237e_-2UAd42mYJAXK_Iq17WhkE8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudefjedguddtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeejtdfhteetuefhkeehhfettedtgeffgfetgeehfeeiffeu keekudelgfduheegkeenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhivghtfhdroh hrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehs thhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:pjrWYcDyB9s8D7rI6d16wttZx8WVpq0tuqtCKmNX1IMMVBaee8rwnA> <xmx:pjrWYRigvuuzayvIH3KGE6DZLR31Ov5Zez4KWQpEYF5l7OdhzxZ-gQ> <xmx:pjrWYYpWBovk9BmQbjuB9nzzFmIlNHFH1KbniwR-X3skGT-Tib9eCg> <xmx:pjrWYUuYRJE49UihOHWc7tXTAjcgTfBiJscl3niSdbiy_T01EvzsWQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Jan 2022 19:41:09 -0500 (EST)
Message-ID: <db4d809d-a64e-4350-ecb4-5e85dca8ba40@stpeter.im>
Date: Wed, 05 Jan 2022 17:41:05 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eric Rescorla <ekr@rtfm.com>, 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> <abb0c140-2bed-312b-4f25-c36bee0c1f56@gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <abb0c140-2bed-312b-4f25-c36bee0c1f56@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/LK3Q-v7Wlvvl_oz7UCmCWZiCY_k>
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: Thu, 06 Jan 2022 00:41:17 -0000

On 1/5/22 5:37 PM, Brian E Carpenter wrote:
> On 06-Jan-22 13:24, Peter Saint-Andre wrote:
>> On 1/3/22 5:39 PM, Peter Saint-Andre wrote:
>>> On 1/3/22 5:19 PM, Eric Rescorla wrote:
>>>> Hi folks,
>>>>
>>>> I have reviewed this document and feel that it is generally
>>>> in good shape. I have made a small editorial PR
>>>> (https://github.com/intarchboard/program-rfced-future/pull/148
>>>> <https://github.com/intarchboard/program-rfced-future/pull/148>)
>>>> and filed four issues. As I know some people don't like using
>>>> Github, I recap them here.
>>>>
>>>>
>>>> Issue 144: The current text seems to say that we would need
>>>> WG consensus for any other mode of operation than a mailing
>>>> list, including a meeting. I understand that people want
>>>> to require consensus to use Github and I'm not trying
>>>> to change that, but do we really need to require consensus
>>>> to have a meeting?
>>>> https://github.com/intarchboard/program-rfced-future/issues/144
>>>> <https://github.com/intarchboard/program-rfced-future/issues/144>
>>>
>>> I tend to think not.
>>
>> Here is suggested text:
>>
>> ###
>>
>> When the RSWG is formed, all discussions shall take place on an
>> open email discussion list, which shall be publicly archived. The
>> RSWG is also empowered to hold in-person or online meetings. The RSWG
>> may also decide by rough consensus to use additional tooling (e.g.,
>> GitHub as specified in RFC 8874), forms of communication,
>> and working methods (e.g., design teams) as long as they are
>> consistent with RFC 2418.
>>
>> ###
> 
> Works for me.
> 
>>
>> As Ekr and I discussed briefly in the GitHub issue, we might to say
>> something about advance notice for meetings, along the lines of
>> https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/ 
>>
>> (or perhaps should we just point there?). The most basic guidance 
>> might be:
>>
>> "The RSWG is also empowered to hold in-person or online meetings, which
>> shall be announced at least four weeks in advance for in-person meetings
>> and at least two weeks in advance for online meetings."
> 
> We already cite 2418 which requires advance notice of meetings, so this 
> may not be necessary. No objection, however.

RFC 2418 says:

    Interim meetings are subject to the
    same rules for advance notification, reporting, open participation,
    and process, which apply to other working group meetings.

However, I don't see exactly where it talks about advance notification 
for "other working group meetings". I must be missing something obvious.

Peter