Key Management Interoperability Protocol Profiles Version 1.1 Errata 01
OASIS Approved Errata
25 September 2014
Specification URIs
This version:
http://docs.oasis-open.org/kmip/profiles/v1.1/errata01/os/kmip-profiles-v1.1-errata01-os.doc (Authoritative)
http://docs.oasis-open.org/kmip/profiles/v1.1/errata01/os/kmip-profiles-v1.1-errata01-os.html
http://docs.oasis-open.org/kmip/profiles/v1.1/errata01/os/kmip-profiles-v1.1-errata01-os.pdf
Previous version:
http://docs.oasis-open.org/kmip/profiles/v1.1/errata01/csprd01/kmip-profiles-v1.1-errata01-csprd01.doc (Authoritative)
Latest version:
http://docs.oasis-open.org/kmip/profiles/v1.1/kmip-profiles-v1.1.doc (Authoritative)
http://docs.oasis-open.org/kmip/profiles/v1.1/kmip-profiles-v1.1.html
http://docs.oasis-open.org/kmip/profiles/v1.1/kmip-profiles-v1.1.pdf
Technical Committee:
OASIS Key Management Interoperability Protocol (KMIP) TC
Chairs:
Saikat Saha, saikat.saha@oracle.com, Oracle
Tony Cox, tjc@cryptsoft.com, Cryptsoft Pty Ltd.
Editor:
Robert Griffin (robert.griffin@rsa.com), EMC Corporation
Related work:
This specification lists errata for:
This specification is related to:
· Key Management Interoperability Protocol Usage Guide Version 1.1. Latest Version http://docs.oasis-open.org/kmip/ug/v1.1/kmip-ug-v1.1.html.
Abstract:
This specification lists errata for the OASIS Standard Key Management Interoperability Protocol Profiles Version 1.1.
Status:
This document was last revised or approved by the OASIS Key Management Interoperability Protocol (KMIP) TC on the above date. The level of approval is also listed above. Check the “Latest version” location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=kmip#technical.
TC members should send comments on this specification to the TC’s email list. Others should send comments to the TC’s public comment list, after subscribing to it by following the instructions at the “Send A Comment” button on the TC’s web page at https://www.oasis-open.org/committees/kmip/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (https://www.oasis-open.org/committees/kmip/ipr.php).
Citation format:
When referencing this specification the following citation format should be used:
[KMIP-Profile-v1.1-Errata]
Key Management Interoperability Protocol Profiles Version 1.1 Errata 01. Edited by Robert Griffin. 25 September 2014. OASIS Approved Errata. http://docs.oasis-open.org/kmip/profiles/v1.1/errata01/os/kmip-profiles-v1.1-errata01-os.html. Latest version: http://docs.oasis-open.org/kmip/profiles/v1.1/kmip-profiles-v1.1.html.
Notices
Copyright © OASIS Open 2014. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for above guidance.
Table of Contents
2 Approved Errata for KMIP Profiles V1.1
This document contains errata for the KMIP Profiles Version 1.1.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].
[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt.
[KMIP-Spec] Key Management Interoperability Protocol
Specification Version 1.1. 24 January 2013. OASIS Standard.
http://docs.oasis-open.org/kmip/spec/v1.1/os/kmip-spec-v1.1-os.html.
[KMIP-Prof] Key
Management Interoperability Protocol Profiles Version 1.1. 24 January 2013.
OASIS Standard.
http://docs.oasis-open.org/kmip/profiles/v1.1/os/kmip-profiles-v1.1-os.html.
See PDF and DOC versions of [KMIP-Prof] for line numbers referenced below.
[KMIP-UG] Key Management Interoperability Protocol
Usage Guide Version 1.1. 27 July 2012. OASIS Committee Note 01.
http://docs.oasis-open.org/kmip/ug/v1.1/kmip-ug-v1.1.html.
[KM-TC] Key Management Interoperability Protocol Test Cases Version 1.1. 27 July 2012. OASIS Committee Note 01. http://docs.oasis-open.org/kmip/testcases/v1.1/kmip-testcases-v1.1.html.
Following are the approved errata to the KMIP Profiles V1.1 OASIS Standard.
At [KMIP-Prof] line 208, add the following missing text after the word “TLS”: “1.2 Authentication Suite).”
At [KMIP-Prof] line 257, change “Basic Authentication Suite” to “TLS 1.2 Authentication Suite”.
At [KMIP-Prof] line 260, change “Basic Authentication Suite” to “TLS 1.2 Authentication Suite”.
At [KMIP-Prof] line 268, change “Server Conformance Clause” to “Client Conformance Clause”.
At [KMIP-Prof] line 300, remove trailing period in “”5.1.1.”.
The following individuals have participated in the creation of this and other KMIP V1.1 documents and are gratefully acknowledged:
Participants:
Hal Aldridge, Sypris Electronics
Mike Allen, Symantec
Gordon Arnold, IBM
Todd Arnold, IBM
Matthew Ball, Oracle Corporation
Elaine Barker, NIST
Peter Bartok, Venafi, Inc.
Mathias Björkqvist, IBM
Kelley Burgin, National Security Agency
John Clark, Hewlett-Packard
Tom Clifford, Symantec Corp.
Graydon Dodson, Lexmark International Inc.
Chris Dunn, SafeNet, Inc.
Michael Duren, Sypris Electronics
Paul Earsy, SafeNet, Inc.
Stan Feather, Hewlett-Packard
Indra Fitzgerald, Hewlett-Packard
Alan Frindell, SafeNet, Inc.
Judith Furlong, EMC Corporation
Jonathan Geater, Thales e-Security
Susan Gleeson, Oracle
Robert Griffin, EMC Corporation
Paul Grojean, Individual
Robert Haas, IBM
Thomas Hardjono, M.I.T.
Steve He, Vormetric
Kurt Heberlein, Hewlett-Packard
Joel Hockey, Cryptsoft Pty Ltd.
Larry Hofer, Emulex Corporation
Brandon Hoff, Emulex Corporation
Walt Hubis, NetApp
Tim Hudson, Cryptsoft Pty Ltd.
Jay Jacobs, Target Corporation
Glen Jaquette, IBM
Scott Kipp, Brocade Communications Systems, Inc.
Kathy Kriese, Symantec Corporation
David Lawson, Emulex Corporation
John Leiseboer, Quintenssence Labs
Hal Lockhart, Oracle Corporation
Robert Lockhart, Thales e-Security
Anne Luk, Cryptsoft Pty Ltd.
Shyam Mankala, EMC Corporation
Upendra Mardikar, PayPal Inc.
Luther Martin, Voltage Security
Hyrum Mills, Mitre Corporation
Bob Nixon, Emulex Corporation
René Pawlitzek, IBM
John Peck, IBM
Rob Philpott, EMC Corporation
Denis Pochuev, SafeNet, Inc.
Ajai Puri, SafeNet, Inc.
Peter Reed, SafeNet, Inc.
Bruce Rich, IBM
Warren Robbins, Credant Systems
Saikat Saha, SafeNet, Inc.
Subhash Sankuratripati, NetApp
Mark Schiller, Hewlett-Packard
Brian Spector, Certivox
Terence Spies, Voltage Security
Marcus Streets, Thales e-Security
Kiran Thota, VMware
Sean Turner, IECA, Inc.
Paul Turner, Venafi, Inc.
Marko Vukolić, Eurécom
Rod Wideman, Quantum Corporation
Steven Wierenga, Hewlett-Packard
Peter Yee, EMC Corporation
Krishna Yellepeddy, IBM
Michael Yoder, Voremetric. Inc.
Magda Zdunkiewicz, Cryptsoft Pty Ltd.
Peter Zelechoski, Election Systems & Software
Revision |
Date |
Editor |
Changes Made |
wd01 |
23 July 2013 |
Robert Griffin |
Initial version, incorporating errata for KMIP Profiles V1.1 that were removed from the draft KMIP Specification V1.1 Errata wd01. |