Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] 802 Chair/Tresurer response to SASB: 11 June 2015 SASB Resolution



Nancy

The rules state that it ends no later than 10:30 am. Ending at 10:15 am is no later than 10:30 am.

The rules are the rules. We have ways to change them. I am just relaying what the rules say.

James Gilb

On 06/24/2015 05:10 AM, Nancy Bravin wrote:
James,

So the original email from Paul asking to go past the 10 scheduled stop time prevents him from doing so per your statement below?
I had assumed that Pat’s interpretation, which is usually correct, and deals with common sense as well, is both what is reasonable to most EC folks when extra time is needed by voting on it?
  IMHO people are more important than rules when issues are at hand and people together. Does that mean that Paul can’t extend the time either
under any circumstances and the P&P which is how the group prefers to work by timely needs, first by agreement, is less important than a rule? Roberts or otherwise as a side note?
Maybe that interpretation needs to change or the rule?

Sincerely, Nancy
On Jun 23, 2015, at 11:32 AM, James P. K. Gilb <gilb@ieee.org> wrote:

Pat

We cannot as it states in section 1 of the OM: "Unless otherwise stated, none of the rules or requirements in this Operations Manual (OM) may be suspended by vote of the Sponsor as would otherwise be allowed by Robert's Rules of Order Newly Revised (latest edition)."

Clause 4, nor its subclauses, have text indicating that it can be suspended.   Subclauses 5.1.2, 8.1 (and subsidiary), and 8.2 (and subsidiary) can be suspended by 2/3 vote.

James Gilb

On 06/22/2015 12:31 PM, Pat (Patricia) Thaler wrote:
Since it is in the OM, not the bylaws (i.e.the P&P) we could vote to suspend the rule.
That said, I'd rather not start early.

-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of James P. K. Gilb
Sent: Monday, June 22, 2015 11:21 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] 802 Chair/Tresurer response to SASB: 11 June 2015 SASB Resolution

Bob

In the current OM, 4.1.4 Procedurefor limiting the length of the IEEE
802 sponsor meetings

"d) The opening Sponsor meeting shall start at 8:00 a.m. and end no
later than 10:30 a.m. on Monday morning and the closing Sponsor meeting
shall start at 1:00 p.m. and shall end no later than 6:00 p.m. on Friday
of the plenary session."

So, while we can end early, we can't start at any time other than 8:00 am.

James Gilb

On 06/22/2015 10:18 AM, Bob Heile wrote:
Paul

Would it be possible to consider starting the EC meeting15 minutes
early? Then we could end on time (or even early maybe)

Bob

At 07:56 PM 6/14/2015 +0000, Paul Nikolich wrote:
Dear EC members,

This weekend Clint and I worked on a response to the draft resolution
and sent to the SASB Chair and Treasurer for review and acceptance, it
is the [bracketed highlighted text] in the attached document.  I will
place an item on the opening EC agenda for discussion of the issue at
the upcoming 802 plenary session.  My preference is not to have an
executive session. However if one is required, I suggest we reserve
the last 15 minutes of the opening EC meeting for it, with the
understanding we may need to go a little past (later than 10:15) the
10AM scheduled end-of-meeting time, depending on how quickly we make
it through the earlier agenda items.

Regards,

--Paul

------ Original Message ------
From: "Stephens, Adrian P"
<<mailto:Adrian.P.Stephens@intel.com>Adrian.P.Stephens@intel.com>
To: <mailto:STDS-802-SEC@listserv.ieee.org>STDS-802-SEC@listserv.ieee.org
Sent: 6/13/2015 1:59:29 AM
Subject: [802SEC] Resolution from IEEE-SA Standards Board re financial
reporting

Dear EC members,



The SASB met this week and produced a resolution as shown below,  on
the failure of the LMSC to provide its

financial reports in a timely manner.   802 EC members were excluded
from the meeting that approved this resolution,

although we (Paul, Clint, Steve, Jon, Andrew, …) were present for
some of the discussion,  up to the point where they

realized they should deem us conflicted.



I believe being cited by the SASB as failing in our duty warrants an
agenda item in the EC to discuss corrective actions,

and this item may need to be held in executive session.   I therefore
ask for such an item to go on the agenda at some time

during the week.



The resolution is at:
<http://standards.ieee.org/about/sasb/resolutions.html>http://standards.ieee.org/about/sasb/resolutions.html


and states:

IEEE-SA STANDARDS BOARD RESOLUTIONS

11 June 2015

Resolved that,

The IEEE 802 LAN/MAN Standards Committee (LMSC) has failed in its
duty as a Sponsor to complete the 2014 LMSC annual financial report
in a timely manner. Therefore, the following corrective actions are
approved by the SASB:

1.     IEEE-SA staff is instructed to set up requested departments in
NetSuite and to keep the NetSuite database unlocked until Wednesday,
17 June 2015.

2.     The LMSC Chair and the LMSC Treasurer shall complete the 2014
LMSC annual financial report and certify that the reported financial
data is materially correct on or before Wednesday, 17 June 2015. All
audit material shall be made available to the auditors by 30 June 2015.

3.     The LMSC Chair and the LMSC Treasurer are instructed to
provide a plan to meet the schedule shown in item 4. This plan shall
be submitted by 30 June 2015 and shall be acceptable to IEEE-SA staff
and IEEE-SA Treasurer.

4.     After completing the 2014 LMSC financial reporting as outlined
in item 2 above, the 2015 LMSC financial data shall be entered in
NetSuite with the following timeline:

o    For Q1 and Q2 2015, the financial data of LMSC shall be
submitted through NetSuite by 31 July 2015 and 31 August 2015
respectively;

o    For Q3 2015, the financial data of LMSC shall be submitted
through NetSuite by 15 November 2015;

o    For Q4 2015, the financial data of LMSC shall be submitted
through NetSuite by 15 February 2016.

o    Complete certified 2015 financial data for LMSC shall be
available in NetSuite no later than 15 February 2016.

5.     If the SASB determines that the LMSC Chair and the LMSC
Treasurer have failed to satisfactorily execute their duties for the
2014 and/or 2015 LMSC annual financial reporting per the schedule
outlined above, the SASB reserves the right to pursue any and all
additional actions that it deems necessary to bring the LMSC annual
financial reporting into compliance with its operating procedures.
Such actions may include removal of specific LMSC Officers and/or
suspension of all LMSC Sponsor activities (potentially including, but
not limited to, new and modified PAR approvals, Sponsor balloting,
approval of standards, meetings, etc.) as described in IEEE-SA
Standards Board Operations Manual 5.3.6.









Best Regards,



Adrian P STEPHENS



Tel: +44 (1793) 404825 (office)
Tel: +1 (971) 330 6025 (mobile)



----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47


---------- 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.
Content-Disposition: attachment; filename="802 Chair and Treasurer 14
June 2015 response to 11 June"
  2015 SASB resolution.pdf"
Content-Type: application/pdf; name="802 Chair and Treasurer 14 June
2015 response to 11"
  June 2015 SASB resolution.pdf"


Bob Heile, Ph.D

Director of Standards, Wi-SUN Alliance
Chair, IEEE 802.15 Working Group on Wireless Specialty Networks
Chair IEEE 2030.5 Working Group for Smart Energy Profile 2
Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications

11 Robert Toner Blvd, Suite 5-301
North Attleboro, MA  02763   USA
Mobile: +1-781-929-4832
email:   bheile@ieee.org

----------
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.


----------
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.