Key Management Interoperability Protocol Specification Version 1.1

More documents

Recommendations

Info

Technical Committee members should send comments on this specification to the TechnicalCommittee’s email list. Others should send comments to the Technical Committee by using the“Send A Comment” button on the Technical Committee’s web page at http://www.oasisopen.org/committees/kmip/.For information on whether any patents have been disclosed that may be essential toimplementing this specification, and any offers of patent licensing terms, please refer to theIntellectual Property Rights section of the Technical Committee web page (http://www.oasisopen.org/committees/kmip/ipr.php).Citation format:When referencing this specification the following citation format should be used:[KMIP-v1.1]Key Management Interoperability Protocol Specification Version 1.1. 21 September 2012.Candidate OASIS Standard 01.http://docs.oasis-open.org/kmip/spec/v1.1/cos01/kmip-spec-v1.1-cos01.html.kmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 2 of 164
NoticesCopyright © OASIS Open 2012. All Rights Reserved.All capitalized terms in the following text have the meanings assigned to them in the OASIS IntellectualProperty 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 thatcomment 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 noticeand this section are included on all such copies and derivative works. However, this document itself maynot be modified in any way, including by removing the copyright notice or references to OASIS, except asneeded for the purpose of developing any document or deliverable produced by an OASIS TechnicalCommittee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, mustbe 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 successorsor assigns.This document and the information contained herein is provided on an "AS IS" basis and OASISDISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANYWARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANYOWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE.OASIS requests that any OASIS Party or any other party that believes it has patent claims that wouldnecessarily 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 tosuch patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee thatproduced this specification.OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership ofany patent claims that would necessarily be infringed by implementations of this specification by a patentholder that is not willing to provide a license to such patent claims in a manner consistent with the IPRMode of the OASIS Technical Committee that produced this specification. OASIS may include suchclaims 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 thatmight be claimed to pertain to the implementation or use of the technology described in this document orthe extent to which any license under such rights might or might not be available; neither does itrepresent that it has made any effort to identify any such rights. Information on OASIS' procedures withrespect to rights in any document or deliverable produced by an OASIS Technical Committee can befound on the OASIS website. Copies of claims of rights made available for publication and anyassurances of licenses to be made available, or the result of an attempt made to obtain a general licenseor permission for the use of such proprietary rights by implementers or users of this OASIS CommitteeSpecification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes norepresentation that any information or list of intellectual property rights will at any time be complete, orthat 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 beused only to refer to the organization and its official outputs. OASIS welcomes reference to, andimplementation and use of, specifications, while reserving the right to enforce its marks againstmisleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark for aboveguidance.kmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 3 of 164
Page 1: Key Management InteroperabilityProt
Page 5 and 6: 3.18.1 Operations outside of operat
Page 7 and 8: 11.8 Certify ......................
Page 9: sanction to perform a security func
Page 13 and 14: 11411511611711811912012112212312412
Page 15 and 16: 18818919019119219319419519619719819
Page 17 and 18: 23723823924024124224324424524624724
Page 19 and 20: 28628728828929029129229329429529629
Page 21 and 22: Value SHALL be TTLVencoded.32632732
Page 23 and 24: Object Encoding REQUIREDKey Materia
Page 25 and 26: 3763773782.1.7.11 Transparent ECDH
Page 27 and 28: Object Encoding REQUIREDSymmetric K
Page 29 and 30: 47447547647747847948048148248348448
Page 31 and 32: 50150250350450550650750850951051151
Page 33 and 34: SHALL always have a valueInitially
Page 35 and 36: 558559key contained within the Cert
Page 37 and 38: 577578579580581582583584585586X9, I
Page 39 and 40: 609Table 56: X.509 Certificate Iden
Page 45 and 46: 71571671771871972072172272372472572
Page 47 and 48: Default Operation Policy for Privat
Page 51 and 52: 81881982082182282382482582682782882
Page 53 and 54:
892893object is destroyed. This att
Page 55 and 56:
SHALL always have a valueInitially
Page 57 and 58:
944945946indicates when the key man
Page 59 and 60:
9709719729733.34 FreshThe Fresh att
Page 61 and 62:
Application SpecificInformationObje
Page 63 and 64:
SHALL always have a valueInitially
Page 65 and 66:
Request PayloadObject REQUIRED Desc
Page 67 and 68:
Attribute REQUIRED SHALL contain th
Page 69 and 70:
1152115311541155115611571158As a re
Page 71 and 72:
AttributePrivate Key UniqueIdentifi
Page 73 and 74:
management server.11941195119611971
Page 75 and 76:
12361237123812391240124112421243124
Page 77 and 78:
12881289129012911292129312941295129
Page 79 and 80:
13241325132613271328132913301331133
Page 81 and 82:
Page 83 and 84:
Response PayloadObject REQUIRED Des
Page 85 and 86:
Page 87 and 88:
Response PayloadObject REQUIRED Des
Page 89 and 90:
15371538153915401541154215431544154
Page 91 and 92:
1588158915901591159215931594a list
Page 93 and 94:
16231624162516261627162816291630163
Page 95 and 96:
16651666166716681669167016711672167
Page 97 and 98:
17211722172317241725172617271728172
Page 99 and 100:
Option17911792179317941795Table 201
Page 101 and 102:
Request Batch ItemObject REQUIRED i
Page 103 and 104:
18311832183318341835183618371838183
Page 105 and 106:
18811882188318841885188618871888188
Page 107 and 108:
ObjectTagTag ValueCertificate Subje
Page 109 and 110:
ObjectPadding Methodkmip-spec-v1.1-
Page 111 and 112:
TagObjectTag ValueExtension Type420
Page 113 and 114:
19379.1.3.2.4 Wrapping Method Enume
Page 115 and 116:
19469.1.3.2.8 Split Key Method Enum
Page 117 and 118:
RC4 00000016RC5 00000017SKIPJACK 00
Page 119 and 120:
19649.1.3.2.17 Key Role Type Enumer
Page 121 and 122:
19759.1.3.2.21 Derivation Method En
Page 123 and 124:
19879.1.3.2.27 Operation Enumeratio
Page 125 and 126:
19939.1.3.2.30 Batch Error Continua
Page 127 and 128:
200820092010201110 TransportKMIP Se
Page 129 and 130:
Operation Failed20172018Table 249:
Page 131 and 132:
202411.5 Re-keyError Definition Res
Page 133 and 134:
203011.8 CertifyError Definition Re
Page 135 and 136:
Key Wrapping Specification contains
Page 137 and 138:
205011.18 Obtain LeaseError Definit
Page 139 and 140:
a certificate listOne or more of th
Page 141 and 142:
20952096209720982099210021012102210
Page 143 and 144:
CertificateSymmetric KeyPublic KeyP
Page 145 and 146:
22092210Appendix C. Tag Cross-Refer
Page 147 and 148:
Object Defined Type NotesInitializa
Page 149 and 150:
Object Defined Type NotesResult Mes
Page 151 and 152:
221322142215Appendix D. Operations
Page 153 and 154:
22192220222122222223222422252226222
Page 155 and 156:
22932294229522962297229822992300230
Page 157 and 158:
23482349235023512352235323542355235
Page 159 and 160:
24322433243424352436243724382439244
Page 161 and 162:
25162517251825192520252125222523252
Page 163 and 164:
2591Appendix G. Revision HistoryRev
show all

Key Management Interoperability Protocol Specification Version 1.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?