Hi Folks, At this point, I think that we're wrapping things up and we will not need to meet in Minneapolis. I've gotten some comments back that the summary of syslog-syslog-03 is consistent with how things work in relays. (I would still like to get some comments back from people who have fully reviewed the ID. :-) We heard from John Kelsey in San Diego and discussed moving forward with syslog-sign. Everyone appears to be supportive of that and there were few comments made on the overall approach. John's next ID should be a synthesis of mostly syslog-sign with some good parts from syslog-auth, and will be on target for fulfilling the charter. We also heard from Darren New and Marshall Rose. Again, it looks like we have a solid proposal that fits the definition in the charter. Darren and Marshall are addressing the few comments made in a new ID that should be available in the next few days. I'll make one last review of syslog-syslog and then I'd like to try to get it submitted to the IESG around the early part of February. If things look good for the new revision of syslog-reliable, then I'd like to get that in the works as well with a similar timetable. If anyone has an overwhelming and burning desire to meet in Minneapolis, please send in your reasons and let's discuss them here in the list. Thanks, Chris (Replies to this will go to the WG list. If you want to reply to me separately, please send to [EMAIL PROTECTED] .) >To: [EMAIL PROTECTED], [EMAIL PROTECTED] >From: [EMAIL PROTECTED] >cc: [EMAIL PROTECTED] >Subject: 50th IETF WG/BOF Scheduling >Date: Wed, 10 Jan 2001 09:16:57 -0500 >Sender: [EMAIL PROTECTED] > >50th IETF in Minneapolis, MN >Meeting Dates: March 18 - 23, 2001 > >We will be taking scheduling requests for ALL Working Groups and BOFs starting today. >The cut-off for requesting a slot is Monday, February 26 at 5:00 PM ET. The agenda >for the Working Group is due by Tuesday, March 13 at 5:00 PM ET, please submit the >agenda to: >[EMAIL PROTECTED] > >1. ALL scheduling requests must be sent also to: [EMAIL PROTECTED] with a copy to the >appropriate Area Director(s). > >2. BOFs will not be scheduled unless the Area Director(s) approved request is >accompanied by a BOF NAME AND ACRONYM, AREA, CHAIRS NAME, AN AGENDA AND FULL >DESCRIPTION. >(Please read the BOF Procedure at ftp://ftp.ietf.org/ietf/1bof-procedures.txt before >requesting a slot for a BOF.) > >3. You MUST provide the following information before the meeting will be scheduled: > >a. Working Group or BOF name: > >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 49th 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 > >===================================================================== > >aaa - 173 >aaa - 126 >aaaarch - 59 >adslmib - 21 >apparea - 147 >atommib - 21 >avt - not received * >bmwg - 58 >calsch - 40 >ceot - 214 >cdnp - 195 >coma - 392 >c15n - 101 >deltav - 64 >dhc - 141 >diffserv - 525 >dnsext - 177 >dnsop 107 >domreg - 100 >enum -180 >fax - 40 >forces - 223 >frnetmib - 10 >gsmp - 81 >idn - 138 >idn - 166 >idmr - not received * >idr - 113 >idr - 152 >idwg - 89 >imapext - 33 >impp - 112 >impp - 160 >imxpbof - 89 >ipcdn - 38 >ipfc - 47 >ipngwg - not received * >ipo - not received * >ipoptr - not received * >ips - 194 >ipsec 309 >ipsp - 124 >isis - 238 >ispra - 193 >issll - 29 >iptel - not received * >itrace - 95 >kink - 174 >krbwg - 147 >l2tpext - 82 >ldapext - 81 >ldapbis - 54 >ldup - 80 >manet - 128 >manet - 128 >mboned - 91 >megaco - 213 >midcom - 136 >mmusic -207 >mmusic -29 >mobileip - 327 >mpls - 374 >mpls - 254 >msdp - 158 >msec - not received * >msgtrk - 37 >multi6 - 72 >nfsv4 - 47 >ngtrans - 197 >ngtrans - 185 >nntpext - 12 >opes - 101 >ospf - 167 >pim - 220 >pilc - 64 >pkix -199 >pkix - 150 >policy - not received * >pppext - 63 >ppvpn - 419 >prim - 232 >rap - 195 >rmonmib - 70 >rmt - 89 >rmt - 146 >rohc - 67 >rohc - 109 >rtgarea - 224 >rtfm2 - not received * >rserpool - 103 >saag - 212 >sacred - 147 >seamoby - 327 >secsh - 87 >sigtran - 183 >sigtran - 134 >simple - 175 >sip - 289 >sip - 155 >sls - 325 >smime - 90 >sming - 165 >snmpv3 - 98 >snmpconf - not received * >spirits - 104 >ssm - 149 >syslog - 82 >telsec - 31 >tewg - 386 >tls - not received * >tn3270e - not received * >trade - 25 >tsvwg - 183 >uswg - 16 >vpim - 25 >webdav - 46 >weird - 5 >whois - 69 >wrec - 148 >zeroconf - 171 > >* Blue Sheets were not received
