[Agentx] Fw: 78th IETF - Working Group - REMINDER

["Randy Presuhn" <[e-mail]>]

Hi -

Forwarded for your information, in case you'd like to request a BOF.

Randy

> From: "IETF Agenda" <[e-mail]>
> To: "Working Group Chairs" <[e-mail]>
> Cc: <[e-mail]>
> Sent: Wednesday, June 09, 2010 10:55 AM
> Subject: 78th IETF - Working Group - REMINDER
>
> -----------------------------------------------------------------
> 78th IETF  Maastricht, Netherlands
> Meeting Dates: July 25-30, 2010
> Host: SIDN
> -----------------------------------------------------------------
> 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.
> 
> 2010-06-01 (Tuesday): Cutoff date for BOF proposal requests to Area
> Directors at 17:00 PT (24:00 UTC). To request a BOF, please see
> instructions on Requesting a BOF.
> 2010-06-14 (Monday): Cutoff date for requests to schedule Working Group
> meetings at 17:00 PT (24:00 UTC). To request a Working Group session, use
> the IETF Meeting Session Request Tool. ** Please note - if you send in
> your request after this date your Working Group will not be scheduled
> until after the Preliminary agenda has been published (Wednesday, June 23,
> 2010) and will NOT receive priority scheduling. **
> 2010-06-14 (Monday): Cutoff date for Area Directors to approve BOFs at
> 17:00 PT (24:00 UTC).
> 2010-06-23 (Wednesday): Preliminary agenda published for comment.
> 2010-06-28 (Monday): Cutoff date for requests to reschedule Working Group
> and BOF meetings 17:00 PT (24:00 UTC).
> 2010-07-02 (Friday): Final agenda to be published.
> 2010-07-14 (Wednesday): Draft Working Group agendas due by 17:00 PT (24:00
> UTC), upload using IETF Meeting Materials Management Tool.
> 2010-07-19 (Monday): Revised Working Group agendas due by 17:00 PT (24: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 [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 14 by 17:00 PT (24:00 UTC).
> Revised Working Group agendas are due no later than Monday, July 19 at
> 17:00 PT (24: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 78 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=78
> 
> 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 78 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 [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(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 28 at 17:00 PT (24: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 (figures from the 77th IETF meeting are
> included at the end of this message):
> 
>     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 <[e-mail]>
> 
> Applications Area (app)
> Alexey Melnikov <[e-mail]> Peter Saint-Andre
> <[e-mail]>
> 
> Internet Area (int)
> Jari Arkko <[e-mail]>
> Ralph Droms <[e-mail]>
> 
> Operations & Management Area (ops)
> Ronald Bonica <[e-mail]>
> Dan Romascanu <[e-mail]>
> 
> Real-time Applications and Infrastructure Area (rai) Gonzalo Camarillo
> <[e-mail]> Robert Sparks <[e-mail]>
> 
> Routing Area (rtg)
> Stewart Bryant <[e-mail]>
> Adrian Farrel <[e-mail]>
> 
> Security Area (sec)
> Tim Polk <[e-mail]>
> Sean Turner <[e-mail]>
> 
> Transport Area (tsv)
> Lars Eggert <[e-mail]>
> David Harrington <[e-mail]>
> ===========================================================
> 77th IETF Meeting Attendance Number
> 
> 6lowpan 108
> 6man 125
> alto 157
> ancp 20
> apparea (AG) 79
> autoconf 31
> avt 47
> avt (2nd session) 43
> behave 130
> behave (2nd session) 63
> bmwg 23
> ccamp 96
> ccamp (2nd session) 94
> codec-BOF 95
> conex-BOF 112
> conex-BOF (2nd session) 80
> core 145
> csi 19
> decade 48
> dhc 53
> dime 30
> dnsext 145
> dnsop 106
> drinks 44
> dtnrg (RG) 51
> e2md-BOF 11
> eai 29
> ecrit 63
> emu 33
> fecframe 10
> forces 21
> geopriv 60
> grow 38
> hip 34
> hiprg (RG) 33
> hokey 11
> hokey (2nd session) 27
> httpbis 39
> httpstate 31
> hybi 31
> iccrg (RG) 65
> idr 106
> intarea (AG) 213
> ipfix 27
> ippm 29
> ipsecme 55
> iri 22
> isis 42
> kitten 13
> krb-wg 25
> l2vpn 51
> l3vpn 91
> ledbat 59
> lisp 211
> lisp (2nd session) 97
> manet 45
> marf 25
> martini 39
> martini (2nd session) 27
> mboned 34
> mediactrl 28
> mext 64
> mif 83
> mip4 11
> mmusic 64
> morg 16
> mpls 157
> mpls (2nd session) 154
> mptcp 97
> mptcp (2nd session) 41
> multimob 37
> nea 28
> netconf 38
> netext 42
> netmod 21
> newprep-BOF 50
> nfsv4 27
> oauth 79
> opsarea (AG) 55
> opsawg 57
> opsec 43
> ospf 23
> p2prg 60
> p2psip 69
> pce 35
> pcn 21
> pim 38
> pkix 53
> ppsp NO SHEETS
> pwe3 88
> pwe3 (2nd session) 77
> radext 33
> rmt 20
> roll 103
> rrg (RG) 65
> rtgarea (AG) 101
> rtgwg 53
> saag (AG) 118
> samrg (RG) 18
> savi 40
> sidr 111
> sieve 11
> sipclf 39
> sipcore 73
> sipcore (2nd session) 42
> siprec 64
> softwire 93
> speermint 43
> storm 16
> tcpm 36
> tictoc 46
> tls 36
> trill 57
> tsvarea (AG) 77
> tsvwg 106
> v6ops 177
> v6ops (2nd session) 116
> vcarddav 19
> vnrg (RG) 81
> vwrap 27
> wgdtspec-BOF 19
> xmpp 57
> yam 25
>