Key Management Interoperability Protocol Tape Library Profile Version 1.0

Transcription

1 Key Management Interoperability Protocol Tape Library Profile Version 1.0 Working Draft April 2013 Technical Committee: OASIS Key Management Interoperability Protocol (KMIP) TC Chairs: Robert Griffin EMC Corporation Subhash Sankuratripati NetApp Editors: Tim Hudson Cryptsoft Stan Feather Hewlett-Packard Rod Wideman Quantum Related work: This specification is related to: Key Management Interoperability Protocol Profiles Version October OASIS Standard. Key Management Interoperability Protocol Specification Version January OASIS Standard. Abstract: Describes a profile for Tape Libraries as KMIP clients interacting with KMIP servers Status: This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and reapprove it any number of times as a Committee Draft. Copyright OASIS Open 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. Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 1 of 17

2 Table of Contents 1 Introduction Terminology Normative References Non-Normative References Tape Library Profile Authentication Suite Baseline Tape Library Using Application Specific Information for Key Identifiers Tape Library Profile Test Cases Mandatory Test Cases... 8 TL-M-1 - Configuration... 8 TL-M-2 - Write with new (Created) Key... 9 TL-M-3 - Read from Tape TL-M-4 Appended Write Optional Test Cases Appendix A. Acknowledgments Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 2 of 17

3 1 Introduction For normative definition of the elements of KMIP see the KMIP Specification ([KMIP-SPEC-1_0 and KMIP-SPEC-1_1]) and the KMIP Profiles ([KMIP-PROF-1_0 and KMIP-PROF-1_1]). Illustrative guidance for the implementation of KMIP clients and servers is provided in the KMIP Usage Guide ([KMIP-UG]) and KMIP Use Cases ([KMIP-UC]) and KMIP Test Cases ([KMIP-TC]). This profile defines the necessary KMIP functionality that a Tape Library operating as a KMIP client SHALL use and a KMIP server conforming to this profile SHALL support in order to interoperate in conformance with this profile. 1.1 Terminology 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]. Key Associated Data (KAD) Hexadecimal Numeric Characters N(a) N(u) Part of the tape format. May be segmented into authenticated and unauthenticated fields. KAD usage is detailed in the SCSI SSC-3 standard from the T10 organization available as ANSI INCITS Case-sensitive, printable, single byte ASCII characters representing the numbers 0 through 9 and uppercase alpha A through F. (US-ASCII characters 30h-39h and 41h-46h). Each byte (single 8-bit numeric value) is represented as two hexadecimal numeric characters with the highnibble represented by the first (left-most) hexadecimal numeric character and the low-nibble represented by the second (right-most) hexadecimal numeric character. The maximum number of bytes in the tape authenticated KAD field. For LTO4, N(a) is 12 bytes. For LTO5, N(a) is 60 bytes. The maximum number of bytes in the tape unauthenticated KAD field. For LTO4, N(u) is 32 bytes. For LTO5, N(u) is 32 bytes. N(k) The maximum number of bytes in the tape format KAD fields i.e. N(a) + N(u). For LTO4, N(k) is 44 bytes. For LTO5, N(k) is 92 bytes. 1.2 Normative References [RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, IETF RFC 2119, March [RFC2246] T. Dierks and C. Allen, The TLS Protocol, Version 1.0, IETF RFC 2246, Jan 1999, [KMIP-SPEC-1_0] Key Management Interoperability Protocol Specification Version OASIS Standard, October Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 3 of 17

4 [KMIP-SPEC-1_1] Key Management Interoperability Protocol Specification Version Candidate OASIS Standard September [KMIP-PROF-1_0] Key Management Interoperability Protocol Usage Guide Version OASIS Standard. 1 October [KMIP-PROF-1_1] Key Management Interoperability Protocol Usage Guide Version Candidate OASIS Standard September Non-Normative References [KMIP-UG] Key Management Interoperability Protocol Usage Guide Version Committee Note Draft, 1 December 2011, [KMIP-TC] Key Management Interoperability Protocol Test Cases Version Committee Note Draft, 1 December [KMIP-UC] Key Management Interoperability Protocol Use Cases Version doc, Committee Specification, 15 June Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 4 of 17

5 2 Tape Library Profile The Tape Library Profile is a tape library operating as a KMIP client interacting with a KMIP server. 2.1 Authentication Suite Implementations conformant to this profile SHALL support at least one of the Authentication Suites defined within section 3 of KMIP Profiles ([KMIP-PROF-1_0] and/or [KMIP-PROF-1_1]). The establishment of the trust relationship between the KMIP client and the KMIP server is the same as the defined base profiles for the version of the profile supported. 2.2 Baseline Tape Library KMIP clients conformant to this profile: 1. SHALL conform to the KMIP Baseline Client profile in KMIP Profiles ([KMIP-PROF-1_0] and/or [KMIP-PROF-1_1]) and the KMIP Specification [KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 2. SHALL support Application Specific Information with Application Data provided by the client in accordance with the algorithm specified in this profile. 3. SHOULD NOT use custom attributes that duplicate information that is already in standard KMIP attributes 4. MAY use x-barcode as the custom attribute of type Textstring to store the barcode KMIP servers conformant to this profile SHALL: 1. Conform to the KMIP Baseline Server profile in KMIP Profiles ([KMIP-PROF-1_0] and/or [KMIP- PROF-1_1]) and the KMIP Specification [KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 2. Support the following additional objects a. Symmetric Key ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 2.2.2) 3. Support the following client-to-server operations: a. Create ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 4.1) 4. Support the following subsets of enumerated attributes: a. Cryptographic Algorithm Enumeration ([KMIP-SPEC-1_0] and/or [KMIP-SPEC- 1_1] ) i. AES b. Object Type Enumeration ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] ) i. Symmetric Key c. Key Format Type Enumeration ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] ) i. Raw d. Cryptographic Length ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 3.5) i. 256-bit 5. Support the following subsets of Name Types ([KMIP-SPEC-1_0] 3.2 and and/or [KMIP-SPEC-1_1] 3.2 and ) a. Uninterpreted Text String 6. Support custom attributes (client specified x-customattributename) with the following data types and properties: a. TextString Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 5 of 17

6 b. Integer c. DateTime 7. Support a minimum length of 256 characters for custom attribute values where the custom attribute type is of variable length. 8. Support a minimum of 30 custom attributes per managed object 9. Support a minimum of 64 characters in customer attribute names 10. Support a Batch Order Option ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 6.12) setting of True. 11. Support a Batch Count ([KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] 6.14) setting of at least Support the Test Library Profile Test Cases returning results consistent with the test cases. 13. Optionally support any clause within [KMIP-SPEC-1_0] and/or [KMIP-SPEC-1_1] that is not listed above 14. Optionally support extensions outside the scope of this standard (e.g., vendor extensions, conformance clauses) that do not contradict any KMIP requirements. 2.3 Using Application Specific Information for Key Identifiers This information applies to Tape Libraries that support usage of the Application Specific Information attribute to store key identifiers. The Application Specific Information (ASI) attribute SHALL be used to store data that is specific to the application (tape library) using the object. The following Application Namespaces are recommended and SHOULD be used in the Application Namespace field of the Application Specific Information attribute: LIBRARY-LTO, LIBRARY-LTO4, LIBRARY-LTO5, and LIBRARY-LTO6 For backwards compatibility with deployed Tape Library implementations servers MAY elect to support VENDOR-LIBRARY-LTO as an Application Namespace where VENDOR is an ASCII string that SHALL not be further interpreted and SHALL be handled by the server as if the Application Namespace was set to LIBRARY-LTO. ASI supports key identifiers being created either on the Server or on the Client (Tape Library), but not both. The ASI method of key identification relies on the ability to uniquely identify a key based (preferably) only on its Application Data, or (alternatively) on some combination of Application Data and custom attributes, which the key creator guarantees to be unique within the Application Namespace. Claiming support for non-vendor-specific namespaces SHALL therefore ensure uniqueness across any LTO implementation, and is preferred for maximum interoperability. Key identifiers stored in the KMIP server's ASI attribute are always in ASCII format. Key identifiers stored in the KMIP client's tape format KAD fields are always numeric format. The method provides a specific algorithm for converting between text and numeric formats. All information contained in the tape format s KAD fields is converted to an ASCII string consisting of hexadecimal numeric character pairs. First, the unauthenticated KAD is converted to text. Second, the authenticated KAD is converted to text and is then concatenated to the end of the converted unauthenticated KAD text. For KMIP clients and servers conforming to this profile, Application Specific Information data SHALL be sent by the tape library KMIP client based on the tape format's KAD fields as follows: 1. Define an empty output buffer sufficient to contain a string with a maximum length of 2*N(k) bytes. 2. Copy the tape format s unauthenticated KAD (if present) to the output buffer converting each byte value to exactly two Hexadecimal Numeric Characters. Effectively, the first byte (byte 0) of the input buffer is the first byte of unauthenticated KAD. 3. Concatenate the tape format s authenticated KAD to the output buffer converting each byte value to exactly two Hexadecimal Numeric Characters. Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 6 of 17

7 Note: the contents of unauthenticated KAD and authenticated KAD fields may be less than the maximum permitted lengths; the implementation provides the correct length values to use in the algorithm rather than using fixed maximum length fields. Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 7 of 17

8 3 Tape Library Profile Test Cases This section documents the test cases that a client or server conformant to the Tape Library Profile SHALL support. Note: the values for the returned items and the custom attributes are illustrative. Actual values from a real client system will vary. These test cases demonstrate usage of all of the mandatory types that are required to be supported in a server implementation. 3.1 Mandatory Test Cases This section documents the test cases that a client or server conformant to the Tape Library Profile SHALL support. TL-M-1 - Configuration Determine server configuration details including operations supported (only the mandatory operations are listed in the response example), objects supported (only the mandatory objects types are listed in the response example), optional server information, and optional list of application name spaces. Time Request/Response messages 0 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="1"/> </RequestHeader> <Operation type="enumeration" value="query"/> <QueryFunction type="enumeration" value="queryoperations"/> <QueryFunction type="enumeration" value="queryobjects"/> <QueryFunction type="enumeration" value="queryserverinformation"/> <QueryFunction type="enumeration" value="queryapplicationnamespaces"/> </RequestMessage> <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t21:35:17+00:00"/> <BatchCount type="integer" value="1"/> </ResponseHeader> <Operation type="enumeration" value="query"/> <Operation type="enumeration" value="query"/> <Operation type="enumeration" value="destroy"/> <Operation type="enumeration" value="get"/> <Operation type="enumeration" value="create"/> <Operation type="enumeration" value="register"/> <Operation type="enumeration" value="getattributes"/> <Operation type="enumeration" value="getattributelist"/> <Operation type="enumeration" value="addattribute"/> <Operation type="enumeration" value="modifyattribute"/> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 8 of 17

9 <Operation type="enumeration" value="deleteattribute"/> <Operation type="enumeration" value="activate"/> <Operation type="enumeration" value="revoke"/> <Operation type="enumeration" value="check"/> <ObjectType type="enumeration" value="symmetrickey"/> <ObjectType type="enumeration" value="template"/> <VendorIdentification type="textstring" value="server-vendor.com"/> <ApplicationNamespace type="textstring" value="lto"/> <ApplicationNamespace type="textstring" value="library-lto"/> </ResponseMessage> TL-M-2 - Write with new (Created) Key This case could occur when the Write operation starts with the first block on a tape. The implementation may choose which Write operations qualify for a creation of a new key. Regardless of the initiating circumstances, the Tape Library requests the server to create a new AES-256 symmetric key with appropriate identifying information which is unique within the Application Namespace. Additional custom attributes MAY be specified in order to: - ensure uniqueness of the key identifier when later Locating the key via ASI - provide human-readable information (such as the tape Barcode value) - information to support client-specific purposes Time Request/Response messages 0 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="2"/> </RequestHeader>o <Operation type="enumeration" value="create"/> <ObjectType type="enumeration" value="symmetrickey"/> <TemplateAttribute> <AttributeName type="textstring" value="name"/> <NameValue type="textstring" value="aaaaaaa1a1aa "/> <NameType type="enumeration" value="uninterpretedtextstring"/> <AttributeName type="textstring" value="cryptographic Algorithm"/> <AttributeValue type="enumeration" value="aes"/> <AttributeName type="textstring" value="cryptographic Length"/> <AttributeValue type="integer" value="256"/> <AttributeName type="textstring" value="cryptographic Usage Mask"/> <AttributeValue type="integer" value="decrypt Encrypt"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 9 of 17

10 value=" abcdef abcdef abcdef "/> <AttributeName type="textstring" value="x-vendorattribute1"/> <AttributeValue type="textstring" value="xxa012a1"/> <AttributeName type="textstring" value="x-vendorattribute2"/> <AttributeValue type="integer" value="0"/> <AttributeName type="textstring" value="x-vendorattribute3"/> <AttributeValue type="datetime" value=" t22:08:19+00:00"/> </TemplateAttribute> <Operation type="enumeration" value="get"/> </RequestMessage> <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t21:41:46+00:00"/> <BatchCount type="integer" value="2"/> </ResponseHeader> <Operation type="enumeration" value="create"/> <ObjectType type="enumeration" value="symmetrickey"/> <Operation type="enumeration" value="get"/> <ObjectType type="enumeration" value="symmetrickey"/> <SymmetricKey> <KeyBlock> <KeyFormatType type="enumeration" value="raw"/> <KeyValue> <KeyMaterial type="bytestring" value="2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a"/> </KeyValue> <CryptographicAlgorithm type="enumeration" value="aes"/> <CryptographicLength type="integer" value="256"/> </KeyBlock> </SymmetricKey> </ResponseMessage> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 10 of 17

11 TL-M-3 - Read from Tape Read an encrypted tape. The Tape Library constructs an identifier string based on the method in 2.3, then requests the server to Locate that string via ASI. A Get is then requested based on the key s unique identifier. The Tape Library MAY update attributes associated with the Symmetric Key Managed Object. The following example shows extensive use of custom attributes. Custom attributes are not required if the Application Name is unique within the Application Namespace. An implementation may also use custom attributes for vendor-unique purposes, or to improve usability. Time Request/Response messages 0 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="2"/> </RequestHeader> <AttributeName type="textstring" value="object Type"/> <AttributeValue type="enumeration" value="symmetrickey"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" value=" abcdef abcdef abcdef "/> <Operation type="enumeration" value="get"/> </RequestMessage> <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t22:00:32+00:00"/> <BatchCount type="integer" value="2"/> </ResponseHeader> <Operation type="enumeration" value="get"/> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 11 of 17

12 <ObjectType type="enumeration" value="symmetrickey"/> <SymmetricKey> <KeyBlock> <KeyFormatType type="enumeration" value="raw"/> <KeyValue> <KeyMaterial type="bytestring" value="2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a"/> </KeyValue> <CryptographicAlgorithm type="enumeration" value="aes"/> <CryptographicLength type="integer" value="256"/> </KeyBlock> </SymmetricKey> </ResponseMessage 1 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="2"/> </RequestHeader> <AttributeName type="textstring" value="object Type"/> <AttributeValue type="enumeration" value="symmetrickey"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" value=" abcdef abcdef abcdef "/> <Operation type="enumeration" value="getattributelist"/> </RequestMessage> <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t22:00:33+00:00"/> <BatchCount type="integer" value="2"/> </ResponseHeader> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 12 of 17

13 <Operation type="enumeration" value="getattributelist"/> <AttributeName type="textstring" value="x-barcode"/> <AttributeName type="textstring" value="x-vendorattribute1"/> <AttributeName type="textstring" value="x-vendorattribute2"/> <AttributeName type="textstring" value="x-vendorattribute3"/> <AttributeName type="textstring" value="unique Identifier"/> <AttributeName type="textstring" value="object Type"/> <AttributeName type="textstring" value="cryptographic Algorithm"/> <AttributeName type="textstring" value="cryptographic Length"/> <AttributeName type="textstring" value="application Specific Information"/> <AttributeName type="textstring" value="cryptographic Usage Mask"/> <AttributeName type="textstring" value="digest"/> <AttributeName type="textstring" value="initial Date"/> <AttributeName type="textstring" value="last Change Date"/> <AttributeName type="textstring" value="lease Time"/> <AttributeName type="textstring" value="name"/> <AttributeName type="textstring" value="state"/> </ResponseMessage> 2 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="2"/> </RequestHeader> <AttributeName type="textstring" value="object Type"/> <AttributeValue type="enumeration" value="symmetrickey"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" value=" abcdef abcdef abcdef "/> <Operation type="enumeration" value="getattributes"/> </RequestMessage <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t22:00:32+00:00"/> <BatchCount type="integer" value="2"/> </ResponseHeader> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 13 of 17

14 <Operation type="enumeration" value="getattributes"/> <AttributeName type="textstring" value="x-vendorattribute1"/> <AttributeValue type="textstring" value="xxa012a1"/> <AttributeName type="textstring" value="x-vendorattribute2"/> <AttributeValue type="datetime" value=" t22:08:19+00:00"/> <AttributeName type="textstring" value="x-vendorattribute3"/> <AttributeValue type="integer" value="0"/> <AttributeName type="textstring" value="unique Identifier"/> <AttributeValue type="textstring" value="12345abc d-be9c- <AttributeName type="textstring" value="object Type"/> <AttributeValue type="enumeration" value="symmetrickey"/> <AttributeName type="textstring" value="cryptographic Algorithm"/> <AttributeValue type="enumeration" value="aes"/> <AttributeName type="textstring" value="cryptographic Length"/> <AttributeValue type="integer" value="256"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" value=" abcdef abcdef abcdef "/> <AttributeName type="textstring" value="cryptographic Usage Mask"/> <AttributeValue type="integer" value="decrypt Encrypt"/> <AttributeName type="textstring" value="digest"/> <HashingAlgorithm type="enumeration" value="sha_256"/> <DigestValue type="bytestring" value="0bd3d7ada745e4eb34cc9d26cc84d4852a15906b2f77f80d01fc31c28108c49b"/> <AttributeName type="textstring" value="initial Date"/> <AttributeValue type="datetime" value=" t21:41:46+00:00"/> <AttributeName type="textstring" value="last Change Date"/> <AttributeValue type="datetime" value=" t21:41:46+00:00"/> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 14 of 17

15 <AttributeName type="textstring" value="lease Time"/> <AttributeValue type="interval" value="3600"/> <AttributeName type="textstring" value="name"/> <NameValue type="textstring" value="aaaaaaa1a1aa "/> <NameType type="enumeration" value="uninterpretedtextstring"/> <AttributeName type="textstring" value="state"/> <AttributeValue type="enumeration" value="preactive"/> </ResponseMessage> 3 <RequestMessage> <RequestHeader> <BatchOrderOption type="boolean" value="true"/> <BatchCount type="integer" value="3"/> </RequestHeader> <AttributeName type="textstring" value="object Type"/> <AttributeValue type="enumeration" value="symmetrickey"/> <AttributeName type="textstring" value="application Specific Information"/> <ApplicationNamespace type="textstring" value="library-lto"/> <ApplicationData type="textstring" value=" abcdef abcdef abcdef "/> <Operation type="enumeration" value="modifyattribute"/> <AttributeName type="textstring" value="x-vendorattribute2"/> <AttributeValue type="datetime" value=" t22:27:06+00:00"/> <Operation type="enumeration" value="modifyattribute"/> <UniqueBatchItemID type="bytestring" value="03"/> <AttributeName type="textstring" value="x-vendorattribute3"/> <AttributeValue type="integer" value="1"/> </RequestMessage> Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 15 of 17

16 <ResponseMessage> <ResponseHeader> <TimeStamp type="datetime" value=" t22:00:33+00:00"/> <BatchCount type="integer" value="3"/> </ResponseHeader> <Operation type="enumeration" value="modifyattribute"/> <AttributeName type="textstring" value="x-vendorattribute2"/> <AttributeValue type="datetime" value=" t22:27:06+00:00"/> <Operation type="enumeration" value="modifyattribute"/> <UniqueBatchItemID type="bytestring" value="03"/> <AttributeName type="textstring" value="x-vendorattribute3"/> <AttributeValue type="integer" value="1"/> </ResponseMessage> TL-M-4 Appended Write his operation appends data to existing data on a tape. It does not introduce new KMIP operations beyond those noted in TL-M-2 and/or TL-M-3. Time 0 Request/Response messages 3.2 Optional Test Cases This section documents the test cases that a client or server conformant to the Tape Library Profile MAY support. [[ TO BE ADDED IF REQUIRED OR REMOVED AS A SECTION]] Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 16 of 17

17 Appendix A. Acknowledgments The following individuals have participated in the creation of this specification and are gratefully acknowledged: TBD Standards Track Draft Copyright OASIS Open All Rights Reserved. Page 17 of 17