Subject: 66th IETF - Working Group and BOF Scheduling

From: IETF Agenda <[email-masked]>
Date: Fri, 26 May 2006 07:19:41 -0400

REMINDER: We are currently accepting scheduling requests for all Working Groups
and BOFs.  The milestones and deadlines for scheduling-related activities are as
follows:

-- Cut-off date for requesting a session: Monday, June 5 at 17:00 ET (21:00
UTC/GMT).
-- Preliminary agenda published for comment: Friday, June 9 by midnight ET.
-- Cut-off date for requests to reschedule a session: Wednesday, June 14 at
09:00 ET (13:00 UTC/GMT).
-- Final schedule published: Monday, June 19 before midnight ET.

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-masked].  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, but by no later than
Monday, July 3 at 12:00 ET (16: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 66 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66

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, comprehensive information on requesting meeting sessions
at IETF 66 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-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(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 
Area Director.  Additional sessions will be assigned, based on availability,
after Wednesday, June 14 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 65th 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 <[email-masked]>

Applications Area (app) 
Ted Hardie <[email-masked]> 
Lisa Dusseault <[email-masked]>

Internet Area (int) 
Mark Townsley <[email-masked]>
Jari Arkko <[email-masked]>

Operations & Management Area (ops) 
David Kessens <[email-masked]>
Dan Romascanu <[email-masked]>

Real-time Applications and Infrastructure Area (rai)
Cullen Jennings <[email-masked]>
Jon Peterson <[email-masked]>

Routing Area (rtg) 
Ross Callon <[email-masked]>
Bill Fenner <[email-masked]> 

Security Area (sec) 
Sam Hartman <[email-masked]>
Russ Housley <[email-masked]>

Transport Area (tsv) 
Lars Eggert <[email-masked]>
Magnus Westerlund <[email-masked]>
===========================================================
65th IETF Meeting Attendance Numbers

16ng 71
6lowpan 44
apparea 67
asrg 44
autoconf 79
avt 99
behave 77
bmwg 21
btns 66
calsify 10
capwap 55
ccamp 84
crisp 24
dccp 41
dhc 49
dime 31
dix 121
dkim 55
dkim 94
dna 83
dnsext 98
dnsop 76
dtnrg 51
eai 45
eap 40
ecrit 80
emu 58 
enum 104
forces 36
genarea 48
geopriv 64
grow 90
hip 54
hoakey 136
idr 113
imapext 19
intarea 103
ipfix 46
ippm 41
ipr 43
ips 12
isis 45
isms 36
krb-wg 27
l1vpn 64
l2cp 120
l2vpn 99
l3vpn 150
l6ng 63
lemonade 25
lemonade 30
ltans 13
manet 112
mboned 67
mip4 56
mip6 141
mipshop 77
mipshop 89
mmusic 131
mobike 65
mobopts 62
monami6 87
mpls 162
msec 37
nea 83
nemo 143
netconf 56
netlmm 119
nfsv4 (one) 17
nfsv4 (two) 21
nsis 30
nsis 52
ntp 27
opsec 52
ospf 86
p2p-rg 60
p2p-sip 201
pana 51
pce 99
pim 39
pk4ipsec 22
pkix 36
pmtud 14
psamp 36
pwe3 103
radext 33
raiarea 189
rpsec 78
rserpool 11
rtgarea 138
rtgwg 119
saag 152
sasl 39
shim6 242
sidr 96
sieve 22
simple 117
sip (two) 83
sip 189
sipping 162
sipping 70
smime 19
softwire 93
speermint 148
tcpm 42
techspec 39
tls 54
trill 101
tsvwg 55
v6ops 105
widex 11
xcon (one) 89
xcon 41