Re: [Rfced-future] RSWG meetings and IETF meetings (Re: Issue 144)
John C Klensin <john-ietf@jck.com> Mon, 10 January 2022 13:59 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 A13C93A0CBD for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 05:59:26 -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 aBBGcQj8QBe4 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 05:59:22 -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 D15503A0CB7 for <rfced-future@iab.org>; Mon, 10 Jan 2022 05:59:21 -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 1n6vCY-000LtF-Ua; Mon, 10 Jan 2022 08:59:10 -0500
Date: Mon, 10 Jan 2022 08:59:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Lars Eggert <lars@eggert.org>, Peter Saint-Andre <stpeter@stpeter.im>
cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, rfced-future@iab.org
Message-ID: <59923C5AB2DB7352FB146561@PSB>
In-Reply-To: <262D7023-B90B-4F9C-B5E4-AACF8880E592@eggert.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> <73eeadd1-9cff-2df8-fe2b-664580acdfad@stpeter.im> <262D7023-B90B-4F9C-B5E4-AACF8880E592@eggert.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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/W_aT_fPf6L5QPWIiZ7gUIbjTzlA>
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: Mon, 10 Jan 2022 13:59:27 -0000
--On Monday, January 10, 2022 09:31 +0200 Lars Eggert <lars@eggert.org> wrote: > Hi, > > On 2022-1-7, at 2:35, Peter Saint-Andre <stpeter@stpeter.im> > wrote: >> 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/i >> nterim-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. > > with regards to meeting during the IETF week, that agenda is > under the overall control of the IESG. > > If the RSWG chairs would decide to request for an unreasonable > amount of meeting time or make other requests that are > difficult/costly/etc. to fulfill, is the IESG authorized to > decline those requests? Lars, Having read Martin's later note but finding this more convenient for a reply... As you certainly know, the other reason why the IESG controls the agenda is to mitigate nasty conflicts that would prevent key people from attending. That topic is not addressed in https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/ (cited in Peter's draft) because it is strictly about Interim Meetings. I assume that the IESG (or at least a relevant AD if they were in the same Area) would intervene if two WG Interims were scheduled for the same time slot. That statement does not say that, it might be worth the IESG taking another look. Wrt f2f meetings during the IETF week (not covered by that statement at all), while I think not treating this the same way an IAB open meeting or an IRTF meeting is treated would rapidly lead to such conflicts, my impression is that the IESG and the Secretariat gave up control of "side meetings" that do not use IETF-provided space (but are not on the agenda) some years ago. So we actually have four cases during the meeting week: (1) IETF WG meetings (covered by the referenced statement) (2) Other meetings that are subject to IESG approval that appear on the (main) agenda (not covered by the referenced statement but subject to IESG approval) (3) Other meetings that use IETF resources (obviously subject to Secretariat and/or LLC approval). Most of these show up on supplements to the agenda even though no formal procedure requires such supplements and I'm not sure all of them do. I don't know how much the IESG is consulted about the scheduling of such meetings, but hope you are at least aware of them and able to offer advice. Note that, for example, IAB breakfasts and assorted Area meetings probably fall into this category. There is also a fourth case: (4) Meetings that occur around the IETF week but outside its nominal time slots. In addition to assorted breakfast and lunch slots that would fall into (3) above, I'm thinking about evening or dinner meetings that do not draw on IETF resources and that occur after the last meeting time on the agenda and, more important, after the last slot on Friday. Because (3) may fall outside of IESG authority although within that of the LLC and (4) presumably falls outside the authority of either, Peter's rather simple draft text and reference to that statement are clearly (at least to me) insufficient for reasons beyond those you suggest. Probably an explicit comment should be made that the scheduling of such meetings should ("MUST" ?) be coordinated with the IESG and LLC. What I don't know is whether it is necessary to get into "approved". Doing so would significantly clutter the lines of authority so I hope that, if everyone knows about the meetings of everyone else, it is reasonable to assume that good sense would be sufficient to prevent conflicts of schedules and of other types. best, john .
- [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Peter Saint-Andre
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- [Rfced-future] Issue 147 [WGLC Review of the draf… Brian E Carpenter
- Re: [Rfced-future] Issue 147 [WGLC Review of the … Eric Rescorla
- [Rfced-future] Issue 145 Re: WGLC Review of the d… Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Michael StJohns
- Re: [Rfced-future] WGLC Review of the draft Brian E Carpenter
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Michael StJohns
- Re: [Rfced-future] WGLC Review of the draft Michael StJohns
- Re: [Rfced-future] WGLC Review of the draft Bob Hinden
- Re: [Rfced-future] WGLC Review of the draft Joel M. Halpern
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Brian E Carpenter
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Peter Saint-Andre
- Re: [Rfced-future] WGLC Review of the draft Carsten Bormann
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Martin Thomson
- Re: [Rfced-future] WGLC Review of the draft Colin Perkins
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] WGLC Review of the draft Colin Perkins
- Re: [Rfced-future] WGLC Review of the draft Eliot Lear
- Re: [Rfced-future] Issue 145 Re: WGLC Review of t… Eric Rescorla
- [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] Issue 144 Brian E Carpenter
- Re: [Rfced-future] Issue 144 Scott Bradner
- Re: [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] Issue 144 Scott Bradner
- Re: [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] Issue 144 Scott Bradner
- Re: [Rfced-future] Issue 144 Brian E Carpenter
- Re: [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] Issue 144 John C Klensin
- [Rfced-future] RSWG meetings and IETF meetings (R… Martin J. Dürst
- Re: [Rfced-future] RSWG meetings and IETF meeting… John C Klensin
- Re: [Rfced-future] RSWG meetings and IETF meeting… Martin J. Dürst
- Re: [Rfced-future] Issue 144 Salz, Rich
- Re: [Rfced-future] Issue 144 Eric Rescorla
- Re: [Rfced-future] Issue 144 Salz, Rich
- Re: [Rfced-future] Issue 144 Eric Rescorla
- Re: [Rfced-future] Issue 144 Salz, Rich
- Re: [Rfced-future] Issue 144 Brian E Carpenter
- Re: [Rfced-future] Issue 144 John C Klensin
- Re: [Rfced-future] Issue 144 Eliot Lear
- Re: [Rfced-future] Issue 144 Martin J. Dürst
- Re: [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] RSWG meetings and IETF meeting… Peter Saint-Andre
- Re: [Rfced-future] Issue 144 Brian E Carpenter
- Re: [Rfced-future] Issue 144 Peter Saint-Andre
- Re: [Rfced-future] Issue 145 Re: WGLC Review of t… Peter Saint-Andre
- Re: [Rfced-future] Issue 147 [WGLC Review of the … Peter Saint-Andre
- Re: [Rfced-future] WGLC Review of the draft Peter Saint-Andre
- Re: [Rfced-future] WGLC Review of the draft Peter Saint-Andre
- Re: [Rfced-future] WGLC Review of the draft Joel M. Halpern
- Re: [Rfced-future] WGLC Review of the draft Michael StJohns
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Joel M. Halpern
- Re: [Rfced-future] WGLC Review of the draft Eric Rescorla
- Re: [Rfced-future] WGLC Review of the draft Martin J. Dürst
- Re: [Rfced-future] WGLC Review of the draft Joel M. Halpern
- Re: [Rfced-future] RSWG meetings and IETF meeting… Lars Eggert
- Re: [Rfced-future] RSWG meetings and IETF meeting… Martin J. Dürst
- Re: [Rfced-future] RSWG meetings and IETF meeting… John C Klensin
- Re: [Rfced-future] RSWG meetings and IETF meeting… Brian E Carpenter
- Re: [Rfced-future] RSWG meetings and IETF meeting… Peter Saint-Andre
- Re: [Rfced-future] Issue 147 [WGLC Review of the … Jean Mahoney
- Re: [Rfced-future] Issue 147 [WGLC Review of the … Peter Saint-Andre