FW: 61st IETF - WG/BOF Scheduling
"Romascanu, Dan \(Dan\)" <[email protected]>
| Newsgroups | gmane.ietf.hubmib |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F056B349E@is0004avexu1.global.avaya.com> |
Should we ask for a meeting slot at IETF-61? I personally hope that the EFM MIBs will be after the second last call, and delivered to the IESG by then. We have the new MAU MIB item in the Charter, We should see how controversial this is. Are there other items that would require a meeting slot? Regards, Dan -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of [email protected] Sent: 25 August, 2004 11:46 PM To: [email protected]; [email protected]; [email protected] Subject: 61st IETF - WG/BOF Scheduling 61st IETF - Washington, D.C, USA Meeting Dates: November 7-12, 2004 We will be taking scheduling requests for all Working Groups and BOFs starting today, August 25. The cut-off for requesting a slot is Monday, October 25 at 17:00 ET. The agenda for the Working Group is due by Monday, November 1 at 12:00 ET. Please submit scheduling request and the working group agenda to: [email protected]. PLEASE NOTE: Please include the acronym of the working group or BOF in the subject line of your request for scheduling and WG agenda. Also include all information requested in Item 4 below. 1. All scheduling requests must be sent to: [email protected] 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'S 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 (2) slots. If your WG will need more than two slots, additional slots will be assigned after agenda scheduling has closed on October 25 at 17:00 ET and with 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 working group 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 60th IETF are at the end of this message): e. Special requests (i.e. multicast, specific day of the week): 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 <[email protected]> Applications Area (app) Ted Hardie <[email protected]> Scott Hollenbeck <[email protected]> Internet Area (int) Thomas Narten <[email protected]> Margaret Wasserman <[email protected]> Operations & Management Area (ops) David Kessens <[email protected]> Bert Wijnen <[email protected]> Routing Area (rtg) Bill Fenner <[email protected]> Alex Zinin <[email protected]> Security Area (sec) Steve Bellovin <[email protected]> Russ Housley <[email protected]> Sub-IP Area (sub) Alex Zinin <[email protected] > Bert Wijnen <[email protected]> Transport Area (tsv) Allison Mankin <[email protected]> Jon Peterson <[email protected]> =========================================================== 60th IETF Meeting Attendance Number aaa - 90 apparea - 77 asrg - no roster atommib - 4 avt - 76 avt - 68 behave - 141 bfd - 74 bmwg - 21 calsch - 28 capwap - 96 ccamp - 118 crisp - 43 dccp - 71 dhc - 61 dna - 79 dnsext - 110 dnsext - 71 dnsop - 127 dtnrg - no roster eap - 87 enroll - 44 entmib - 6 enum - 84 forces - 35 genarea - 56 geopriv - 95 grow - 51 hip - 111 hiprg - 83 hubmib - 15 icar - 20 idr - 137 ieprep - 74 imapext - 25 imss - 14 inch - 20 ipcdn - 9 ipdvb - 27 ipfix - 41 ipoib - 16 ippm - 41 ips - 24 ipv6 - 241 ipvlx - 111 isis - 83 isms - 37 kitten - 82 krbwg - 40 l2vpn - 191 l3vpn - 145 ldapbis - 16 lemonade - 34 ltans - 29 magma - 80 manet - 113 marid - 107 marid - 142 mass - 128 mboned - 75 midcom - 71 mip4 - 93 mip6 - 135 mip6 - 214 mmusic - 84 mobike - 78 mobopts - 105 mpls - 184 msec - 75 multi6 - 161 nemo - 82 netconf - 69 netmod - 82 newtrk - 43 nfsv4 - 28 nsis - 101 nsis - 51 opes - 23 opsec - 92 ospf - 129 pana - 58 pce - 115 perm - 79 pim - 73 pki4ipsec - 63 pkix - 73 pmtud - 58 psamp - 43 pwe3 - 146 radext - 75 radext - 58 rddp - 36 rmonmib - 26 rmt - 42 rohc - 24 rpsec - 130 rrg - 141 rserpool - 29 rtgarea - 119 rtgwg - 125 saag - 127 sasl - 53 simple - 66 simple - 132 sip - 162 sip - 79 sipping - 174 sipping - 35 smime - 34 speechsc - 23 tcpm - 68 tsvwg - no roster urirev04 - 25 v6ops - 130 v6ops - 123 vrrp - 25 webdav - 13 xcon - 105 xcon - 15