Subject: [v6ops] Fwd: IETF 113 - Working Group/BOF/IRTF Scheduling

From: Fred Baker <[email-masked]>
Date: Fri, 24 Dec 2021 20:04:01 -0800

I am planning to schedule a single slot for v6ops at IETF 113; if we have enough work, we can add a second slot. It will be "hybrid", meaning that some of us will be in Vienna and some of us will be online. 

At this point, we have no updated working group drafts:

At this point, we have no working group drafts updated since the November meeting, and we have two updated individual submissions:

Individual Submission: Updated (since 2021-11-12) 
2021-12-23 draft-yu-v6ops-split6  (tracker) <https://datatracker.ietf.org/doc/draft-yu-v6ops-split6>  (HTML) <https://tools.ietf.org/html/draft-yu-v6ops-split6>  (thread) <https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-yu-v6ops-split6%22>  (diffs) <https://tools.ietf.org/rfcdiff?url2=draft-yu-v6ops-split6-02.txt>
2021-11-17 draft-hunek-v6ops-nat64-srv  (tracker) <https://datatracker.ietf.org/doc/draft-hunek-v6ops-nat64-srv>  (HTML) <https://tools.ietf.org/html/draft-hunek-v6ops-nat64-srv>  (thread <https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-hunek-v6ops-nat64-srv%22>)
So we're looking for new or updated drafts.

> Begin forwarded message:
> 
> From: IETF Agenda <[email-masked]>
> Subject: IETF 113 - Working Group/BOF/IRTF Scheduling
> Date: December 22, 2021 at 12:48:17 PM PST
> To: "Working Group Chairs" <[email-masked]>
> Reply-To: [email-masked]
> 
> -----------------------------------------------------------------
> IETF 113 – Vienna, Austria
> Meeting Dates: March 19-25, 2022
> -----------------------------------------------------------------
> 
> We are now accepting scheduling requests for all Working Groups and Research Groups until Friday, February 4, 2022 and BOF requests until Friday, January 21, 2022.
> 
> 
> ===========================================================
> What’s New for IETF 113
> 
> IETF 113 will be our first meeting with an in-person component since 2019 [1]. In order to accommodate the number of people who are expected to participate online, the IESG will aim to maintain a schedule that is similar to past fully-online meetings, i.e., with approximately six hours of session time on most days. Exact details of the daily schedule and the scheduling of other meeting related activities are still under development and will be announced as they are confirmed. 
> 
> The session request form will ask you to estimate the number of people attending. Please make your best guess, based on your last several online sessions, as to the total number of participants. When we assign conference rooms at the meeting, we will make room size estimates based on the proportion of in-person registrations.
> 
> Requests for more than two hours of total meeting time are unlikely to succeed. 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 email from the IESG [2] for more detailed guidance on how to structure your session requests. 
> 
> As of IETF 112, BOFs are now requested via the Datatracker instead of the wiki. Please see the BoF section of this email below for more details. 
> 
> [1] https://mailarchive.ietf.org/arch/msg/ietf-announce/eEgVx3PsP4u6JVoM21by9aj4b3M/
> [2] 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 [email-masked].  If you are unable to use the tool, then you may send your request via email to [email-masked], 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 January 21. 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. If your initial proposal needs further work you may submit revised BoF proposals until February 4. 
> 
> 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://datatracker.ietf.org/doc/bof-requests/new/ for more information about planning a BOF. You will need a Datatracker account to submit a BOF request.
> 
> 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-12-22 (Wednesday): Working Group and BOF scheduling begins.
> • 2022-01-21 (Friday): Cut-off date for BOF proposal requests.
> • 2022-02-04 (Friday): Cut-off date for revised BOF proposal requests to Area Directors at UTC 23:59.
> • 2022-02-04 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. 
> • 2022-02-11 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
> • 2022-02-18 (Friday): Preliminary agenda published for comment.
> • 2022-02-23 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
> • 2022-02-25 (Friday): Final agenda to be published.
> • 2022-03-09 (Wednesday): Draft Working Group agendas due by UTC 23:59.
> • 2022-03-14  (Monday): Revised Working Group agendas due by UTC 23:59.
> 
> 
> ===========================================================
> 
> 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 113 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/meeting/113/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 [email-masked].
> 
> ===============================================================
> Area Director Contact Information
> 
> IETF Chair
> Lars Eggert <[email-masked]>
> 
> 
> Applications and Real-Time Area (art)
> Murray Kucherawy <[email-masked]>
> Francesca Palombini <[email-masked]>
> 
> 
> Internet Area (int)
> Erik Kline <[email-masked]>
> Éric Vyncke <[email-masked]>
> 
> 
> Operations & Management Area (ops)
> Warren Kumari <[email-masked]>
> Robert Wilton <[email-masked]>
> 
> 
> Routing Area (rtg)
> John Scudder <[email-masked]>
> Alvaro Retana <[email-masked]>
> Martin Vigoureux <[email-masked]>
> 
> 
> Security Area (sec) 
> Roman Danyliw <[email-masked]>
> Benjamin Kaduk <[email-masked]>
> 
> 
> Transport Area (tsv)
> Martin Duke <[email-masked]>
> Zaheduzzaman Sarker <[email-masked]>
>