Re: [Rfced-future] Issue 144

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 06 January 2022 00:38 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 406EC3A1044 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:38:00 -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 7hlXw74SWKZu for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:37:56 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 038543A1040 for <rfced-future@iab.org>; Wed, 5 Jan 2022 16:37:55 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id y16-20020a17090a6c9000b001b13ffaa625so6468130pjj.2 for <rfced-future@iab.org>; Wed, 05 Jan 2022 16:37:55 -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=Aft+5IfRAiQKFUdmL73W/AayShliVps3SGEP6CdRSek=; b=fa1XVMseO3kL9+F/c7JVwU0E1mT2CYM5WpjfmsEhAf+R/cDfQl+0QxrnYZnpRy++RH HDe2EscQ9QFtx040LbD0XhQKVb3vRB+UmBCM1HV+02LQ/9McCQn63POa+pGlamTOF3gG smB1ig1IR6XDWfg/b0mKwQuygGbsr3LWmRvvCasDf6b56AuRQWSfyNL3IMbx7Oa2o1YN +BaydCTL///R3GLIk4lk3AGK0jtfmXowUPmX3UHdlpQXWoaLqwgxow5l2yXjcsg6QOV6 Bgot1/9ZREWIbBlTtKsbAwCnkfpVU2uoADry2r1nAwKt4Z5u+d2meE2MyzxIacBHrwL6 xfoA==
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=Aft+5IfRAiQKFUdmL73W/AayShliVps3SGEP6CdRSek=; b=2ay1gFWz6XjxEoKLbfIYg+GIVCIo2tnb2IDhsuaVR5Em+48zY+W+pAubouRiDbjIYH ftMIpDGNr5QeeKipYTwRugrelPvIzZvK3eBij5dwxsNai9x1zHWpr0RShH+1BLJFBJaU T6Ze6a/vqDii63aLIhVo1IF6OogpKsapYpdsF1Kwk3PonKDY/dEGWhTrHUyqNz34qgQ6 6C8y3P/MJqowB97VSd4fuYZoyiHERh+FGKKuSo+92mqk0JW8lvDz8Zk3ZmNQNLxiAfCw 00Sy+c8KiTmiXsTT6Zn8AqQwmw57njcxAWAMxqKiB/gAemxTZ8ZM+5oo7DpwP0V152Xj Rq3A==
X-Gm-Message-State: AOAM532+yqsGBNkB8xHKinr9vQZSPjhyc9B7j9Y6WrzSaPHP4JNjASLO 7bm7vu0Mx+H5RKPczgVzj6rgZMX1pNxIeA==
X-Google-Smtp-Source: ABdhPJyGOt/i/sA6JXHjldgjfedDBT1MeXzHvI7l/OOyu4rLh0q1Sd5rRM4/gPwRb5rgYaVYvGSKTw==
X-Received: by 2002:a17:902:e0cc:b0:149:e2d4:ec51 with SMTP id e12-20020a170902e0cc00b00149e2d4ec51mr3417337pla.99.1641429474176; Wed, 05 Jan 2022 16:37:54 -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 l18sm3687932pjy.6.2022.01.05.16.37.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Jan 2022 16:37:53 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <abb0c140-2bed-312b-4f25-c36bee0c1f56@gmail.com>
Date: Thu, 06 Jan 2022 13:37:49 +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: <53497e97-ed65-93c8-5f4c-3f4ee9943501@stpeter.im>
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/97gg3hlc2vtJyq_VBvfe-xIGftc>
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:38:00 -0000

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.

    Brian
> 
> Peter
>