[secdir] Fwd: 87th IETF - Working Group/BOF/IRTF Scheduling - Cut-off Monday, June 3

[Stephen Farrell <[e-mail]>]

FYI - if you've not gotten your meeting request in...

S


-------- Original Message --------
Subject: 87th IETF - Working Group/BOF/IRTF Scheduling - Cut-off Monday,
June 3
Date: Fri, 31 May 2013 07:57:33 -0700
From: IETF Agenda <[e-mail]>
Reply-To: IETF Agenda <[e-mail]>
To: Working Group Chairs <[e-mail]>
CC: [e-mail]

Subject: 87th IETF - Working Group/BOF/IRTF Scheduling

-----------------------------------------------------------------
87th IETF – Berlin, Germany
Meeting Dates: July 28 – August 2, 2013
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

We are accepting scheduling requests for all Working Groups, BOFs, and
Research Groups starting today.  The milestones and deadlines for
scheduling-related activities are as follows:

NOTE: cutoff dates are subject to change.

- 2013-06-03 (Monday): Cut-off date for requests to schedule Working
Group meetings at UTC 24:00. To request a Working Group session, use the
IETF Meeting Session Request Tool.
- 2013-06-17 (Monday): Cut-off date for BOF proposal requests to Area
Directors at UTC 24:00. To request a BOF, please see instructions on
Requesting a BOF.
- 2013-06-20 (Thursday): Cut-off date for Area Directors to approve BOFs
at UTC 24:00.
- 2013-06-27 (Thursday): Preliminary agenda published for comment.
- 2013-07-01 (Monday): Cut-off date for requests to reschedule Working
Group and BOF meetings UTC 24:00.
- 2013-07-05 (Friday): Final agenda to be published.
- 2013-07-17 (Wednesday): Draft Working Group agendas due by UTC 24:00,
upload using IETF Meeting Materials Management Tool.
- 2013-07-22 (Monday): Revised Working Group agendas due by UTC 24:00,
upload using IETF Meeting Materials Management Tool.
- 2013-08-30 (Friday): Proceedings submission cutoff date by UTC 24:00,
upload using IETF Meeting Materials Management Tool.
- 2013-09-18 (Wednesday): Proceedings submission corrections cutoff date
by UTC 24:00, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your sessions.

The URL for the tool is:

https://pub.ietf.org/sreq/

Please send requests to schedule your BOF sessions to [e-mail].
Please include the acronym of your BOF in the subject line of the
message, and include all of the information specified in item (4) of
"Requesting Meeting Sessions at IETF Meetings" in the body.  (This
document is included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, July 17, 2013 at UTC 24:00.
Revised Working Group agendas are due no later than Monday, July 22,
2013 at UTC 24:00.  The proposed agenda for a BOF session should be
submitted along with your request for a session.  Please be sure to copy
your Area Director on that message.

Please submit the agendas for your Working Group sessions 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://pub.ietf.org/proceedings/

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.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 87 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/87/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, comprehensive information on requesting meeting
sessions at IETF 87 is presented below:

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://pub.ietf.org/sreq/

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

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 Working Group or BOF session request by e-mail, please
include the Working Group or 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. The approval depends on, for instance,
Internet-Drafts and list discussion on the suggested topic. BOF agenda
requests, if approved, will be submitted to the IETF Secretariat by the ADs.

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned,
based on availability, after Monday, July 1, 2013, the cut-off date for
requests to reschedule a session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets:

    b. AREA under which Working Group or 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 1/2 hours
       - 2 hours
       - 2 1/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).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair
Jari Arkko <[e-mail]>

Applications Area (app)
        Barry Leiba <[e-mail]>
        Pete Resnick <[e-mail]>

Internet Area (int)
Brian Haberman <[e-mail]>
        Ted Lemon <[e-mail]>

Operations & Management Area (ops)
Benoit Claise <[e-mail]>
Joel Jaeggli <[e-mail]>

Real-time Applications and Infrastructure Area (rai)
Gonzalo Camarillo <[e-mail]>
Richard Barnes <[e-mail]>

Routing Area (rtg)
Stewart Bryant <[e-mail]>
Adrian Farrel <[e-mail]>

Security Area (sec)
Stephen Farrell <[e-mail]>
Sean Turner <[e-mail]>

Transport Area (tsv)
Martin Stiemerling <[e-mail]>
 ===========================================================
86th IETF Meeting Attendance Number

6man - 96
abfab - 34
aggsrv (BoF) - 93
alto  - 36
appsawg - 98
avtcore - 57
avtext - 61
behave - 45
bmwg - 24
ccamp - 87
ccamp (2nd session) - 51
ccamp (3rd session) - 32
cdni - 51
cdni (2nd session) - 49
cfrg (RG) - 35
clue - 53
clue (2nd session) - 50
core - 67
core (2nd session) - 49
dhc - 54
dime - 24
dispatch - 66
dmm - 30
dnsop - 50
ecrit - 39
eman - 28
emu - 24
forces - 41
grow - 49
history (BoF) - 150
homenet - 137
httpauth - 64
httpbis - 79
i2rs - 228
iab-wcit (BoF) - 146
iccrg (RG) - 97
icnrg (RG) - 76
idr - 80
intarea (AG) - 72
ipfix - 19
ippm - 44
ippm (2nd session) - 36
iprbis (BoF) - 58
ipsecme - 47
IRTF Open Meeting - 63
isis - 46
jose - 65
json (BoF) - 86
karp - 29
l2vpn - 103
l3vpn - 82
lmap (BoF) - 100
lwig - 39
manet - 23
mboned - 24
mif - 40
mile - 39
mmusic - 92
mmusic (2nd session) - 61
mpls - 114
mpls (2nd session) - 107
mptcp - 43
multimob - 32
ncrg (RG) - 73
netconf - 67
nfsv4 - 13
nmrg (RG) - 15
nwcrg (RG BoF) - 40
nvo3 - 226
oauth - 42
oauth (2nd session) - 44
opsawg - 88
opsec - 32
ospf - 26
p2psip - 27
paws - 32
pce - 99
pcp - 43
pcp (2nd session) - 33
pim - 24
pkix - 50
precis - 27
pwe3 - 77
radext - 22
rmcat - 82
roll - 63
rtcweb - 170
rtcweb (2nd session) - 137
rtgarea (AG) - 51
rtgwg - 117
saag (AG) - 115
sacm (BoF) - 48
scim - 25
sdnrg (RG) - 265
sidr - 69
sidr (2nd session) - 57
siprec - 27
softwire - 75
softwire (2nd session) - 66
straw - 26
sunset4 - 82
tcpm - 39
tictoc - 26
tls - 76
trill - 55
tsvarea (AG) - 160
tsvwg - 94
tsvwg (2nd session) - 54
v6ops - 157
v6ops (2nd session) - 113
websec - 68
weirds - 55
weirds (2nd session) - 25
wpkops - 34
xmpp - 23
xrblock - 27