OASIS Open: Committees

RNG - go forward strategy

Which way do we move forward around RNG prescription in various operations?

There are two different approaches to addressing how to describe/select/seed/... RNGs in KMIP:

1. Enhancements to query and use of attributes to prescribe RNGs during usage
2. RNG as an object with its set of operations and changes to other operations

[ ]	Query enhancements + Attributes
[ ]	RNG Object
[ ]	Both 1 & 2
[ ]	Neither

Opening:		Wednesday, 1 January 2014 @ 11:00 am PST
Closing:		Thursday, 9 January 2014 @ 11:00 am PST
Group:		OASIS Key Management Interoperability Protocol (KMIP) TC

Ballot has closed.

Referenced Items
Name	Type	Date	Action
02557: RNG - go forward strategy (35K)	Document	2014-01-09	Details

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
Query enhancements + Attributes	26	90%
RNG Object	0	0%
Both 1 & 2	3	10%
Neither	0	0%

Eligible members who have voted:	29 of 33	88%
Eligible members who have abstained:	0 of 33	0%
Eligible members who have not voted:	4 of 33	12%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Magda Zdunkiewicz	Cryptsoft Pty Ltd.	Query enhancements + Attributes
Amruta Soman	Cryptsoft Pty Ltd.	Query enhancements + Attributes
Tim Hudson	Cryptsoft Pty Ltd.	Query enhancements + Attributes	Changing the approach for RNG to be an object would be inconsistent with the KMIP model and the decisions already made as part of KMIP-1.2 and without substantial reasons to change we should not be ch
Tony Cox	Cryptsoft Pty Ltd.	Query enhancements + Attributes	I'm unsure how Random can neatly fit within the definition of an Object, given that Objects are immutable in KMIP. From my standpoint it would appear every operation that involves an Object would need
Warren Robbins	Dell	Query enhancements + Attributes
Peter Robinson	EMC	Both 1 & 2
Judith Furlong	EMC	Query enhancements + Attributes
Krishna Yellepeddy	IBM	Query enhancements + Attributes
Bruce Rich	IBM	Query enhancements + Attributes
John Peck	IBM	Query enhancements + Attributes
Tom Benjamin	IBM	Query enhancements + Attributes
Rick Robinson	IBM	Query enhancements + Attributes
Michael Jenkins	National Security Agency	--
Subhash Sankuratripati	NetApp	Query enhancements + Attributes
Hal Lockhart	Oracle	Query enhancements + Attributes
Susan Gleeson	Oracle	Query enhancements + Attributes
Saikat Saha	Oracle	Query enhancements + Attributes
Mark Joseph	P6R, Inc	Query enhancements + Attributes	Lets not go over ground that has already been decided. We need to add other items to the protocol and should not waste time on old issues.
Kenli Chong	QuintessenceLabs Pty Ltd.	--
Jin Wong	QuintessenceLabs Pty Ltd.	--
Warren Armstrong	QuintessenceLabs Pty Ltd.	Both 1 & 2
John Leiseboer	QuintessenceLabs Pty Ltd.	Both 1 & 2	The query enhancements are compatible with the RNG Object proposal, however they do not provide the more complete protection and assurance of the RNG Object proposal.
Stephen Kingston	SafeNet, Inc.	--
Catherine Ying	SafeNet, Inc.	Query enhancements + Attributes
Charles White	Semper Fortis Solutions, LLC.	Query enhancements + Attributes
Joseph Brand	Semper Fortis Solutions, LLC.	Query enhancements + Attributes
Jeff Bartell	Semper Fortis Solutions, LLC.	Query enhancements + Attributes
Kathy Kriese	Symantec Corp.	Query enhancements + Attributes
Nathan Turajski	Thales e-Security	Query enhancements + Attributes
Robert Burns	Thales e-Security	Query enhancements + Attributes
Robert Lockhart	Thales e-Security	Query enhancements + Attributes	I do not believe that creating a full object and attributes for RNG would fall under what we are trying to do in OASIS KMIP TC. I believe that it falls too far inside implementation which is best lef
Kiran Thota	VMware, Inc.	Query enhancements + Attributes	RNG object, as I understand it, will need more serious thought and changes in the spec. Will be a good candidate to investigate for a major revision and not 1.3.
Michael Yoder	Vormetric, Inc.	Query enhancements + Attributes