IETF 106 - Working Group/BOF/IRTF Scheduling
IETF Agenda <agenda@ietf.org> Mon, 19 August 2019 20:39 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 5DA7D120045 for <wgchairs@ietf.org>; Mon, 19 Aug 2019 13:39:35 -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 106 - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: agenda@ietf.org
Message-ID: <156624717531.19927.8955656312254070762.idtracker@ietfa.amsl.com>
Date: Mon, 19 Aug 2019 13:39:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/4E4WIF1j2piPB6h3VnIdIalZ4M8>
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, 19 Aug 2019 20:39:35 -0000
----------------------------------------------------------------- IETF 106 – Singapore Meeting Dates: November 16-22, 2019 ----------------------------------------------------------------- We are now accepting scheduling requests for all Working Groups, BOFs, and Research Groups until Friday October 4, 2019. Please review the IETF 105 attendance numbers below for your working group and adjust for IETF 106 as necessary. As discussed in June [1], 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. If you choose to retrieve all the information in your session request from the previous meeting, your conflicts may not be sorted into the correct categories. 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-08-19 (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. • 2019-10-04 (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. • 2019-10-04 (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. • 2019-10-11 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59. • 2019-10-18 (Friday): Preliminary agenda published for comment. • 2019-10-23 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59. • 2019-10-25 (Friday): Final agenda to be published. • 2019-11-06 (Wednesday): Draft Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool. • 2019-11-11 (Monday): Revised Working Group agendas due by UTC 23:59; upload using IETF Meeting Materials Management Tool. =========================================================== IETF 105 Meeting Attendance Numbers 6lo - 55 6man - 79 6man Second Session - 91 6tisch - 24 ace - 37 acme - 45 add - 222 alto - 25 anima - 45 anima - 36 avtcore - 25 babel - 14 bess - 66 bess Second Session - 63 bfd - 36 bier - 31 bmwg - 28 cacao - CANCELLED calext - 14 capport - 45 cbor - 25 ccamp - 23 cfrg - 67 coinrg - 88 core - 48 core - 41 cose - 36 detnet - 29 detnet - 49 dinrg - 79 dispatch - 91 dmm - 32 dnsop - 120 dnsop - 152 dnssd - 40 dots - 17 dprive - 89 dtn - 15 emu - 35 gaia - 44 grow - 75 hrpc - 38 httpbis - 87 httpbis Second Session - 54 i2nsf - 28 iccrg - 78 ice - CANCELLED icnrg - 56 idr - 84 idr Second Session - 89 intarea - 48 ippm - 45 ipsecme - 35 ipwave - 26 irtfopen - 107 jmap - 15 lake - 136 lamps - 33 lisp - 25 loops - 94 lpwan - 38 lsr - 80 lsr - 52 lsvr - 65 manet - 15 maprg - 127 mboned - 14 mile - 19 mls - 39 mops - 105 mpls - CANCELLED mpls - 73 mptcp - 45 netconf - 56 netmod - 48 netmod - 47 netrqmts - 66 nfsv4 - 11 nmrg - 70 ntp - 20 nvo3 - 43 nwcrg - 16 oauth - 42 oauth Second Session - 26 opsawg - 54 panrg - 49 pce - 54 pearg - 93 pim - 34 quic - 144 quic - 139 rats - 79 rats - 44 regext - 49 rift - 30 rmcat - 16 roll - 15 rtgwg - 149 rtgwg - 109 rum - 18 saag - 140 sacm - 22 secdispatch - 101 secevent - 18 sidrops - 61 spring - 136 stir - 53 suit - 72 t2trg - 74 taps - 38 tcpm - 42 tdd - 230 teas - 53 teas Second Session - 58 teep - 49 teep - 45 tls - 98 tls - 105 tsvarea - 68 tsvwg - 91 tsvwg - 71 v6ops - 69 =========================================================== 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 ietf-action@ietf.org. If you are unable to use the tool, then you may send your request via e-mail to agenda@ietf.org, with a copy to the appropriate Area Director(s). Requests to schedule BOF sessions must be sent to agenda@ietf.org 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 106 Meeting Materials" Web page is: https://datatracker.ietf.org/meeting/106/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: ietf-action@ietf.org. =============================================================== For your convenience please find a list of the IETF Area Directors with their e-mail addresses below: IETF Chair Alissa Cooper <alissa@cooperw.in>; Applications and Real-Time Area (art) Barry Leiba <barryleiba@computer.org>; Alexey Melnikov <aamelnikov@fastmail.fm>; Adam Roach <adam@nostrum.com>; Internet Area (int) Suresh Krishnan <suresh@kaloom.com>; Éric Vyncke <evyncke@cisco.com>; Operations & Management Area (ops) Ignas Bagdonas <ibagdona@gmail.com>; Warren Kumari <warren@kumari.net>; Routing Area (rtg) Deborah Brungard <dbrungard@att.com>; Alvaro Retana <aretana@cisco.com>; Martin Vigoureux <martin.vigoureux@nokia.com>; Security Area (sec) Roman Danyliw <rdd@cert.org>; Benjamin Kaduk <kaduk@mit.edu>; Transport Area (tsv) Mirja Kühlewind <ietf@kuehlewind.net>; Magnus Westerlund <magnus.westerlund@ericsson.com> =============================================================== [1] https://mailarchive.ietf.org/arch/msg/wgchairs/TApt-izFF-Mv8o2NjrShO_1X_R8
- IETF 106 - Working Group/BOF/IRTF Scheduling IETF Agenda