IETF Logo Mail Archive

RSWG at IETF 119

Russ Housley <housley@vigilsec.com> Mon, 18 December 2023 18:05 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC616C14F616 for <wgchairs@ietfa.amsl.com>; Mon, 18 Dec 2023 10:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JToNIBJTWGCr for <wgchairs@ietfa.amsl.com>; Mon, 18 Dec 2023 10:05:25 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83A0CC14F615 for <wgchairs@ietf.org>; Mon, 18 Dec 2023 10:05:25 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id E38A3151D31; Mon, 18 Dec 2023 13:05:24 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id D5C5C1514CD; Mon, 18 Dec 2023 13:05:24 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Subject: RSWG at IETF 119
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <170291799631.14021.12149647492302721036@ietfa.amsl.com>
Date: Mon, 18 Dec 2023 13:05:14 -0500
Cc: IETF WG Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <53829F69-9C40-4965-9C39-CAEC400A596E@vigilsec.com>
References: <170291799631.14021.12149647492302721036@ietfa.amsl.com>
To: Pete Resnick <resnick@episteme.net>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/cvOswZqYhMiWhSqhnm5rQBnHuvY>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2023 18:05:27 -0000

What do you suggest?


> On Dec 18, 2023, at 11:46 AM, IETF Agenda <agenda@ietf.org> wrote:
> 
> -----------------------------------------------------------------
> IETF 119 – Brisbane, Australia
> Meeting Dates: March 16 - 22, 2024
> -----------------------------------------------------------------
> 
> We are now accepting scheduling requests for all Working Groups and Research Groups until Friday, February 2, 2024.
> 
> ===========================================================
> How to Request a WG or RG Session
> 
> Requests to schedule Working Group or Research Group sessions should be submitted using the "IETF Meeting Session Request Tool." The URL for the tool is:
> 
> https://datatracker.ietf.org/secr/sreq/
> 
> If you need assistance using the tool, then please send a message to support@ietf.org.  
> 
> As a reminder, the conflict list options are:
> 
> - Chair Conflict: to indicate other WGs the Chairs also lead, or will be active participants in the upcoming meeting
> 
> - Technology Overlap: to indicate WGs with a related technology or a closely related charter
> 
> - Key Participant Conflict (e.g., presenter, Secretary, etc.): to indicate WGs with which key participation may overlap in the upcoming meeting. You do NOT need to add your Area Directors here; the datatracker will do this automatically.
> 
> The Special Request field will continue to be available for more specific needs. Please make sure you take a few minutes to check your conflict lists carefully!
> 
> ===========================================================
> Deadlines
> Cut-off dates are subject to change.
> 
> • 2023-12-18 (Monday): Working Group and BOF scheduling begins.
> • 2024-01-19 (Friday): Cut-off date for BOF proposal requests.
> • 2024-02-02 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. 
> • 2024-02-09 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
> • 2024-02-16 (Friday): Preliminary agenda published for comment.
> • 2024-02-21 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
> • 2024-02-23 (Friday): Final agenda to be published.
> • 2024-03-06 (Wednesday): Draft Working Group agendas due by UTC 23:59.
> • 2024-03-11 (Monday): Revised Working Group agendas due by UTC 23:59.
>

v2.23.0 | Report a Bug | By Email