OASIS Open: Committees

Approval of WD01 of the OpenC2 Over HTTPS Specification as a Committee Specification Draft

Do you approve the OpenC2 Over HTTPS Transfer Specification v1.0 Working Draft 01 (WD01) and all associated artifacts as Committee Specification Draft 01?

WD01 was presented to the OpenC2 TC for review and approval at the 18 July 2018 TC meeting, and the Implementation Considerations Subcommittee (IC-SC) recommends its approval as a CSD. The balance of the OpenC2 Over HTTPS Specification (to include portions marked TBSL and TBD in this version) will be provided in subsequent Working Drafts.

The OpenC2 Over HTTPS Transfer Specification v1.0 Working Draft 01 and all associated artifacts are packaged together in openc2-impl-https-WD01.zip, https://www.oasis-open.org/committees/document.php?document_id=63682&wg_abbrev=openc2.

The Markdown (MD) version of the specification will be designated as authoritative.

This ballot requires a majority vote of the TC's voting members. The ballot is open for 2 weeks to allow TC members time to review and consider the draft.

[ ]	Yes
[ ]	No
[ ]	Abstain

Opening:		Thursday, 9 August 2018 @ 03:00 pm EDT
Closing:		Thursday, 23 August 2018 @ 11:00 am EDT
Group:		OASIS Open Command and Control (OpenC2) TC

Ballot has closed.

Referenced Items
Name	Type	Date	Action
03231: Approval of WD01 of the OpenC2 Over HTTPS Specification as a Committee Specification Draft (32K)	Document	2018-08-23	Details

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
Yes	18	95%
No	1	5%
Abstain	1

Eligible members who have voted:	19 of 32	59%
Eligible members who have abstained:	1 of 32	3%
Eligible members who have not voted:	12 of 32	38%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Michelle Barry	AT&T	Abstain	Clarity is needed re: issue #3. I'm going to be out of the country for 2 weeks and therefore am abstaining given clarification and discussion will occur after I'm offline.
David Hamilton	AT&T	Yes
Michael Stair	AT&T	Yes	Trey summarizes very well.
Bill Trost	AT&T	Yes	I am voting yes, given this is an initial draft, with some consternation over the wording on support for REST. I am also not clear about the wording around HTTPS support.
Travis Farral	Anomali	Yes
Sounil Yu	Bank of America	Yes	I concur with Duncan and take Trey's position as well.
Chris Ricard	Financial Services Information Sharing and...	--
Paul Patrick	FireEye, Inc.	--
James Meck	FireEye, Inc.	--
Sean Barnum	FireEye, Inc.	--
Andy Gray	ForeScout	Yes
Gerald Stueve	Fornetix	--
David Lemire	G2	Yes
Danny Martinez	G2	Yes
Adrian Bishop	Huntsman Security	--
Jason Webb	LookingGlass	--
Takahiro Kakumaru	NEC Corporation	Yes
Joe Brule	National Security Agency	Yes
Jason Romano	National Security Agency	Yes
Lisa Mathews	National Security Agency	Yes
Andrew Storms	New Context Services, Inc.	--
Christian Hunt	New Context Services, Inc.	--
Daniel Riedel	New Context Services, Inc.	Yes
John-Mark Gurney	New Context Services, Inc.	Yes	I have provided a number of comments to the WD01 spec. IMO, it is in good shape, and I believe Duncan's issue would be solved by striking the sentence from the spec.
Trey Darley	New Context Services, Inc.	Yes	In the spirit of how the OpenC2 TC has progressed through rapid CSD releases, I am voting yes on this initial draft. But I concur with Duncan's comments about not precluding a RESTful implementation.
Duane Skeen	Northrop Grumman	Yes
Philip Royer	Splunk Inc.	Yes
Bret Jordan	Symantec Corp.	--
Efrain Ortiz	Symantec Corp.	Yes
Alex Everett	University of North Carolina at Chapel Hill	--
Andrew May	Viasat	--
Duncan Sparrell	sFractal Consulting LLC	No	I object that the spec can not be used for rest api's. Given all the interfaces I could find for cloud security were rest api's, I think whatever obstacles to using rest must be removed. I have opened