Subject: REMINDER - IETF 99 - Working Group/BOF/IRTF Scheduling

From: IETF Agenda <[email-masked]>
Date: Wed, 24 May 2017 11:27:46 -0700

-----------------------------------------------------------------
IETF 99 – Prague, Czech Republic
Meeting Dates: July 16-21, 2017
-----------------------------------------------------------------

Please review the IETF 98 attendance numbers below for your working group and adjust for IETF 99 as necessary. Please also check to ensure your conflict lists are up to date.

The milestones and deadlines for scheduling-related activities are as follows:
Cut-off dates are subject to change.

•	2017-06-02 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. 
•	2017-06-02 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. 
•	2017-06-09 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
•	2017-06-16 (Friday): Preliminary agenda published for comment.
•	2017-06-21 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
•	2017-06-23 (Friday): Final agenda to be published.
•	2017-07-05 (Friday): Draft Working Group agendas due by UTC 23:59
•	2017-07-10 (Monday): Revised Working Group agendas due by UTC 23:59 

IETF 98 Meeting Attendance Numbers

6lo - 84
6man - 91
6tisch - 64
ace - 98
acme - 69
alto - 15
anima (1st session) - 51
anima (2nd session) - 66
avtcore - 33
babel - 16
bess - 72
bfd - 20
bier - 56
bmwg - 31
capport - 48
casm (BoF 98) - 60
cbor - 40
ccamp - 35
codec - 7
core (1st session) - 73
core (2nd session) - 49
curdle - 22
detnet - 78
dhc - 19
dime - 7
dispatch - 66
dmm - 34
dnsop - 133
dnssd - 61
dots - 67
dtn - 20
grow - 63
homenet - 104
hrpc - 80
httpbis - 75
i2nsf - 39
i2rs - 49
iasa2.0 (BoF 98) - 77
iccrg - 86
icnrg - 58
idr - 67
intarea - 103
ippm - 65
ipsecme - 54
ipwave - 64
irtfopen – Did not return
isis - 28
jmap - 31
lamps - 34
lime - 9
lisp - 30
lpwan - 81
lwig - 41
manet - 11
maprg - 107
mboned - 36
mile - 22
mmusic - 36
mpls (1st session) - 70
mpls (2nd session) - 46
mptcp - 39
mtgvenue - 46
netconf - 64
netmod (1st session) - 80
netmod (2nd session) - 53
netvc - 38
nfvrg (1st session) - 115
nfvrg (2nd session) - 82
nmrg - 66
ntp (combined with tictoc) -22
nvo3 (1st session) - 73
nvo3 (2nd session) - 43
oauth (1st session) - 48
oauth (2nd session) - 45
opsawg/opsarea - 74
opsec - 29
ospf - 46
payload - 28
pce - 67
perc - 33
pim - 33
quic - 194
regext (1st session) - 42
regext (2nd session) - 42
roll - 31
rtcweb (1st session) - 57
rtcweb (2nd session) - 43
rtgarea - 82
rtgwg (1st session) - 127
rtgwg (2nd session) - 100
saag - 145
sacm - 42
secevent - 53
sfc - 103
sidrops - 57
sipcore - 20
spring - 90
stir - 33
supa - 31
t2trg - 94
taps - 39
tcpinc - CANCELLED
tcpm - 61
teas - 64
teep - 96
tictoc (combined with ntp) - 22
tls - 168
tokbind - 55
tram - 19
trans - 49
trill - 14
tsvarea (1st session) - 97
tsvarea (2nd session) - 106
tsvwg (1st session) - 66
tsvwg (2nd session) - 55
uta - 44
v6ops - 106
wugh (BoF 98) – 116
 ===========================================================

How to Request a WG Session or BOF:

1. Requests to schedule Working Group sessions should be submitted using the "IETF Meeting Session Request Tool," a Web-based tool for submitting all of the information required by the Secretariat to schedule your sessions.  The URL for the tool is:

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

Instructions for using the tool are available at:

http://www.ietf.org/wg/request-tool-instructions.html

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 e-mail to [email-masked], with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to [email-masked] 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.

2. 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 4. Please read RFC 5434 for instructions on how to drive a successful BOF effort. 

3. 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, 2.5 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/

Additional information about this tool is available at:

http://www.ietf.org/wg/meeting-materials.html

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 99 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/99/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].

===============================================================
For your convenience please find a list of the IETF Area Directors with their e-mail addresses below:

IETF Chair 
Alissa Cooper <[email-masked]>

Applications and Real-Time Area (art)
Ben Campbell <[email-masked]>
Alexey Melnikov <[email-masked]>
Adam Roach <[email-masked]>

Internet Area (int) 
Suresh Krishnan <[email-masked]>
Terry Manderson <[email-masked]>

Operations & Management Area (ops) 
Benoit Claise <[email-masked]> 
Warren Kumari <[email-masked]>

Routing Area (rtg) 
Alia Atlas <[email-masked]>
Deborah Brungard <[email-masked]>
Alvaro Retana <[email-masked]>

Security Area (sec) 
Kathleen Moriarty <[email-masked]>  
Eric Rescorla <[email-masked]>

Transport Area (tsv) 
Spencer Dawkins  <[email-masked]>
Mirja Kühlewind <[email-masked]>