Ballot Details: Approve OpenC2 Stateless Packet Filtering Actuator Profile, v1.0, WD07 as CSD and for public review (CLOSED)

Ballot Question Do you approve the OpenC2 Profile for Stateless Packet Filtering v1.0 Working Draft (WD) 07 and all associated artifacts as Committee Specification Draft 06, and its release for public review?
Ballot Description WD 07 was posted to OASIS on 14 May 2019. The co-chairs of the Actuator Profiles Subcommittee have determined that general consensus has been reached on the resolution of all comments to the CSD 05 / PRD 02 version received during the second public review and presented it to the Technical Committee’s co-chairs.

In accordance with the OpenC2 Technical Committee’s Standing Rule 5, the co-chairs submit this ballot to the Technical Committee to authorize the release of the working draft and all associated artifacts for a third public review.

Per the guidance adopted at the October 2018 TC meeting, approval of this ballot includes approval for the Co-Chairs and Editors to work with OASIS staff make any changes necessary to prepare this document for Public Review.

Public document link: https://www.oasis-open.org/committees/document.php?document_id=65307&wg_abbrev=openc2

The Markdown (MD) version of the specification will be designated as authoritative. OASIS will be requested to conduct the third public review of all three OpenC2 specifications concurrently.

This ballot requires a majority vote of the TC's voting members.
Ballot Options
VOTING CLOSED: Tuesday, 21 May 2019 @ 12:00 pm EDT
Yes 24 100
No 0 0
Open Date Tuesday, 14 May 2019 @ 4:00 pm EDT
Close Date Tuesday, 21 May 2019 @ 12:00 pm EDT
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 24
Eligible members who have voted 24 of 33 72.727%
Eligible members who have not voted 9 of 33 27.273%

Voting Summary by Option

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

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Barry, Michelle AT&T Yes 2019-05-15 15:22:00
* Berliner, Brian Symantec Corp. Yes 2019-05-20 22:28:00 1
* Brule, Joe National Security Agency Yes 2019-05-14 20:24:00
* Considine, Toby University of North Carolina at Chapel Hill Yes 2019-05-15 11:25:00
* Everett, Alex University of North Carolina at Chapel Hill Yes 2019-05-15 15:24:00
* Girard, David Trend Micro Yes 2019-05-20 14:55:00
* Hamilton, David AT&T Yes 2019-05-20 11:45:00
* Kakumaru, Takahiro NEC Corporation Yes 2019-05-16 14:55:00
* Kemp, David National Security Agency Yes 2019-05-14 20:00:00
* Lemire, David G2 Yes 2019-05-14 20:51:00
* Martinez, Danny G2 Yes 2019-05-20 18:08:00
* Meck, James FireEye, Inc. Yes 2019-05-15 16:02:00
* Patrick, Paul FireEye, Inc. Yes 2019-05-15 16:05:00
* Riedel, Daniel New Context Services, Inc. Yes 2019-05-14 22:20:00
* Riley, Shawn DarkLight, Inc. Yes 2019-05-15 14:59:00
* Romano, Jason National Security Agency Yes 2019-05-15 01:45:00
* Skeen, Duane Northrop Grumman Yes 2019-05-15 14:58:00
* Sparrell, Duncan sFractal Consulting LLC Yes 2019-05-14 20:47:00
* Stair, Michael AT&T Yes 2019-05-14 21:06:00
* Storms, Andrew New Context Services, Inc. Yes 2019-05-20 15:38:00
* Stueve, Gerald Fornetix Yes 2019-05-16 01:32:00
* Trost, Bill AT&T Yes 2019-05-14 21:31:00
* Varner, Drew NineFX, Inc. Yes 2019-05-16 01:05:00
* Yu, Sounil Bank of America Yes 2019-05-16 16:35:00
* Gurney, John-Mark New Context Services, Inc. --
* Hunt, Christian New Context Services, Inc. --
* Jordan, Bret Symantec Corp. --
* Joyce, Ryan DarkLight, Inc. --
* Mathews, Lisa National Security Agency --
* May, Andrew Viasat --
* Ortiz, Efrain Symantec Corp. --
* Ricard, Chris Financial Services Information Sharing and... --
* Webb, Jason LookingGlass --

Voter Comments

Submitter Vote Comment
Berliner, Brian
Symantec Corp.
Yes Approved. However, the example in Section A.4.2 is incorrect. It shows the response of a query/features/versions command incorrectly. The "versions" field should be inside a "results" object, per the requirements of the Language Spec. The other examples appear correctly. This is a minor edit.