should be have a wg meeting to discuss as3?
-----Original Message-----
From: wgchairs-admin@xxxxxxxx [mailto:wgchairs-admin@xxxxxxxx] On Behalf Of
agenda@xxxxxxxx
Sent: Tuesday, May 04, 2004 9:53 AM
To: wgchairs@xxxxxxxx; bofchairs@xxxxxxxx
Cc: agenda@xxxxxxxx
Subject: 60th IETF WG/BOF Scheduling
60th IETF - San Diego, CA, USA
Meeting Dates: August 1-6, 2004
We will be taking scheduling requests for ALL Working Groups and BOFs
starting today. The cut-off for requesting a slot is Monday, July 19 at
17:00 ET. The agenda for the Working Group is due by Monday, July 26 at
12:00 ET. Please submit scheduling request and the working group agenda to:
agenda@xxxxxxxxx
1. ALL scheduling requests must be sent to: agenda@xxxxxxxx with a copy to
the appropriate Area Director(s). Please include working group or BOF
acronym in Subject line.
2. BOFs will NOT be scheduled unless the Area Director(s) approved request
is accompanied by a BOF FULL NAME AND ACRONYM, AREA, CHAIRS NAME(s) (given
together with e-mail address(es)), AN AGENDA AND FULL DESCRIPTION as well as
the information requested in (4) below. Please read the BOF Procedure at:
http://www.ietf.org/meetings/1bof-procedures.txt before requesting a slot
for a BOF.
3. WORKING GROUPs will be allowed a maximum of TWO slots (second slot has to
be approved by AD). If your WG will need more than two slots, additional
slots will be assigned after agenda scheduling has closed on July 19 at
17:00 ET. If slots are available, you will need approval from the AREA
DIRECTOR(s). Should you need additional information on WG scheduling visit
the IETF Working Group guidelines at http://www.ietf.org/rfc/rfc2418.txt.
4. You MUST provide the following information before the meeting 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 59th IETF are at the end of this
message):
e. Special requests (i.e. multicast):
f. Number of slots:
g. Length of slot:
- 1 hour
- 2 hours
- 2 1/2 hours
============================================================
For your convenience please find here the list of the AREA Directors with
their e-mail addresses:
IETF Chair
Harald Alvestrand <Harald@xxxxxxxxxxxxx>
Applications Area (app)
Ted Hardie <hardie@xxxxxxxxxxxx>
Scott Hollenbeck <sah@xxxxxxxxxxxxxxx>
Internet Area (int)
Thomas Narten <narten@xxxxxxxxxx>
Margaret Wasserman <margaret.wasserman@xxxxxxxxx>
Operations & Management Area (ops)
David Kessens <david.kessens@xxxxxxxxx>
Bert Wijnen <bwijnen@xxxxxxxxxx>
Routing Area (rtg)
Bill Fenner <fenner@xxxxxxxxxxxxxxxx>
Alex Zinin <zinin@xxxxxxx>
Security Area (sec)
Steve Bellovin <smb@xxxxxxxxxxxxxxxx>
Russ Housley <housley@xxxxxxxxxxxx>
Sub-IP Area (sub)
Alex Zinin <zinin@xxxxxxx >
Bert Wijnen <bwijnen@xxxxxxxxxx>
Transport Area (tsv)
Allison Mankin <mankin@xxxxxxx>
Jon Peterson <jon.peterson@xxxxxxxxxxx>
===========================================================
59th IETF Meeting Attendance Number
aaa 130
apparea 62
avt 76
avt 67
calsch 16
capwap 137
ccamp 109
crisp 39
dccp 72
dhc 98
disman 38
dna 166
dnsop 76
eap 80
enum 89
forces 62
genarea 51
geopriv 54
grow 102
hipbof 122
hiprr-IRTF 97
hubmib 20
icar 39
idr 93
iea 68
iiri 38
inch 19
ipfix 56
ippm 64
ipv6 246
krbwg 34
l2vpn 136
l3vpn 225
ldapbis 15
lemonade 40
ltans 13
magma 100
manet 86
marid 105
mboned 53
midcom 78
mip4 75
mip6 232
mmusic 82
mobike 115
mobopts 144
mpls 131
multi6 116
nemo 177
netconf 80
newtrk 93
nfsv4 8
nsis 61
nsis 94
openpgp 30
opsarea 49
opsec 117
pana 75
pki4ipsec 68
pkix 49
pmtud 27
psamp 56
pwe3 96
rddp 10
rmonmib 20
rserpool 20
rtgarea
saag 91
sasl 51
simple 81
simple 27
sip 134
sipping 72
sipping 106
smime 47
speechsc 30
syslog 24
tsvwg 118
v6ops 174
v6ops 122
webdav 17
xcon 105
|
