Hi Folks,
I just received the note below. I'd like to propose that we have a
1 hour meeting.
Agenda:
Discuss syslog ID 15 minutes
Discuss Alex's draft 45 minutes
I figure that we'll have talked enough about the syslog ID before we
get there so that it should just be some wrap-up at that time. Alex's
draft should be checked in by then and I hope that we'll have some
discussion in the mailing list before San Diego but I'll keep the
majority of time for that.
I'll also be looking to rope-in volunteers to write the 3rd part of all
of this - the event notification protocol that has verifiable delivery.
I'll also suggest that we not conflict with the following:
BEEP
IDWG
Any discussion on this?
Thanks,
Chris
>To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>From: [EMAIL PROTECTED]
>cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: 49th IETF WG/BOF Scheduling
>Date: Tue, 03 Oct 2000 11:04:19 -0400
>Sender: [EMAIL PROTECTED]
>
>Meeting Dates: December 10 - 15, 2000
>
>
>We will be taking scheduling requests for ALL Working Groups and
>BOFs starting today. The cut-off for requesting a slot is Friday,
>November 17 at 5:00 PM ET. The agenda for the working group is due by
>Monday, December 4 at 5:00 PM ET, please submit the agenda to:
> [EMAIL PROTECTED]
>BOF agendas are due at the time the request is made.
>
>If you cancel a scheduled working group session, please send a
>message to [EMAIL PROTECTED] as soon as possible. If you cancel a
>session once on site at the meeting, please inform someone at
>the IETF Registration Desk.
>
>With respect to working group and BOF requests, please note the
>following:
>
>1. All scheduling requests must be sent to the appropriate Area
> Director(s) with a copy to: [EMAIL PROTECTED]
>
> Applications: Patrik Faltstrom <[EMAIL PROTECTED]>
> Ned Freed <[EMAIL PROTECTED]>
> Internet: Thomas Narten <[EMAIL PROTECTED]>
> Eric Nordmark <[EMAIL PROTECTED]>
> Operations: Randy Bush <[EMAIL PROTECTED]>
> Bert Wijnen <[EMAIL PROTECTED]>
> Routing: Rob Coltun <[EMAIL PROTECTED]>
> Dave Oran <[EMAIL PROTECTED]>
> Security: Marcus Leech <[EMAIL PROTECTED]>
> Jeff Schiller <[EMAIL PROTECTED]>
> Transport: Scott Bradner <[EMAIL PROTECTED]>
> Allison Mankin <[EMAIL PROTECTED]>
> User Services: April Marine <[EMAIL PROTECTED]>
>
> All requests are subject to AD approval. You MUST provide the
> following information before the group will be scheduled:
>
> a. Working Group or BOF name. (Please read the BOF Procedure at
> ftp://ftp.ietf.org/ietf/1bof-procedures.txt
> before requesting a slot for a BOF.)
>
> 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 48th IETF are at the end
> of this message);
>
> e. Special requests. i.e., multicast (data projectors will be
> available in all meeting rooms)
>
>2. Tuesday will have one-hour sessions. If your working group or BOF
> needs to meet for one hour or less it will be scheduled on Tuesday.
> Please indicate on your request if you will need a one-hour session.
> Requests for two contiguous one-hour sessions will not be addressed
> until all one-hour requests have been accommodated.
>
>3. Working groups will be allowed a maximum of two slots. If your
> working group will need more, please let me know. Additional slots
> will be available after agenda scheduling has closed (currently
> November 17) and with approval from the AD.
>
>4. BOF's will not be scheduled unless the AD approved request is
> accompanied by a full description, BOF name and acronym,
> chairs name and an agenda.
>======================================================================
>aaa - 174
>aaaarch- 87
>adslmib - 17
>aft - 50
>apparea - 143
>avt - 170
>beep - 147
>bmwg - 46
>calsch - 31
>cnhttp - 57
>craps - 279
>deltav - 25
>dhc - 99
>diffserv - 453
>disman - 80
>dnsext - 128
>dnsop - 92
>ecm - 84
>enum - 224
>fax - 36
>frnetmib - 15
>grip - 40
>gsmp - 40
>idapbis - 85
>idmr - 179
>idn - 104
>idn - 36
>idn - 70
>idn - 86
>idwg - 86
>ieps -153
>imapext - 29
>impp - 224
>ipcdn - 18
>ipfc - 38
>ipngwg - 336
>ipo - 409
>ipobt - 269
>ipp - 20
>ippm - 194
>ips - 158
>ipsec - 188
>ipsp - 126
>iptel - 197
>isis - 107
>ispra - 140
>kkmp - 89
>krb-wg - 79
>l2tpext - 97
>ldapext - 89
>ldup - 62
>manet - 130
>mboned - 104
>megaco - 120
>mmusic - 171
>mobile ip - 223
>mobileip - 337
>mpls - 324
>mpls - 371
>msdp - 92
>msgtrk - 29
>nat - 104
>nbvpn - 248
>nfsv4 - 27
>ngtrans - 193
>nim - 133
>nntpext - 14
>opsarea - 105
>ospf - 130
>pilc - 157
>pim - 204
>pkix - 184
>policy - 293
>rap - 283
>rmonmib - 71
>rmt - 204
>rspool - 90
>rtgarea - 312
>saag - 108
>saag - 117
>sacred - 112
>secsh - 70
>sgm - 227
>sigtran - 183
>sin - 188
>sip - 288
>sip - 193
>smime - 131
>snmpconf - 184
>snmpv3 - 71
>spatial - 130
>spirits - 110
>ssm - 190
>stime - 67
>tewg - 334
>tls - 162
>trade - 57
>tsvwg - 110
>uswg - 17
>vpim - 88
>webdav - 20
>wrec - 64
>xmldsig - 66
>zeroconf - 180
