Ballot Details: OpenC2 Technical Committee - Standing Rule #1 (CLOSED)

Ballot Question Approve Standing Rule #1: Suspension of Standing Rules for the duration of the Meeting
Ballot Description In addition to the rules defined by the OASIS TC Process and Roberts Rule of Order, the OASIS OpenC2 Technical Committee has adopted a set of standing rules to facilitate the execution of the day-to-day business of the Technical committee.

Rule One;
SUSPENSION OF STANDING RULES FOR THE DURATION OF THE MEETING
1. The rules of OASIS or Roberts Rule of Order cannot be suspended as they are not standing rules and always apply.
2. During the course of a meeting, a standing rule may be suspended for the duration of a meeting. A motion to suspend a standing rule is not debatable and must be called to question immediately. The rule will be suspended if any of the following criteria are met;
i. By a vote of 2/3 majority of the voting members present without prior notice
ii. By a simple majority vote of the voting members present with prior notice
Ballot Options
VOTING CLOSED: Monday, 3 July 2017 @ 11:00 am EDT
Yes 18 100
No 0 0
Abstain 3
Open Date Monday, 26 June 2017 @ 11:00 am EDT
Close Date Monday, 3 July 2017 @ 11:00 am EDT
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 18
Eligible members who have voted 21 of 53 39.623%
Eligible members who have not voted 32 of 53 60.377%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 18 100%
No 0 0%
Abstain 3

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Andrenacci, Andrea Moviri SPA Yes 2017-07-03 07:02:00
* Athias, Jerome Individual Yes 2017-06-30 17:17:00
* Banghart, Stephen NIST Yes 2017-06-30 14:50:00
* Brule, Joe National Security Agency Yes 2017-06-27 12:05:00
* De Bernardi, Andrea Moviri SPA Yes 2017-07-01 07:11:00
* Fai, Joyce National Security Agency Yes 2017-06-26 20:38:00
* Farral, Travis Anomali Yes 2017-06-28 20:05:00
* Fitzgerald-McKay, Jessica National Security Agency Yes 2017-06-30 14:44:00
* Gudenius, Sr., Eric Nteligen, LLC Yes 2017-06-30 14:55:00
* Hagen, Stefan Individual Yes 2017-06-26 20:47:00
* Lemire, David G2 Yes 2017-06-27 16:03:00
* Maroney, Patrick Wapack Labs LLC Yes 2017-06-26 21:54:00
* Meck, James FireEye, Inc. Yes 2017-07-02 15:58:00
* Patrick, Paul FireEye, Inc. Yes 2017-06-30 17:44:00
* Pinto, Alex Individual Yes 2017-06-30 21:07:00
* Stueve, Gerald Fornetix Yes 2017-06-28 20:14:00 1
* Suarez, Natalie NC4 Yes 2017-06-30 20:12:00
* Yu, Sounil Bank of America Yes 2017-06-30 14:17:00
* Skeen, Duane Northrop Grumman Abstain 2017-06-30 14:40:00
* Thomson, Allan LookingGlass Abstain 2017-06-26 21:15:00
* Verma, Jyoti Cisco Systems Abstain 2017-06-30 20:37:00
* Boles, Phillip FireEye, Inc. --
* Cornell, Cody Swimlane, LLC --
* Darley, Trey New Context Services, Inc. --
* Darnell, David North American Energy Standards Board --
* Davidson, Mark NC4 --
* Everett, Alex University of North Carolina at Chapel Hill --
* Ginn, Jane Cyber Threat Intelligence Network, Inc. (C... --
* Goffin, Glen Lumeta Corporation --
* Gurney, John-Mark New Context Services, Inc. --
* Hadden, Allen IBM --
* Hasumi, Daichi NEC Corporation --
* Hunt, Christian New Context Services, Inc. --
* Jolly, John Syncurity --
* Jordan, Bret Symantec Corp. --
* Kakumaru, Takahiro NEC Corporation --
* Kemp, David National Security Agency --
* Kirillov, Ivan Mitre Corporation --
* Landfield, Kent McAfee --
* MacGregor, Scott McAfee --
* May, Andrew ViaSat --
* Moore, Sean Centripetal Networks --
* Ortiz, Efrain Symantec Corp. --
* Pendergast, Andrew ThreatConnect, Inc. --
* Ricard, Chris Financial Services Information Sharing and... --
* Riedel, Daniel New Context Services, Inc. --
* Rolls, Darran SailPoint Technologies --
* Romano, Jason National Security Agency --
* Satish, Sourabh Phantom --
* Sooter, Ben Electric Power Research Institute (EPRI) --
* Sparrell, Duncan sFractal Consulting LLC --
* Storms, Andrew New Context Services, Inc. --
* Waltermire, David NIST --

Voter Comments

Submitter Vote Comment
Stueve, Gerald
Fornetix		 Yes Modify prior notice to add sufficient lead time (i.e. at least 24 hours)