| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
We could consider adding provision to a future version of the P&P to allow calling a teleconference meeting on an urgent topic with less notice, perhaps with a majority or 2/3 email vote. That won’t help us now. A rule in the P&P can be suspended if the P&P explicitly states the conditions where that is allowed.
Pat
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Pat Thaler
Sent: Monday, April 22, 2013 6:53 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Motion to Suspend the Rules to enable 802 EC telecon meeting Tuesday 30 April noon-12:30pm ET
Removing some of the old messages in the thread because my response are being sent to the moderator.
From: Pat Thaler
Sent: Monday, April 22, 2013 6:51 PM
To: 'Paul Nikolich'; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: RE: Re[2]: [802SEC] Motion to Suspend the Rules to enable 802 EC telecon meeting Tuesday 30 April noon-12:30pm ET
Dear Paul,
I do not recall exactly when it was discussed before. It was during the time when Matt and I were vice-chairs because I remember him participating in the discussion. The rationale was that the P&P is the highest IEEE 802 specific rules document and therefore are equivalent to our charter, constitution or bylaws and therefore not subject to suspension. One could also now make the argument that the P&P require approval by AudCom to go into effect. A suspension of them by a vote of the EC wouldn’t have approval by the body that had to approve the P&P. If we can’t approve something by ourselves, I don’t think we can suspend it. (The discussion I recall probably happened before AudCom approval was required because I remember the point being made when we were dividing the old P&P into a P&P and an OM that the division would allow us to vote to suspend OM rules).
The previous version of our P&P, i.e. the one from 2010, did not have the meeting notice requirement. Therefore when that was in effect the Chair’s Guideline 2.12 was valid. The Chair’s guidelines are subsidiary to our P&P. Therefore, they cannot contradict or override a requirement in the P&P. The IEEE 802 P&P adopted on December 5, 2012 added the notice requirement that Geoff quoted below. When that was approved, Chair’s guideline 2.12 became invalid because it conflicted with the P&P.
Regards,
Pat
From: Paul Nikolich [mailto:paul.nikolich@att.net]
Sent: Monday, April 22, 2013 6:22 PM
To: Pat Thaler; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re[2]: [802SEC] Motion to Suspend the Rules to enable 802 EC telecon meeting Tuesday 30 April noon-12:30pm ET
Pat,
Do you recall when it was concluded the P&P were equivalent to bylaws and what the rationale was that led to that conclusion? This is an important point that I would like clarification on.
Regarding the approval threshold, I agree a 2/3 vote is appropriate.
By the way, I forgot that we have in the Chair's guideline 2.12 IEEE 802 EC Interim telecon meetings the following text:
7. Urgent EC Teleconference Meeting Exception:
On rare occasions, there may be a need for an Urgent EC Meeting by teleconference to address
unexpected circumstances that require a quick response. If the Sponsor Chair decides an urgent EC
meeting is in order, the notification requirement may be as little as 24 hours
I would be willing to invoke the Chair's Guideline in this instance, but only if there are no objections.
Regards,
--Paul
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.