IETF 111 - Working Group/BOF/IRTF Scheduling

IETF Agenda <agenda@ietf.org> Mon, 26 April 2021 18:24 UTC

Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D233A2BC4 for <wgchairs@ietf.org>; Mon, 26 Apr 2021 11:24:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Agenda <agenda@ietf.org>
To: "Working Group Chairs" <wgchairs@ietf.org>
Subject: IETF 111 - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: agenda@ietf.org
Message-ID: <161946144094.31924.15329053750672900573@ietfa.amsl.com>
Date: Mon, 26 Apr 2021 11:24:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/X4wDyt7VtrpiaAlMFYUdpPhTpUw>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Apr 2021 18:24:01 -0000

-----------------------------------------------------------------
IETF 111 – Online
Meeting Dates: July 26-30, 2021
-----------------------------------------------------------------

We are now accepting scheduling requests for all Working Groups, BOFs, and Research Groups until Friday, June 11, 2021. 

===========================================================
What’s New for IETF 111

To accommodate the online meeting format, there will be two choices for session length: 60 minutes or 120 minutes. 

Requests for more than two hours of total meeting time are discouraged. In special cases, you may request more than two hours of meeting time, but the IESG will likely request a rationale, and scheduling pressure may still make it impossible to grant any additional meeting slots. Please see this recent email from the IESG [1] for more detailed guidance on how to structure your session requests. 

[1] https://mailarchive.ietf.org/arch/msg/wgchairs/_x2nc9Xqa5i1U4SuEFs3eggTCyk/

===========================================================
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 require an account on this tool, or assistance in using it, then please send a message to support@ietf.org.  If you are unable to use the tool, then you may send your request via email to support@ietf.org, with a copy to the appropriate Area Director(s).

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

The Special Request field will continue to be available for more specific needs, and Responsible AD conflicts are already taken into consideration. Please make sure you take a few minutes to check your conflict lists carefully!

===========================================================
How to Request a BOF


The BOF deadline is a little earlier than normal, on May 28. The intent of this earlier deadline is to allow BOF proponents time to work more closely with the IESG and IAB to develop their proposal before final approval determinations are made by June 18. Please see more details on the BOF wiki <https://trac.tools.ietf.org/bof/trac/wiki>.

Requests to schedule BOF sessions must be sent to support@ietf.org with a copy to the appropriate Area Director(s). Their contact information is listed at the bottom of this message.

When submitting a BOF session request by email, please include the BOF acronym in the Subject line.

BOFs will NOT be scheduled unless the Area Director approves the BOF. The proponents behind a BOF need to contact a relevant Area Director, preferably well in advance of the BOF approval deadline date. The AD needs to have the full name of the BOF, its acronym, suggested names of chairs, an agenda, full description of the BOF and the information below. Please refer to https://trac.tools.ietf.org/bof/trac/wiki for more information about planning a BOF.

You MUST provide the following information before a BOF session will be scheduled:

a. BOF full name with acronym in brackets: 
b. AREA under which the BOF appears:
c. CONFLICTS you wish to avoid, please be as specific as possible:
d. Special requests:
e. Number of sessions:
f. Length of session: 60 minutes or 120 minutes


===========================================================
Deadlines
Cut-off dates are subject to change.

• 2021-04-26 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool. If you are working on a BOF request, it is highly recommended to tell the IESG now by sending an email to iesg@ietf.org to get advance help with the request. 
• 2021-05-28 (Friday): Cut-off date for preliminary BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
• 2021-06-11 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool.
• 2021-06-18 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
• 2021-06-25 (Friday): Preliminary agenda published for comment.
• 2021-06-30 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
• 2021-07-02 (Friday): Final agenda to be published.
• 2021-07-14 (Wednesday): Draft Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool.
• 2021-07-19 (Monday): Revised Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool.


===========================================================


Submitting Session Agendas

Please submit the agendas for your sessions as early as possible using the "IETF Meeting Materials Management Tool," a Web-based tool for making your meeting agenda, minutes, and presentation slides available to the community before, during, and after an IETF meeting.  If you are a BOF chair, then you may use the tool to submit a revised agenda as well as other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/secr/proceedings/

Agendas submitted via the tool will be available to the public on the "IETF Meeting Materials" webpage as soon as they are submitted.

The URL for the "IETF 111 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/111/materials.html

If you are a Working Group chair, then you already have accounts on the "IETF Meeting Session Request Tool" and the "IETF Meeting Materials Management Tool."  The same User ID and password will work for both tools.  If you are a BOF chair who is not also a Working Group chair, then you will be given an account on the "IETF Meeting Materials Management Tool" when your BOF has been approved.  If you require assistance in using either tool, or wish to report a bug, then please send a message to support@ietf.org.

===============================================================
Area Director Contact Information

IETF Chair
Lars Eggert <lars@eggert.org>

 
Applications and Real-Time Area (art)
Murray Kucherawy <superuser@gmail.com>
Francesca Palombini <francesca.palombini@ericsson.com>

 
Internet Area (int)
Erik Kline <ek.ietf@gmail.com>
Éric Vyncke <evyncke@cisco.com>


Operations & Management Area (ops)
Warren Kumari <warren@kumari.net>
Robert Wilton <rwilton@cisco.com>


Routing Area (rtg)
John Scudder <jgs@juniper.net>
Alvaro Retana <aretana.ietf@gmail.com>
Martin Vigoureux <martin.vigoureux@nokia.com>


Security Area (sec) 
Roman Danyliw <rdd@cert.org>
Benjamin Kaduk <kaduk@mit.edu>

 
Transport Area (tsv)
Martin Duke <martin.h.duke@gmail.com>
Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>