Re: [802SEC] RE: 2005 Meeting of 802 and IEEE-SASB
For those of us such as Paul Nikolich, Geoff Thompson, Mark Klerer, Matt
Sherman
and myself who are very active in both 802 and the StB committees,
overlapping
the meetings in the middle of the week would definitely be suboptimal.
While I can't
anticipate exactly what our duties will be in March, 2005, it is a
pretty fair guess
that we would be unable to carry out our duties in both 802 and the StB
if the meetings
overlap.
When we met in Hilton Head in 2001, things were a little different. We
were still
holding the closing session of the 802 SEC on Thursday evening in those
days,
so the overlap between 802 and the StB committee meetings was minimal.
It was
a fairly brutal week for yours truly (I was the SEC Recording Sec'y, the
chair of
the EFM Study Group, the chair of RevCom, and a member of the StB at the
time),
but it did seem to work out well for most of the rest of the crowd.
My humble suggestion would be as follows (he said slipping into his MOP
gear):
1) As a one time only deal, hold the closing SEC meeting in March, 2005 from
7:00 pm to midnight on Thursday, March 17 (just like the bad old days).
2) Start the StB committee meetings on Friday, March 18, continuing on
Saturday ,
March 19.
3) Hold the StB meeting on Sunday, March 20.
With two years to plan for it, I think that 802 could handle the
challenge of
returning to the Thursday evening format as a one time only event. If
this is
just too obnoxious for 802, then as a compromise I would suggest overlapping
the StB committee meetings (ProCom, PatCom, AudCom) with the closing
802 WG meetings and the closing 802 SEC meetings on Friday. The remainder
of the StB committee meetings (NesCom, RevCom, AdCom) would then take
place on Saturday and and the StB meeting could be held on Sunday.
We're still TBD on the venue for March, 2005, right? Can I put in a pitch
for Vancouver? Great skiing at Whistler/Blackcomb that time of year. I
think
that dot3 is pretty close to proposing that we hold ALL of our future
meetings
in Vancouver, given our past success in that city.
Howard
Rigsbee, Everett O wrote:
>Rona, Thanx for your quick response. I do have concerns that trying to schedule Stds Board meetings during the middle of our Plenary week will create serious scheduling problems for our members who would normally participate in those meetings. The last time we did a joint meeting (Hilton Head, SC,) the Stds Boards committees met on Thursday and Friday and the Stds Board met on Saturday, which helped to reduce the number of meeting conflicts.
>
>I'm inviting other members of the 802 SEC to provide feedback on this proposal to assess their level of concerns. We would ideally like the two sessions to complement one another rather than to overlap in conflicts.
>
>Thanx, Buzz
>Dr. Everett O. (Buzz) Rigsbee
>Boeing - SSG
>PO Box 3707, M/S: 7M-FM
>Seattle, WA 98124-2207
>(425) 865-2443 Fx: (425) 865-6721
>everett.o.rigsbee@boeing.com
>
>
>-----Original Message-----
>From: r.gertz@ieee.org [mailto:r.gertz@ieee.org]
>Sent: Tuesday, April 01, 2003 9:41 AM
>To: Rigsbee, Everett O
>Cc: t.steenweg@ieee.org
>Subject: 2005 Meeting of 802 and IEEE-SASB
>
>Hi Buzz:
>
>I have had a conversation with Karen Rup and Terry deCourcelle regarding
>the 2005 March meeting of the 802 Plenary. Karen has asked me to
>coordinate the details.
>
>The IEEE-SA Standards Board and Committee members and staff would very much
>like to again meet during your series, and staff is requesting the dates of
>March 15-17 (Tuesday - Thursday) for the Standards Board and Committee
>meetings. These dates will be the most favorable for our needs. Terry
>Steenweg, our meeting coordinator, will forward our meeting and sleeping
>room requirements to you and Dawn after you advise if these dates are
>agreeable with you.
>
>Thank you for your consideration.
>
>Best regards,
>Rona
>_______________________________
>Rona I. Gertz
>Manager, IEEE-SA Governance
>IEEE Standards Activities
>r.gertz@ieee.org
>+1 732 562 3808 (phone); +1 732 562 1571 (fax)
>IEEE Standards web site:http://standards.ieee.org/
>
>
>