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

Re: [802SEC] interim tally +++EC Ballot+++ 802 LMSC and SCC 42 Transportation liaison agreement



Paul,

Glitches do happen. No harm done.

Best regards,

Mike

Sent from my Windows 8.1 Phone

From: Paul Nikolich
Sent: ‎7/‎27/‎2015 18:37
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] interim tally +++EC Ballot+++ 802 LMSC and SCC 42 Transportation liaison agreement

 Dear EC members,
 
One of our eagle-eyed colleagues noted an typo in the motion text that specified the attached document, it should be SCC42-2015-A001, not SCC41-2015-A001.  My apologies for the error.  Since the document attached to the email in which the motion was made is SCC42-2015-A001, I consider your approval votes to apply that document.
 
Regards,
 
--Paul
 
------ Original Message ------
From: "Paul Nikolich" <paul.nikolich@att.net>
Sent: 7/27/2015 10:33:30 AM
Subject: [802SEC] interim tally +++EC Ballot+++ 802 LMSC and SCC 42 Transportation liaison agreement
Dear EC members,
 
The interim tally for the below motion is 12 approve, 0 disapprove, 0 abstain, 4 did- not-vote (DNV).
 
Thanks to all that quickly responded. I will hold the ballot open for a few more days to allow the DNVs to cast their votes.
 
Regards,
 
--Paul
 
Interim tally:
Voting:
1) Thaler- approve
2) Gilb- dnv
3) Rosdahl-approve
4) D'Ambrosia- approve
5) Chaplin- approve
6) Parsons- dnv
7) Law- approve
8) Stephens-approve
9) Heile-approve
10) Marks-approve
11) Lynch-approve
12) Shellhammer- dnv
13) Das- approve
14) Mody-approve
15) Godfrey-approve
16) Nikolich- dnv-votes only to break tie (9 approves needed to pass, >1/2 of EC voting members )
Non-voting:
1) Thompson
2) Lemon
3) Canchi
4) Zuniga
 
------ Original Message ------
From: "Paul Nikolich" <paul.nikolich@att.net>
Sent: 7/24/2015 6:06:25 PM
Subject: [802SEC] +++EC Ballot+++ Approve sponsor liaison agreement between 802 LMSC and SCC 42 Transportation
Dear EC members,
 
Last week I forgot to get EC approval on establishing an bi-directional liaison between 802 and SCC 42 Transportation (see below for details on SCC42), hence I will be conducting an EC email ballot. Attached is the liaison agreement I sent to the EC in early June, revised to address Bob Grow's comments/concerns. This agreement will provide full access into each other's works in progress (i.e., drafts). Furthermore, I would like you to consider nominating someone to be the SCC42 liaison representative.
 
Motion
======
 
The EC supports the attached SCC41-2015-A001 Sponsor Liaison Agreement, with editorial changes as deemed necessary.
 
Move: James Gilb
Second: Pat Thaler
 
Start of ballot: Friday 24th July
Close of ballot: Sunday 2nd August, 11:59PM AOE
 
Early close: As required in subclause 4.1.2 'Voting rules' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Operations Manual, this is notice that, to ensure the release is provided in a timely manner, this ballot may close early once sufficient responses are received to clearly decide a matter.
Sufficient responses to clearly decide this matter will be based on the required majority for a motion under subclause 7.1.1 'Actions requiring approval by a majority vote' item (h), 'Other motions brought to the floor by members (when deemed in order by the Sponsor Chair)' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Policies and Procedures.
Regards,
 
Regards,
 
--Paul
 
p.s. note the shortened ballot header, in response to Pat's June request ...
 
 
 
SCC42 Transportation
SCC Type 2
Chair: Yu Yuan <mailto:y.yuan@ieee.org>
Staff Liaison: Michael Kipness <mailto:m.kipness@ieee.org>
Leads the coordination of IEEE standardization activities for technologies related to transportation, especially in the areas of connected vehicles, autonomous/automated vehicles, inter- and intra-vehicle communications, and other types of transportation electrification. These technologies include but are not limited to Mobile Apps, Sensor Networks, and Communications that allow human to vehicle, vehicle to vehicle, vehicle to infrastructure, vehicle to platform, and vehicle to everything exchange of information and data. Where standardization needs exist, the SCC will develop guides, recommended practices, standards, and common definitions of terms.
---------- 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.