IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Mon, 10 January 2022 07:31 UTC

Return-Path: <lars@eggert.org>
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 23D4D3A0B9B for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 23:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=eggert.org
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 QJMJOloqvFDV for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 23:31:34 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 547E23A0BB3 for <rfced-future@iab.org>; Sun, 9 Jan 2022 23:31:34 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:3861:f1d9:3418:9369]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 623571D255A; Mon, 10 Jan 2022 09:31:22 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1641799882; bh=fMGMXUyuA6nduxkbdr4/6I6Bjqboy6awuQikCXQc/4A=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=tfTXmtmfl+a5+w8JKTL3jMpl+6cbFFC4tO/37jj4FszIQrZX/tSQV/nJttpUVa+N/ evEZ5W7EWLJRKrLHeCUUzDL4kI/ZmhNhSwIZrsuA+YNKBtA/UA2AuHRlzN8JXUUu9u Io5oikP4+VgfBfVYGjThOTu3gTCsi4jr9IHdyCgE=
Content-Type: multipart/signed; boundary="Apple-Mail=_9B70B63F-FE76-4835-8CB1-230111B44D34"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <73eeadd1-9cff-2df8-fe2b-664580acdfad@stpeter.im>
Date: Mon, 10 Jan 2022 09:31:21 +0200
Cc: John C Klensin <john-ietf@jck.com>, "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, rfced-future@iab.org
Message-Id: <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>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-MailScanner-ID: 623571D255A.A2CD3
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/L6awVCsVVS4Rur0al1neX5ERSY0>
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 07:31:39 -0000

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

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?

Thanks,
Lars

v2.23.0 | Report a Bug | By Email