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

[Fred Baker <[e-mail]>]

I will be asking for a slot for a working group meeting in Vancouver soon. The secretariat is asking for specific categories of conflict avoidance. If you fall into any of these categories, please let Ron and I ([e-mail]) know.

Sent from my iPad

Begin forwarded message:

> From: IETF Agenda <[e-mail]>
> Date: December 19, 2019 at 2:40:55 PM PST
> To: Working Group Chairs <[e-mail]>
> Subject: IETF 107 - Working Group/BOF/IRTF Scheduling
> Reply-To: [e-mail]
> 
> -----------------------------------------------------------------
> IETF 107 – Vancouver, Canada
> Meeting Dates: March 21-27, 2020
> -----------------------------------------------------------------
> 
> We are now accepting scheduling requests for all Working Groups, BOFs, and Research Groups until Friday February 7, 2020. Please review the IETF 106 attendance numbers below for your working group and adjust for IETF 107 as necessary. 
> 
> As a reminder, the conflict list descriptions changed for IETF 106. These new labels will continue for IETF 107. In an attempt to provide more clarity about conflicts, the old priority options have been replaced with more explicit indications about the type of conflict. These new 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!
> 
> 
> 
> The milestones and deadlines for scheduling-related activities are as follows:
> Cut-off dates are subject to change.
> 
> • 2019-12-16 (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 [e-mail] to get advance help with the request. 
> • 2020-02-07 (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.
> • 2020-02-07 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
> • 2020-02-14 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
> • 2020-02-21 (Friday): Preliminary agenda published for comment.
> • 2020-02-26 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
> • 2020-02-28 (Friday): Final agenda to be published.
> • 2020-03-11 (Wednesday): Draft Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool.
> • 2020-03-16 (Monday): Revised Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool.
> 
> 
> ===========================================================
> 
> 
> IETF 106 Meeting Attendance Numbers
> 
> 
> 6lo - 39
> 6man - 121
> 6man 2nd session - 59
> 6tisch - 15
> abcd - 257
> ace - 40
> acme - 43
> alto - 15
> anima - 42
> anima 2nd session - 28 
> avtcore - 16
> babel - 9
> bess - 74
> bess 2nd session - 59 
> bfd - 17
> bier - 41
> bmwg - 22
> calext - 12
> cbor - 15
> ccamp - 35
> cfrg - 72
> coinrg - 74
> core - 25
> core - 22
> cose - 18
> detnet - 57
> detnet - 37
> dhc - 24
> dinrg - CANCELLED
> dispatch - 70
> dmm - 46
> dnsop - 107
> dnsop 2nd session - 116 
> dnssd - 69
> dnssd 2nd session - 30 
> dots - 18
> dprive - 101
> dtn - 13
> emu - 38
> extra - 14
> gaia - 41
> gendispatch - 33
> git - 31
> grow - 34
> homenet - 29
> hrpc - 59
> httpbis - 75
> httpbis 2nd session - 41
> iccrg - 75
> icnrg - 65
> idr - 82
> idr 2nd session - 63
> intarea - 54
> ippm - 47
> ipsecme - 29
> irtfopen - 149
> jmap - 13
> lake - 62
> lamps - 28
> lisp - 25
> lpwan - 36
> lsr - 101
> lsr 2nd session - 40
> lsvr - 43
> lwig - 21
> manet - 13
> maprg - 92
> mathmesh - 92
> mboned - 17
> mls - 33
> mops - 41
> mpls - 86
> mptcp - 32
> netconf - 37
> netmod - 67
> netmod 2nd session - 54 
> nmrg - 43
> nmrg 2nd session - 41
> ntp - 23
> nvo3 - 21
> nwcrg - 24
> oauth - 37
> oauth 2nd session - 34
> opsawg - 68
> panrg - 48
> pce - 42
> pearg - 87
> pim - 20
> qirg - 54
> quic - 158
> quic 2nd session - 94
> rats - 36
> rats 2nd session - 37
> raw - 114
> regext - 38
> rift - 25
> rmcat - 17
> roll - 19
> roll 2nd session - 24 
> rseme - 62
> rtgwg - 129
> rtgwg 2nd session - 78
> rum - 6
> saag - 74
> sacm - 20
> secdispatch - 82
> sidrops - 62
> spring - 188
> spring 2nd session - 67 
> stir - 24
> suit - 52
> t2trg - 54
> taps - 37
> tcpm - 36
> teas - 63
> teas 2nd session - 81 
> teep - 44
> teep 2nd session - 31 
> tls - 85
> tls 2nd session - 75
> tmrid - 45
> tsvarea - 50
> tsvwg - 98
> tsvwg 2nd session - 90 
> txauth - 91
> v6ops - 64
> webtrans - 129
> wpack - 91
> 
> 
> ===========================================================
> 
> 
> How to Request a WG Session or BOF:
> 
> Requests to schedule Working 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 [e-mail].  If you are unable to use the tool, then you may send your request via e-mail to [e-mail], with a copy to the appropriate Area Director(s).
> 
> Requests to schedule BOF sessions must be sent to [e-mail] with a copy to the appropriate Area Director(s).
> 
> When submitting a BOF session request by e-mail, 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 covered in item 3. Please read RFC 5434 for instructions on how to drive a successful BOF effort. 
> 
> 
> 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. Expected Attendance:
> e. Special requests:
> f. Number of sessions:
> g. Length of session: 1 hour, 1.5 hours, 2 hours
>               
> For more information on scheduling Working Group and BOF sessions, please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (http://www.ietf.org/rfc/rfc2418.txt).
> 
> ===============================================================
> 
> Submitting Session Agendas
> 
> Please submit the agendas for your Working Group 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 107 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/meeting/107/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: [e-mail].
> 
> ===============================================================
> 
> For your convenience please find a list of the IETF Area Directors with their e-mail addresses below:
> 
> 
> IETF Chair
> Alissa Cooper <[e-mail]>
> 
> 
> Applications and Real-Time Area (art)
> Barry Leiba <[e-mail]>
> Alexey Melnikov <[e-mail]>
> Adam Roach <[e-mail]>
> 
> 
> 
> Internet Area (int)
> Suresh Krishnan <[e-mail]>
> Éric Vyncke <[e-mail]>
> 
> 
> 
> Operations & Management Area (ops)
> Ignas Bagdonas <[e-mail]>
> Warren Kumari <[e-mail]>
> 
> 
> 
> Routing Area (rtg)
> Deborah Brungard <[e-mail]>
> Alvaro Retana <[e-mail]>
> Martin Vigoureux <[e-mail]>
> 
> 
> 
> Security Area (sec) 
> Roman Danyliw <[e-mail]>
> Benjamin Kaduk <[e-mail]>
> 
> 
> 
> Transport Area (tsv)
> Mirja Kühlewind <[e-mail]>
> Magnus Westerlund <[e-mail]>
>