Subject: [sacm] FW: 91st IETF - Working Group/BOF/IRTF Scheduling

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Mon, 25 Aug 2014 14:23:47 +0000

Hi, 

Adam and me think that we should attempt to do the same thing for IETF 91 that we did for IETF 90 and request two 2.5-hour sessions, with one near the beginning of the week and the other on Friday.

Any concerns, comments or other suggestions? 

Regards,

Dan

> -----Original Message-----
> From: WGChairs [mailto:[email-masked]] On Behalf Of IETF
> Agenda
> Sent: Tuesday, August 12, 2014 1:32 AM
> To: Working Group Chairs
> Cc: [email-masked]
> Subject: 91st IETF - Working Group/BOF/IRTF Scheduling
> 
> -----------------------------------------------------------------
> 91st IETF – Honolulu, HI, USA
> Meeting Dates: November 9 - 14, 2014
> -----------------------------------------------------------------
> 
> We are accepting scheduling requests for all Working Groups, BOFs, and
> Research Groups starting today.
> 
> NOTE: Please ensure your list of conflicts is complete and up to date prior to
> submitting your session request.
> 
> The milestones and deadlines for scheduling-related activities are as follows:
> Cut-off dates are subject to change.
> 
> •	2014-08-11 (Monday): Working Group and BOF scheduling begins. To
> request a Working Group session, use the IETF Meeting Session Request
> Tool.
> •	2014-09-26 (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.
> •	2014-09-26 (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.
> •	2014-10-03 (Friday): Cut-off date for Area Directors to approve BOFs
> at UTC 23:59.
> •	2014-10-10 (Friday): Preliminary agenda published for comment.
> •	2014-10-13 (Monday): Cut-off date for requests to reschedule
> Working Group and BOF meetings UTC 23:59.
> •	2014-10-17 (Friday): Final agenda to be published.
> •	2014-10-27 (Monday): Draft Working Group agendas due by UTC
> 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-11-03 (Monday): Revised Working Group agendas due by UTC
> 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-12-05 (Friday): Proceedings submission cutoff date by UTC
> 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-12-26 (Friday): Proceedings submission corrections cutoff date
> by UTC 23:59, upload using IETF Meeting Materials Management Tool.
> 
> 
> ==========================================================
> =====
> For your convenience, comprehensive information on requesting meeting
> sessions 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://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 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, October 13th, 2014, 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.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
> 
> 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 Monday, October 27th, 2014 at UTC 23:59.  Revised
> Working Group agendas are due no later than Monday, November 3rd, 2014
> at UTC 23:59.  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://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 91 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/meeting/91/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
> Jari Arkko <[email-masked]>
> 
> Applications Area (app)
> Barry Leiba <[email-masked]>
> Pete Resnick <[email-masked]>
> 
> Internet Area (int)
> Brian Haberman <[email-masked]> Ted Lemon
> <[email-masked]>
> 
> Operations & Management Area (ops)
> Benoit Claise <[email-masked]>
> Joel Jaeggli <[email-masked]>
> 
> Real-time Applications and Infrastructure Area (rai) Richard Barnes
> <[email-masked]> Alissa Cooper <[email-masked]>
> 
> Routing Area (rtg)
> Alia Atlas <[email-masked]>
> Adrian Farrel <[email-masked]>
> 
> Security Area (sec)
> Stephen Farrell <[email-masked]> Kathleen Moriarty
> <[email-masked]>
> 
> Transport Area (tsv)
> Spencer Dawkins  <[email-masked]> Martin Stiemerling
> <[email-masked]>
> 
> 
> ==========================================================
> =
> 90th IETF Meeting Attendance Numbers
> 
> 6lo - 66
> 6tisch - 63
> abfab – 42
> ace - 70
> actn (BoF) - 114
> alto  - 38
> appsawg/apparea - 157
> aqm - 50
> avtcore - 49
> avtext - 40
> bfd - 46
> bmwg - 24
> ccamp - 42
> ccamp (2nd session) - 44
> cdni – 35
> cfrg - 80
> clue – 23
> clue (2nd session) - 21
> core - 64
> core (2nd session) – 31
> dane - 158
> dart - 57
> dclcrg (RG BoF) - 37
> dhc - 44
> dice - 58
> dime - 17
> dispatch - 69
> dmm - 30
> dmm (2nd session) - 28
> dnsop - 149
> dnssd - 63
> dtnwg (BoF) - 85
> ecrit - 28
> forces - 76
> grow - 45
> homenet - 136
> httpauth - 56
> httpbis - Not Provided
> httpbis (2nd session) - Not Provided
> i2rs - 119
> ianaplan - 170
> icnrg (RG) - 90
> idr - 72
> intarea (AG) - 94
> ippm - 44
> ipsecme - 37
> IRTF Open Meeting - 87
> isis - 42
> jose - 41
> kitten - 16
> l2vpn - 96
> l3vpn - 50
> lisp - 24
> lmap - 36
> lwig - 23
> manet - 17
> mboned - 16
> mif – 49
> mile - 32
> mmusic - 56
> mmusic (2nd session) - 42
> mpls - 123
> mpls (2nd session) - 68
> mptcp - 73
> netconf - 94
> netext - 26
> netmod - 106
> nfsv4 - 17
> nmrg (RG) - 56
> ntp (combined with tictoc) - 30
> nvo3 - 102
> oauth - 44
> opsawg/opsarea - 79
> ospf - 42
> paws – 23
> pce - 87
> pim - 21
> ppsp - 14
> precis - 27
> pwe3 - 31
> radext - 11
> rfcform - 66
> rmcat - 52
> rmcat (2nd session) - 31
> roll - 33
> rtcweb - 101
> rtcweb (2nd session) - 87
> rtgarea (AG) - 150
> rtgwg - 64
> saag (AG) - 168
> sacm - 40
> sacm (2nd session) - 29
> scim - 28
> sdnrg (RG) – 193
> sfc - 248
> sidr - 60
> sipcore - 34
> siprec - 11
> softwire - 54
> spring - 157
> stir - 43
> straw - 23
> sunset4 - 75
> taps - 107
> tcpinc - 96
> tcpm - 46
> tictoc (combined with ntp) - 30
> tls - 139
> tls (2nd session) - 94
> tram - 30
> trans - 44
> trill - 19
> tsvwg - 75
> tsvwg (2nd session) - 76
> ucan (BoF) - 159
> uta - 102
> urnbis - 29
> v6ops - 198
> v6ops (2nd session) – 62
> vnfpool (BoF) - 180
> weirds - 60
> xrblock - 25