OASIS Open: Committees

Proposal for elliptic curve mechanisms in section 1 of pkcs11-kdf-ecdh-v3.doc

Do you accept the proposal for elliptic curve key agreement mechanisms in section 1 of pkcs11-kdf-ecdh-v3.doc?

Do you accept the proposal for elliptic curve key agreement mechanisms in section 1 of pkcs11-kdf-ecdh-v3.doc as posted bz Mike StJohns on 14-Aug-2013 at https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/50278/pkcs11-kdf-ecdh-v3.docx? You also have the option to also vote at the same time for deprecation of CKM_ECDH1_DERIVE and CKM_ECDH1_COFACTOR_DERIVE, as proposed in section 2.3 of the document. Please choose only one of the 4 options below.

[ ]	accept the proposal as written
[ ]	accept proposal as written and deprecate current mechanisms
[ ]	reject the proposal
[ ]	abstain

Opening:		Monday, 26 August 2013 @ 03:45 am EDT
Closing:		Wednesday, 4 September 2013 @ 03:30 pm EDT
Group:		OASIS PKCS 11 TC

Ballot has closed.

Referenced Items
Name	Type	Date	Action
pkcs11-kdf-ecdh-v3.docx (30K)	Document	2013-08-14	Details
02497: Proposal for elliptic curve mechanisms in section 1 of pkcs11-kdf-ecdh-v3.doc (35K)	Document	2013-09-04	Details

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
accept the proposal as written	3	20%
accept proposal as written and deprecate current mechanisms	4	27%
reject the proposal	8	53%
abstain	0	0%

Eligible members who have voted:	15 of 32	47%
Eligible members who have abstained:	0 of 32	0%
Eligible members who have not voted:	17 of 32	53%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Chris Zimman	Bloomberg Finance L.P.	--
Magda Zdunkiewicz	Cryptsoft Pty Ltd.	reject the proposal
Tony Cox	Cryptsoft Pty Ltd.	reject the proposal
Tim Hudson	Cryptsoft Pty Ltd.	reject the proposal	This proposal (as perviously commented) tangles too many items in along with the solution for the simple problem it is meant to be tackling. Sorting out the entire KDF handling area requires more disc
Robert Griffin	EMC	--
Ryan Smith	Futurex	--
Fadi Cotran	Futurex	--
Walter-John Turnes	Gemini Security Solutions, Inc.	--
Wan-Teh Chang	Google Inc.	--
Darren Krahn	Google Inc.	reject the proposal
Gershon Janssen	Individual	--
Michael StJohns	Individual	accept proposal as written and deprecate curren...
Alex Krasnov	Infineon Technologies AG	--
Hai-May Chao	Oracle	--
Mark Powers	Oracle	--
Dina Kurktchi	Oracle	--
Hal Lockhart	Oracle	accept proposal as written and deprecate curren...
Oscar So	Oracle	accept proposal as written and deprecate curren...
Radhika Siravara	Oracle	accept the proposal as written
Valerie Fenwick	Oracle	accept the proposal as written
Susan Gleeson	Oracle	reject the proposal
Michael Stevens	QuintessenceLabs Pty Ltd.	--
Stef Walter	Red Hat	--
Robert Relyea	Red Hat	accept the proposal as written	NSS certainly has a need for the kdf to be split into it's own mechanism. We have cases where a smart card only supports KDF_NULL and we have to move the key into the NSS token to complete the operati
Ajai Puri	SafeNet, Inc.	--
Doron Cohen	SafeNet, Inc.	accept proposal as written and deprecate curren...
Andrey Jivsov	Symantec Corp.	reject the proposal
Mark Knight	Thales e-Security	--
Sander Temme	Thales e-Security	reject the proposal
Robert Burns	Thales e-Security	reject the proposal	I agree in spirit that ECDH mechanisms need improvement, and that a stand alone KDF function is useful, but I think this proposal is over ambitious for the 2.40 specification.
David Smith	Venafi, Inc.	--
Janice Cheng	Vormetric, Inc.	--