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

John C Klensin <john-ietf@jck.com> Thu, 06 January 2022 03:44 UTC

Return-Path: <john-ietf@jck.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 AF2F23A1614 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 19:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kFSN032mLv07 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 19:44:00 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41A913A1613 for <rfced-future@iab.org>; Wed, 5 Jan 2022 19:43:58 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1n5Jgu-000CYb-4h; Wed, 05 Jan 2022 22:43:52 -0500
Date: Wed, 05 Jan 2022 22:43:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
cc: Scott Bradner <sob@sobco.com>, Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org, Eric Rescorla <ekr@rtfm.com>
Message-ID: <13563BFE328B6B07D99E4800@PSB>
In-Reply-To: <55feea9d-d649-6e9d-7f71-74e19ecb194d@it.aoyama.ac.jp>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/aK5Pp1iPB2sZDhYqLxtGOZOyDTQ>
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: Thu, 06 Jan 2022 03:44:05 -0000


--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.

best,
    john