1. November 2013 802 EC Workshop Introduction
May 2011
doc.: IEEE /0051r2
November 2013
November EC Workshop Introduction
Date: xx
Authors:
Adrian Stephens, Intel Corporation
Adrian Stephens, Intel Corporation

2. November 2013
Introduction
This presentation provides an introduction to the November executive committee (EC) workshop.
Adrian Stephens, Intel Corporation

3. November 2013
Purpose
This workshop provides an opportunity to discuss matters relevant to the operation of the 802 LMSC in more depth than is possible at the 802 EC plenaries, which are dominated by routine matters.
Adrian Stephens, Intel Corporation

4. November 2013
Modus operandi - 1
I will keep to the agreed agenda timings. Near the end of each item I will look for action items and owners to progress any identified need for continued development.
Priority will be given to those who haven’t spoken on a topic.
If discussion turns into a head to head, with no progress being made, I will call “rat-hole” and move on to the next agenda item.
We are professionals – let’s run the meeting in an ordered manner. In particular speaking loudly over somebody else is not helpful. One conversation suffices.
Adrian Stephens, Intel Corporation

5. November 2013
Modus Operandi - 2
Adrian will display running notes written into a copy of the agenda during the meeting.
These notes will attempt to capture and highlight areas of agreement and areas where consensus has yet to be published in real time.
The notes will also capture action items.
This is a working document and there will be no attempt to make it pretty.
Adrian Stephens, Intel Corporation

6. Documents and confidentiality
November 2013
Documents and confidentiality
The agenda is an open document, on mentor.
This workshop is a closed meeting (i.e. is equivalent to an executive session), and may include sensitive (i.e., confidential) matters.
Input materials that are not confidential should be placed on mentor.
The workshop notes will be posted on the mentor server after redaction of any confidential material.
Therefore, it is important that members identify confidential material as we proceed so that it can be marked as such to guide redaction.
Adrian Stephens, Intel Corporation