This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
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.
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.
p.s. note the shortened ballot header, in response to Pat's June request ...
SCC Type 2
Chair: Yu Yuan
Staff Liaison: Michael Kipness
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.