Re: [802SEC] +++EC Motion+++ Motion to Confirm Denis Kuwahara asVice-chair of 802.18--(open July30-close Aug 29th)
I have noticed that the LMSC rules are a little blurry regarding this
(1) On one hand, 5.1.2 says "LMSC Working Group Chairs and Vice
Chairs shall be elected by the Working Group..."
(2) On the other hand, 3.1b says: "The Chairs of Working Groups and
Technical Advisory Groups are confirmed or elected by the Working
Group and Technical Advisory Group members themselves."
So, in the case of the WG Chairs, the rules basically imply that
confirmation and election are both acceptable. While 3.1b doesn't
apply to Vice Chair, I think that, if confirmation is good enough for
picking a Chair, it ought be to OK for picking a Vice Chair.
P.S. Please don't ask me what "confirmation" would mean in the case
of WG Chair. I have no idea. And I certainly wouldn't recommend it.
>Unless 802.18 has its own approved procedures in place that
>contradict the 802 procedures I feel that I am forced to vote
>against this motion.
>> As Chair of 802.18, I appointed Denis to the position of Vice-chair,
> > and the membership of 802.18 unanimously affirmed that appointment.
>Our procedures say:
> LMSC Working Group Chairs and Vice Chairs shall be elected by the
>Working Group and
> confirmed by the LMSC Executive Committee.
>By my read of what has been put before me "appointed by the chair
>and affirmed by the membership" is not the same or even equivalent
>to "elected by the Working Group"
>This is no reflection whatsoever on Denis whom I would have been
>delighted to vote to confirm had his placement been done according
>If I am mistaken please point me to chapter and verse.
>At 11:26 AM 7/30/2003 -0400, Paul Nikolich wrote:
>>Reply-To: "Paul Nikolich" <firstname.lastname@example.org>
>>From: "Paul Nikolich" <email@example.com>
>>To: "IEEE802" <firstname.lastname@example.org>
>>Date: Wed, 30 Jul 2003 11:26:16 -0400
>>Subject: [802SEC] +++EC Motion+++
>> Motion to Confirm Denis Kuwahara as Vice-chair of 802.18--
>> (open July30-close Aug 29th)
>>Dear SEC members,
>>This is a 30 day SEC email ballot to make a determination by SEC motion to
>>confirm Denis Kuwahara as vice-chair of 802.18. See the specific motion
>>Moved by Carl Stevenson
>>Seconded by Stuart Kerry
>>The email ballot opens on Wednesday July 30th noon EDT and closes Friday
>>August 29th NOON EDT.
>>Please direct your responses to the SEC reflector with a CC directly to me
>>- Paul Nikolich
>>----- Original Message -----
>>From: "Stevenson, Carl R (Carl)" <email@example.com>
>>To: "802 SEC Reflector (E-mail)" <stds-802-SEC@ieee.org>
>>Cc: "802. 18 Reflector (E-mail)" <firstname.lastname@example.org>
>>Sent: Tuesday, July 29, 2003 2:48 PM
>>Subject: [802SEC] Motion to Confirm Denis Kuwahara as Vice-chair of 802.18
>>> Moved: Stevenson
>>> 2nd: Kerry
>>> To confirm Denis Kuwahara as Vice-chair of the IEEE 802.18 Radio
>>> Regulatory Technical Advisory Group.
>>> Information to Executive Committee Members:
>> > Denis has been an extremely active member of the 802.18 RR-TAG
>> > since its inception, and has been extremely helpful to the Chair,
>> > acting, in effect, as Vice-chair/Secretary "pro-tem" ... helping keep
>>> attendance, taking minutes, etc., greatly reducing the burden on
>>> me and helping the group to have effective, efficient meetings.
>>> Denis was also very active in the Regulatory Ad Hoc group that
>>> preceded the formation of 802.18, and has, thus, been a valued
>>> contributor for quite some time.
>>> As Chair of 802.18, I appointed Denis to the position of Vice-chair,
>>> and the membership of 802.18 unanimously affirmed that appointment.
>>> Thus, I urge the IEEE 802 Executive Committee to confirm Denis as
>>> the Vice-chair of 802.18.
>>> Paul, or designate, please initiate an Executive Committee e-mail ballot
>>> on this motion at your earliest convenience.
>>> Carl R. Stevenson
>>> Chair, IEEE 802.18 Radio Regulatory Technical Advisory Group
>>> 610-965-8799 (home office)
>>> 610-712-3217 (fax mailbox)
>>> 610-570-6168 (cellphone)
>>> Short Message Service: email@example.com