67th IETF - Working Group and BoF Scheduling
IETF Secretariat <ietf-secretariat@ietf.org> Mon, 07 August 2006 22:28 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GADZx-0002Kv-Ai; Mon, 07 Aug 2006 18:28:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GADZw-0002IQ-Gw; Mon, 07 Aug 2006 18:28:08 -0400
Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GADZw-00047S-4h; Mon, 07 Aug 2006 18:28:08 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id 1D4AC3287D; Mon, 7 Aug 2006 22:28:08 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43) id 1GADZw-0002Bm-0y; Mon, 07 Aug 2006 18:28:08 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: Working Group Chairs <wgchairs@ietf.org>
From: IETF Secretariat <ietf-secretariat@ietf.org>
Message-Id: <E1GADZw-0002Bm-0y@ietf.org>
Date: Mon, 07 Aug 2006 18:28:08 -0400
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 025f8c5000216988bfe31585db759250
Cc: irtfchairs@ietf.org, bofchairs@ietf.org
Subject: 67th IETF - Working Group and BoF Scheduling
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Errors-To: wgchairs-bounces@ietf.org
We will be accepting scheduling requests for all Working Groups and BOFs starting today, Monday, August 7, 2006. The milestones and deadlines for scheduling-related activities are as follows: -- Cut-off date for requesting a Working Group session and for preliminary BOF proposals to ADs: Monday, September 18 at 17:00 ET (21:00 UTC/GMT). -- Cut-off date for requests to schedule BoFs: Monday, September 25 at 17:00 ET (21:00 UTC/GMT). -- Preliminary agenda published for comment: Friday, September 29 by midnight ET. -- Cut-off date for requests to reschedule a session: Wednesday, October 11 at 09:00 ET (13:00 UTC/GMT). -- Final schedule published: Monday, October 16 before midnight ET. -- Draft Working Group agendas due: Wednesday, October 25 at 17:00 ET (21:00 UTC/GMT). -- Revised Working Group agendas due: Monday, October 30 at 12:00 ET (17:00 UTC/GMT), 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 agenda@ietf.org. 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, October 25 by 17:00 ET (21:00 UTC/GMT). Revised Working Group agendas are due no later than Monday, October 30 at 12:00 ET (17:00 UTC/GMT). 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 67 Meeting Materials" Web page is: https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=67 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: ietf-action@ietf.org. =============================================================== For your convenience, comprehensive information on requesting meeting sessions at IETF 67 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 ietf-action@ietf.org. If you are unable to use the tool, then you may send your request via e-mail to agenda@ietf.org, with a copy to the appropriate Area Director(s). Requests to schedule BOF sessions must be sent to agenda@ietf.org 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 Wednesday, October 11 at 09:00 ET (13:00 UTC/GMT), 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 66th IETF meeting are included at the end of this message): e. Special requests: f. Number of sessions: g. Length of session: - 1 hour - 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 Brian Carpenter <brc@zurich.ibm.com> Applications Area (app) Ted Hardie <hardie@qualcomm.com> Lisa Dusseault <lisa@osafoundation.org> Internet Area (int) Mark Townsley <townsley@cisco.com> Jari Arkko <jari.arkko@piuha.net> Operations & Management Area (ops) David Kessens <david.kessens@nokia.com> Dan Romascanu <dromasca@avaya.com> Real-time Applications and Infrastructure Area (rai) Cullen Jennings <fluffy@cisco.com> Jon Peterson <jon.peterson@neustar.biz> Routing Area (rtg) Ross Callon <rcallon@juniper.net> Bill Fenner <fenner@research.att.com> Security Area (sec) Sam Hartman <hartmans-ietf@mit.edu> Russ Housley <housley@vigilsec.com> Transport Area (tsv) Lars Eggert <eggert@netlab.nec.de> Magnus Westerlund <magnus.westerlund@ericsson.com> =========================================================== 66th IETF Meeting Attendance Number 16ng 168 6lowpan 141 ancp 54 apparea (AG) 83 atompub 21 autoconf 57 avt 69 behave 94 bmwg 29 btns 73 calcify 18 capwap 60 ccamp 88 dccp 38 dhc 53 dime 33 dkim 47 dkim (2nd session) 63 dmsp 32 dna 68 dnsext 99 dnsop 119 eai 49 ecrit 57 emu 61 enum 147 fecframe 41 forces 33 genarea 41 geopriv 78 hip 42 hiprg hoakey 71 idr 108 imss 9 inch 20 intarea ipdvb 27 ipfix 34 ippm 53 ipr 44 ips 16 isis 28 isms 47 kitten 32 krb-wg 30 l1vpn 83 l2vpn 111 l3vpn 108 lemonade 22 ltans manet 103 mboned 61 mip4 59 mip6 110 mipshop 149 mipshop (2nd sess.) 91 mmusic 159 mobopts 62 monami6 104 mpls 167 msec 29 nea 118 nemo 56 netconf 51 netlmm 128 nfsv4 22 nmrg 48 nsis 54 nsis (2nd session) 22 ntp 18 offpath 128 openpgp 10 opsarea 89 opsec 57 ospf 70 pana 39 pce 103 pim 60 pkix 54 pwe3 119 radext 33 rohc 23 rtgarea 121 rmt 49 rohc rpsec rserpool 15 rtpsec 161 saag 155 samrg 45 sasl 25 shim6 159 sidr 130 sieve 16 simple 128 sip 223 sip (2nd session) 110 sipping 174 sipping (2nd session) 61 smime 27 softwire 98 speermint 111 tcpm 40 tls 56 trill 113 tsvarea 93 tsvwg 106 v6ops 120 wae 80 widex 10 xcon 84
- 67th IETF - Working Group and BoF Scheduling IETF Secretariat