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

Elections in March 2000

The following notice describes the IEEE 802 Executive Committee election
process to occur at the March 2000 Plenary Meeting based on the Operating
Rules and past experience (these are the same procedures used in March

Current Working Group Chairs should announce to their Working Groups that
normal two-year elections are being held per the operating rules, inform the
Working Group if they wish to be considered as a candidate for re-election
and solicit new candidates. A formal election, within the Working Group
should occur during the week and a statement on the Working Groups selection
for Chair and Vice Chair(s) be reported to the SEC on Thursday evening.

Each Working Group should also elect a Vice Chair or Vice Chair(s), and in
some cases where the Working Group chair will be departing after the March
2002 elections (because of the ten year rule), this election may have
stronger significance than normal. A Working Group may have more than one
Vice Chair, if circumstances warrant and to provide more leadership

Candidates for IEEE 802 LMSC Chair should notify Howard Frazier, the
recording secretary by Monday morning, 8March98, in order that the process
proceed smoothly in an open manner.

Responsibilities of the IEEE 802 LMSC chair and appointed positions are
copied below.

I wish to continue to seek the LMSC Chair position and am announcing myself
as a candidate for re-election. All current appointed members of the SEC
have agreed to serve an additional term.

The reporting of WG chair elections to the SEC will take place at the
Thursday meeting as the first item under "Motions, Internal"(MI). If there
are new WG chairs, they will take office after the WG chair election report
at the start of the Thursday Plenary Meeting.

The election of LMSC chair will then take place followed by the appointment
and confirmation of appointed officers immediately following WG chair
election. If a new IEEE 802 Chair is elected, I propose that we delay the
affirmation of the appointed members until the following meeting to provide
for adequate review.

It is expected that all WG/TAG Chairs broadcast this messages to the members
of their respective groups with appropriate comments as needed.

Jim Carlo( Cellular:1-214-693-1776 Voice&Fax:1-214-853-5274
TI Fellow, Networking Standards at Texas Instruments
Chair, ISO/IEC JTC1/SC6 Telecom and Info Exchange Between Systems
Chair, IEEE802 LAN/MAN Standards Committee


1. Fulfill Duties as Outlined in LMSC Operating Rules

2. Obligations to Computer Society
  (a) Attend CS Standards Activities Board meetings as LMSC Chair (two
face-to-face, nominally three telecons)
  (b) Represent LMSC views and needs
  (c) Guide/facilitate healthy evolution of SAB projects and practices
  (d) Produce summary reports on LMSC activities, three times a year
  (e) Generate LMSC Annual Report:  past year highlights, next year target
goals, summary overviews, major changes, etc.

3. Obligations to LMSC Beyond Explicit Dutied Identified in OP Rules
  (a) Sign and, in many cases, draft/author/edit official communications to
external organizations (eg.  RES 10, FCC, DAVIC, ITU-T...nominally 15-20
documents per year, but growing)
  (b) Review and sign-off on Sponsor Ballot lists generated by Piscataway
  (c) Review and sign-off on PAR submissions, send to SAB and IEEE
  (d) Facilitate generation of LMSC agenda with significant help from the
recording secretary, finalize agenda for Thursday executive meeting
  (e) Review with the recording secretary, all LMSC actions items Friday

4   Plenary Meeting Facilitation:
  (a) On-call entire week to coach/mentor/facilitate resolution of issues
and guide actions toward LMSC win-win results (usually 10-20 hours, 5-10 key
projects).  [This limits one's freedom to attend WG meetings for more than a
few hours)
  (b) Act as liaison with IEEE Standards staff (at meeting and in
Piscataway) on working issues/projects (usually 5-10 hours per Plenary
  (c) Lead ad hoc activities as needed, usually one or two per Plenary

5.  Inter-Meeting Activities:
  (a) Follow-up on items in (3) above
  (b) Work with IEEE staff on issue resolution (eg.  Sponsor Ballot process,
SPAsystem directions/policy)
  (e) Respond to calls from the press, obtain approval of LMSC press
releases from CS SAB etc
  (f) Respond to NesCom and RevCom concerns on behalf of LMSC PARs and draft
standard reviews (if needed beyond WG chair actions)
  (g) Monitor JTC 1 actions affecting 8802 series of standards.

General Notes:
There are tremendous variations in the level of time/resources needed to
support LMSC.  There is a somewhat constant level of 20 hours per month
(average) to do the various items identified above.  There are also actions
that demand attention whenever they occur, ranging from big issues that take
100+% of one's time because of the magnitude of the issue, or the volume of
communications.  Fortunately, the latter events are infrequent but they can
consume full-time effort from two to ten days.

There is another level of activity that has tremendous advantages for LMSC
at the same time it consumes substantial resources.  From time-to-time the
opportunity arises for LMSC spokespersons to speak at conference and
seminars.  One could make this a full-time job (not really), or ignore it.
Experience indicates that good/valuable opportunities arise about every two
years to make a major presentation at some national or international meeting
(eg.  MoMuC, Waseda University, 12/93, one-hour overview of all LMSC
projects).  It is my opinion that we should do more of this on a coordinated
basis to spread the word, build further interest, gain added commitments to
LMSC programs.

1.  To stand in for the Chair when needed.  This is sometimes just a few
minutes at the executive committee meetins.  Other times it means chairing a
whole Plenary meeting.  In the latter case, there are a couple of weeks'
worth of work in the 4-6 weeks before the Plenary meeting, and 100%
consumption of one's time during the meeting.

2.  Chair rules change activities.  When major issues are being addressed
this can consume significant amounts of time, occasionally precluding
meaningful participation in a working group.

3.  Be expert on process and Roberts Rules of Order to help resolve issues
in EC meetings and, when asked, at WG/TAG meetings.

4.  Visit all WG meetings for short intervals during the Plenary week to
keep abreast of the pulse of the organization.

5.  Interpret the LMSC Operating Rules and provide advice to LMSC members,
WG chairs, and other executive committee members when requested.  This also
requires the VC to have in-depth knowledge of the policies and procedures of
the Computer Society SAB, and the IEEE Standards Board.

6.  Present LMSC introductory information at each opening Plenary session.

7.  Assist Chair with administrative and other assigned tasks.


Required Core Responsibilities:
1.  Records minutes of executive committee meetings (ie. four-hour Monday
session and five-hour Thursday session, at each of three plenary sessions
per year).
2.  Draft, produce, distribute executive committee minutes to committee
members and liaisons (nominally 40 people) (30-40 days after meeting).
3.  Maintain official records of minutes for historical purposes.
4.  Generate agenda for executive committee meetings.
5.  Edits and coordinates press releases with Computer Society

Additional Responsibilities (desired, could be given to others);
1.  Maintain assignment lists (P802 decisions)
     (a) Liaisons
     (b) OUIs
     (c) LSAPs

2.  Maintain archival records for:
     (a) Functional requirements, document revisions
     (b) Operating Rules document revisions
     (c) 802.0 Guidelines/Practices
     (d) PARs approved, revised, completed, withdrawn, etc.

3.  Keep informal records of Monday pm and Friday pm Plenary

4.  Condut 802.0 ballots

Not now part of Recording Secretary's responsibilities, though they have
been dne in the past by this office:

1.  Plenary presentation of 802 overview
2.  LMSC database management/coordination

1. Establishment and Maintenance of Accounts
    (a) credit card companies, (AmEX, Discover, VISA/MC)
    (b) bank account
          (i)    checking account
          (ii)   credit card charge processing
    (c) vendor accounts (one currently:  Zenith Maint)

2. Prepare Budget
    (a) annual CS SAB submissin
    (b) periodic recommentations/justification for meeting fee changes

3. Collect and Disburse Money
     (a) establish money handling procedures for meeting registration staff
           (i)    check and travelers check endorsement
           (ii)   credit card processing
           (iii)  temporary storage of receipts
           (iv)   daily cash-out
     (b) credit card desposit transactions (one or two per meeting day)
     (c) void/adjusted credit card transactions (one to three per meeting
     (d) storage of cash/check/etc during plenary meeting
     (e) preparation of deposits (deposit execution)
     (f) review of vendor invoices (CCI, hotel master account, A/V, etc)
     (g) expense reimbursement payments (executive committee member between
         meeting expenses, items specifically approved by executive
     (h) deadbeat collections.

4. Reports
    (a) statement of operations, balance sheet
          (i)   accounting period (meeting and following interval) at
                Monday executive committee and plenary
          (ii)  estimated statements at closing executive committee
                and plenary meetings
     (b) reports of expenses to Computer Society
     (c) deadbeat report (recommendations for removal of voting rights
         when needed)

5. Capital Equipment
    (a) maintain records of owned equipment and assigned custodians
    (b) procure equipment approved by executive committee

6. Reprogram credit card transaction terminal for each meeting

7. Maintain files of all financial transactions (database and journal

1. Existing PC based programs are quite comprehensive and thought to be
    useful for the next few years.
2. Pre-registration automation mechanisms are to be further encouraged.
3. The potential for IEEE CS assistance remains a possibility.


1. 802 Plenary Meetings:  Facilities and Services
    (a) oversee activities related to meeting facilities and services
    (b) ensure first-rate facilities and pricing
    (c) review and approve all decisions involving 802 funds for  meetings
    (d) present unusual expenditures to executive committee for approval
    (e) assist in identification of future site choices/locations
    (f)  tabulate site choice selections and maintain calendar for plenary
    (g) maintain Conference Guidelines for solicitation of hotel proposals
    (h) review hotel proposals for correctness and conformance to
    (i)  present summary of hotel options to executive committee and sign
          approval proposal on behalf of 802
    (j)  coordinate with CSP and LMSC Chair on major decisions

2. IEEE 802 Registration Database
    (a) responsible for database maintenance
    (b) oversee conference service staff on updates and additions
    (c) assure adequate backups and loss/corruption of data

3. 802 Document List
    (a) oversee maintenance and distribution of IEEE (Stds) documents
    (b) ensure collection of draft standards for distribution service at end
of meeting
    (c) maintain backup copy of draft standards documents as required

4. Assist 802 Treasurer
    (a) review of expenditures and future budget preparations
    (b) identify meeting deadbeats and report to treasurer for collection

5. Conference Service Provider (CSP)
     (a) maintain document on CSP duties
     (b) oversee CSP performance at meetings
     (c) serve as primary resource for planning and problem resolution both
           at meetings and between as necessary
     (d) participate in letter of agreement between 802 and CSP
     (e) present summary recommendations on future CSP contracts to
executive committee
     (f) execute (sign) approved CSP agreement on behalf of 802