Fw: 81th IETF - Working Group/BOF Scheduling - REMINDER

"Randy Presuhn" <[email protected]> Thu, 2 Jun 2011 10:24:26 -0700
Newsgroups gmane.ietf.disman
Message-ID <001601cc2149$ecfaf260$6801a8c0__42818.3832591914$1307035268$gmane$org@oemcomputer>
Hi -

Forwarded for your information, and to shake loose any "bouncers"
from these mailing lists.

Randy

----- Original Message ----- 
> From: "IETF Agenda" <[email protected]>
> To: "Working Group Chairs" <[email protected]>
> Cc: <[email protected]>
> Sent: Thursday, June 02, 2011 9:22 AM
> Subject: 81th IETF - Working Group/BOF Scheduling - REMINDER 
>
> -----------------------------------------------------------------
> 81th IETF  Quebec City, Canada
> Meeting Dates: July 24-29, 2011
> Host: RIM
> -----------------------------------------------------------------
> IETF meetings start Monday morning and run through Friday mid-afternoon
> (15:15).
> 
> We are accepting scheduling requests for all Working Groups and BOFs
> starting today.  The milestones and deadlines for scheduling-related
> activities are as follows:
> 
> NOTE: cutoff dates are subject to change.
> 
> - 2011-06-06 (Monday): Cutoff date for requests to schedule Working Group
> meetings at 17:00 PT (00:00 UTC). To request a Working Group session, use
> the IETF Meeting Session Request Tool. 
> - 2011- 06-13 (Monday): Cutoff date for BOF proposal requests to Area
> Directors at 17:00 PT (00:00 UTC). To request a BOF, please see
> instructions on Requesting a BOF. 
> - 2011-06-16 (Thursday): Cutoff date for Area Directors to approve BOFs
> at 17:00 PT (00:00 UTC). 
> - 2011-06-23 (Thursday): Preliminary agenda published for comment. 
> - 2011-06-27 (Monday): Cutoff date for requests to reschedule Working
> Group and BOF meetings 17:00 PT (00:00 UTC). 
> - 2011-06-27 (Monday): Working Group Chair approval for initial document
> (Version -00) submissions appreciated by 17:00 PT (00:00 UTC). 
> - 2011-07-01 (Friday): Final agenda to be published. 
> - 2011-07-04 (Monday): Internet Draft Cut-off for initial document (-00)
> submission by 17:00 PT (00:00 UTC), upload using IETF ID Submission Tool.
> - 2011-07-11 (Monday): Internet Draft final submission cut-off by 17:00
> PT (00:00 UTC), upload using IETF ID Submission Tool. 
> - 2011-07-13 (Wednesday): Draft Working Group agendas due by 17:00 PT
> (00:00 UTC), upload using IETF Meeting Materials Management Tool. 
> - 2011-07-18 (Monday): Revised Working Group agendas due by 17:00 PT
> (00:00 UTC), 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://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
> 
> Instructions for using the tool are available at:
> 
> http://www.ietf.org/instructions/session_request_tool_instruction.html
> 
> Please send requests to schedule your BOF sessions to [email protected]. 
> 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 13, 2011 by 17:00 PT (00:00
> UTC).  Revised Working Group agendas are due no later than Monday, July
> 18, 2011 at 17:00 PT (00:00 UTC).  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/cgi-bin/wg/wg_proceedings.cgi
> 
> 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" Web page as soon as they are submitted.
> 
> The URL for the "IETF 81 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=81
> 
> 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 protected].
> ===============================================================
> For your convenience, comprehensive information on requesting meeting
> sessions at IETF 81 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/cgi-bin/wg/wg_session_requester.cgi
> 
> 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 [email protected].  If you are unable to use
> the tool, then you may send your request via e-mail to [email protected],
> with a copy to the appropriate Area Director(s).
> 
> Requests to schedule BOF sessions must be sent to [email protected] 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(s) approved
> request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
> NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
> DESCRIPTION, and the information requested in (4) below. (Please read the
> BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
> requesting a session for a BOF.)
> 
> 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, June 27, 2011 at 17:00 PT (00:00 UTC), 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 
> Russ Housley <[email protected]>
> 
> Applications Area (app)
> Pete Resnick <[email protected]>
> Peter Saint-Andre <[email protected]> 
> 
> Internet Area (int) 
> Jari Arkko <[email protected]>
> Ralph Droms <[email protected]> 
> 
> Operations & Management Area (ops) 
> Ronald Bonica <[email protected]>
> Dan Romascanu <[email protected]>
> 
> Real-time Applications and Infrastructure Area (rai)
> Gonzalo Camarillo <[email protected]>
> Robert Sparks <[email protected]> 
> 
> Routing Area (rtg) 
> Stewart Bryant <[email protected]>
> Adrian Farrel <[email protected]> 
> 
> Security Area (sec) 
> Stephen Farrell <[email protected]>
> Sean Turner <[email protected]> 
> 
> Transport Area (tsv) 
> Wesley Eddy <[email protected]>
> David Harrington <[email protected]> 
> ===========================================================
> 80th IETF Meeting Attendance Number and Minutes Recorded:\
> 
> Working Groups
> 
> 6lowpan - 131 
> 6man - 162 
> abfab - 49 
> abfab (second session) - 36
> alto - 105 
> ancp - 9 
> apparea (AG) - 129 - 145 mins
> armd - 114 - 60 mins 
> atoca - 37 - 71 mins
> avtcore - 90 - 110 mins
> avtext - 75 - 15 mins
> behave - 120 
> bmwg - 34 - 150 mins
> ccamp - 89 
> ccamp (2nd session) - 74 - 165 mins
> cdni BOF - 132 - 123 mins
> clue - 91 - 120 mins
> codec - 59 
> conex - 67 
> core - 106 
> core (2nd session) - 93 
> dane - 115 - 130 mins
> decade - 49 - 120 mins
> dhc - 53 - 120 mins
> dime - 15 
> dispatch - 100 - 60 mins
> dkim - 24 - 65 mins
> dnsext - 154 
> dnsop - 70 - 60 mins
> drinks - 23 - 60 mins
> eai - 23 
> ecrit - 45 
> eman - 51 
> emu - 30 - 90 mins
> fecframe - 14 
> forces - 17 - 80 mins
> geopriv - 61 
> grow - 61
> hip - 17 - 70 mins
> hiprg (RG) - 35 - 120 mins
> hokey - 24
> httpbis - 51 
> hybi - 96 
> iccrg (RG) - 80 - 150 mins
> idr - 107 - 120 mins
> intarea (AG) - 186
> ipfix - 37
> ippm - 21 - 118 mins
> iri - 23 
> isis - 57 
> karp - 41 
> kitten - 14 
> krb-wg - 20 
> l2vpn - 134 - 150 mins
> lisp - 74 
> lwig - 86
> manet - 32 - 140 mins
> marf - 18 
> mboned - 21 
> mext - 43 
> mif - 64 
> mip4 - 16 - 50 mins
> mmusic - 59 - 150 mins
> mpls - 172
> mpls (2nd session) - 106 
> mptcp - 49
> msec - 24 
> multimob - 42 - 160 mins
> nea - 23 - 110 mins
> netext - 42 
> netconf - 28 
> netmod - 30 - 80 mins
> nfsv4 - 18 - 130 mins
> nfsv4 (second session) - 17 - 60 mins
> oauth - 55 - 150 mins
> opsarea (AG) - 85 - 150 mins
> ospf - 39 - 135 mins
> p2prg - 62 
> p2psip - 49 - 128 mins 
> paws BOF - 54 
> pce - 41 
> pcn - 19 - 85 mins
> pcp - 59 
> pim - 30 - 120 mins
> pkix - 49 - 105 mins
> plasma BOF - 42 - 101 mins
> ppsp - 60 - 150 mins
> precis - 28 - 185 mins
> pwe3 - 113 - 152 mins
> radext - 18 - 149 mins
> renum BOF - 100 
> rmt - 19 - 60 mins
> roll - 74 
> rtcweb BOF - 239 
> rtgarea (AG) - 223 
> rtgwg - 119 - 127 mins
> saag (AG) - 99 - 125 mins
> samrg (RG) - 27 - 110 mins
> savi - 21 - 90 mins
> sidr - 137 - 174 mins
> sipclf - 18 - 95 mins
> sipcore - 62 - 55 mins
> sipcore (2nd session) - 35 
> soc - 49
> softwire - 102 
> splices - 41 - 85 mins
> tcpm - 51 
> tictoc - 21 - 145 mins
> trill - 88 - 115 mins
> tsvarea (AG) - 119 - 150 mins
> tsvwg - 66 - 160 mins
> urnbis - 21 - 120 mins
> v6ops - 196
> v6ops (second session) - 136 
> vcarddav - 13 - 60 mins
> vipr - 58 - 109 mins
> websec - 91 - 125 mins
> xmpp - 44