Ballot Details: Deprecation Rule (CLOSED)

Ballot Question Do you approve the proposed rule related to deprecating KMIP functionallity?
Ballot Description Do you approve, for KMIP V1.2 and all subsequent KMIP versions, this proposed TC rule regarding deprecation as posted by Bob Griffin to the KMIP mailing list on 3-Dec-2012: “Upon approval from the KMIP TC, items in the normative KMIP Specification document can be marked deprecated in any document version, but will be removed only in a major version. Similarly, conformance clauses or other normative information in the KMIP Profiles document can be deprecated in any document version, but removed only in a major version. Information in the non-normative KMIP Use Cases, KMIP Usage Guide and KMIP Test Cases documents may be removed in any document version.”
Ballot Options
VOTING CLOSED: Thursday, 20 December 2012 @ 2:00 pm EST
Yes 21 100
No 0 0
Abstain 0
Open Date Monday, 10 December 2012 @ 6:00 am EST
Close Date Thursday, 20 December 2012 @ 2:00 pm EST

Voting Statistics

Number of votes cast (excluding abstentions) 21
Eligible members who have voted 21 of 34 61 13/17%
Eligible members who have not voted 13 of 34 38 4/17%

Voting Summary by Option

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

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Allen, Mike Symantec Corp. Yes 2012-12-12 19:19:00
* Burgin, Kelley National Security Agency Yes 2012-12-10 14:32:00
* Burns, Robert Thales e-Security Yes 2012-12-10 18:24:00
* Cox, Tony Cryptsoft Pty Ltd. Yes 2012-12-10 22:01:00
* Feather, Stan Hewlett-Packard Yes 2012-12-10 18:28:00
* Furlong, Judith EMC Yes 2012-12-10 20:06:00
* Gleeson, Susan Oracle Yes 2012-12-13 17:04:00 1
* Griffin, Robert EMC Yes 2012-12-10 11:11:00
* Hudson, Tim Cryptsoft Pty Ltd. Yes 2012-12-10 11:32:00
* Kenig, Marc SafeNet, Inc. Yes 2012-12-13 17:24:00
* Leiseboer, John QuintessenceLabs Pty Ltd. Yes 2012-12-12 06:37:00
* Lockhart, Robert Thales e-Security Yes 2012-12-10 17:21:00
* Peck, John IBM Yes 2012-12-10 12:36:00
* Puri, Ajai SafeNet, Inc. Yes 2012-12-10 15:02:00
* Rich, Bruce IBM Yes 2012-12-12 19:49:00
* Robbins, Warren Credant Technologies, Inc. Yes 2012-12-10 19:16:00
* Turajski, Nathan Thales e-Security Yes 2012-12-13 20:53:00
* Wideman, Rod Quantum Corporation Yes 2012-12-12 19:00:00 1
* Wierenga, Steven Hewlett-Packard Yes 2012-12-13 18:23:00 1
* Yellepeddy, Krishna IBM Yes 2012-12-10 15:27:00
* Yoder, Michael Vormetric, Inc. Yes 2012-12-10 21:19:00
* Arnold, Gordon IBM --
* Benjamin, Tom IBM --
* Berglas, Anthony Cryptsoft Pty Ltd. --
* Bjorkqvist, Mathias IBM --
* Fitzgerald, Indra Hewlett-Packard --
* Lockhart, Hal Oracle --
* Olson, Bryan Hewlett-Packard --
* Saha, Saikat SafeNet, Inc. --
* Sankuratripati, Subhash NetApp --
* Singh, Greg QuintessenceLabs Pty Ltd. --
* Stevens, Michael QuintessenceLabs Pty Ltd. --
* Thota, Kiran VMware, Inc. --
* Zdunkiewicz, Magda Cryptsoft Pty Ltd. --

Voter Comments

Submitter Vote Comment
Wideman, Rod
Quantum Corporation
Yes As an alternative to complete removal, designating an item as 'obsolete' might be useful (i.e., it would transition from deprecated to obsolete). This avoids potential re-use of values in subsequent versions.
Gleeson, Susan
Oracle
Yes Suggest possibly moving deprecated item info to an appendix or (probably better) having an appendix with a list of deprecated items and the version in which they were deprecated.
Wierenga, Steven
Hewlett-Packard
Yes I favor the latter recommendation in Susan Gleeson's comment.