Re: [Rfced-future] RSWG meetings and IETF meetings (Re: Issue 144)

Peter Saint-Andre <stpeter@stpeter.im> Fri, 07 January 2022 00:36 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 C8FFF3A0BA3 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:36:03 -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=B5v5x3gF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QaJSJr08
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 YuIyIL-A1Ar9 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:35:58 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 754DD3A0BA0 for <rfced-future@iab.org>; Thu, 6 Jan 2022 16:35:58 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D77935C00DF; Thu, 6 Jan 2022 19:35:57 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 06 Jan 2022 19:35:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:to:cc:references:from :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=N nClmVrUx6IXinr3J77U4aCoKqc8RUs1ThB6J7ydO18=; b=B5v5x3gF2FD6KAf63 LCfCmly4Jr+HNQ4Y+Zq9Bd5JvEK8d/mDan8xJy58UwQsSmP4+35aFiUoZL4BOVW9 gs6iIabiXUbzUKzPD/fpieGudf4qfhoTcNTu4o76mREO5vMviwY/0P4GmxLHh+SQ IwEeTBkyQgg5jV+LxRHTZb5/2u7ZPP/r/J2UJdQHhlH5fnyrdx9R9M3KXC2dBisv oQROcnv+jwvGRJNMVtC6UUjK/L+iSKEnb0X848rLnMpPyCYe48c8hSHGGxcpZFjz cUtC7J4HmOGoXzokkSikFxCpO1QNbVkJg7bN4GHcthpitgxaTKjunfwwusBlWI+L OIvLw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=NnClmVrUx6IXinr3J77U4aCoKqc8RUs1ThB6J7ydO 18=; b=QaJSJr08XnozZgaNtyU5xnvvSOnSklGxjMnCSWVM0nfY9L47eJSNjNRO+ SqP97SO4eqC+pB2tpBuMZGwUueYEAMUYmzbLs4+TuPuZkDFB7N/ACp7PPyMW2YQf 5F1bSqM0U3j2ecb2J9BczyoJ9izqLSbyQWoJ8f+Z+LDKVySu01OVmAh5cGXYKTeP I1Lskz/utRdDZN4za9s/9qUebhFiMKFnp6cXl6gTjIvnOXdx13HJrzxChC/Ubg9j LXrkq+iCjzMeVwOL7WkngdmeB/HsatSK1yQgQFP+QcCI81kfbX1O+CjFbYQ1kTRP jxpjO++I0xQfHfy4ydUibgMmuZWCQ==
X-ME-Sender: <xms:7YrXYSGKVOwYETHT4tGgbjHrEOO5GVBKrmf6NxMcjLYgurV65m129Q> <xme:7YrXYTWSetD7EQAK6CPrbaST-wouZ1KXPUk_0FFDmsWAGCGAvLbOUvomRnsyPpA28 UuJYBuc4wg9PcEPig>
X-ME-Received: <xmr:7YrXYcI2yJnk1aNrKJ2LoHk21XdDtwO80yqgFE-L28Wwwbg91MBByzuGvFOdCLLvyCbLteExmNHECPbUtiLnaRkbRG4f57P_tTSeSvU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegtddgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpefrvghtvghrucfurghinhhtqdetnhgurhgvuceoshhtphgv thgvrhesshhtphgvthgvrhdrihhmqeenucggtffrrghtthgvrhhnpeevueefjeduieeiie dtiedvfeefkeejvefgleeghfdvvddvffevgeffgedtudegteenucffohhmrghinhepihgv thhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:7YrXYcEILVf6Uk9iezd60Z4C73bL4ZdorqPcJvzm3iyzcwIbPOlH-A> <xmx:7YrXYYXkOUDqKT-QUiFhPrfRg0gTK4EwVSrhccwtMKGJcaWfQvDeog> <xmx:7YrXYfNmeN2nNUuQBUkRPHzvbhSFkUhpQzzPOUs58GFAP8iIEN2cRg> <xmx:7YrXYVgdaZsFlcYP14MEN0OtOpNZ7W2sNvNosHRGFuQsW08GOd03fg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Jan 2022 19:35:56 -0500 (EST)
Message-ID: <73eeadd1-9cff-2df8-fe2b-664580acdfad@stpeter.im>
Date: Thu, 06 Jan 2022 17:35:54 -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: John C Klensin <john-ietf@jck.com>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: 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> <55feea9d-d649-6e9d-7f71-74e19ecb194d@it.aoyama.ac.jp> <13563BFE328B6B07D99E4800@PSB>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <13563BFE328B6B07D99E4800@PSB>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/cRm03Iaixus4gAaJKtG6XYIoMWs>
Subject: Re: [Rfced-future] RSWG meetings and IETF meetings (Re: 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:36:04 -0000

On 1/5/22 8:43 PM, John C Klensin wrote:
> 
> 
> --On Thursday, January 6, 2022 11:53 +0900 "Martin J. Dürst"
> <duerst@it.aoyama.ac.jp> wrote:
> 
>> So far, this discussion seems to be going in the right
>> direction.
>>
>> However, I think it's unrealistic to imagine in-person RSWG
>> meetings independent of IETF meetings; the travel costs would
>> just not make sense. I think we should say so explicitly. That
>> would also raise the question of funding, but we could
>> probably assume that all the participants in the RSWG would
>> attend some other WG or RG anyway.
> 
> Martin,
> 
> Yes, but...
> 
> If we are going to go in this direction and spell that out, we
> also need to be clear that RSWG f2f meetings, with IETF or not,
> must have provision for effective offsite/online participation.
> In addition to all the usual reasons (with or without the
> pandemic), we want to be very sure that we don't exclude the
> non-IETF users/ customers for the RFC Series from the RSWG.
> While my expectations that many (or even a few) of them will
> actively participate are very low, doing anything that blocks
> their participation would be really bad news.

Something like this:

The RSWG is empowered to hold in-person or online-only 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. In-person meetings should include
provision for effective online participation for those unable to
to attend in person.