Key Management Interoperability Protocol Specification Version 1.1

SHALL always have a valueInitially set byModifiable by serverModifiable by clientDeletable by clientMultiple instances permittedWhen implicitly setApplies to Object TypesAll Managed Objects that areof the Object Types for whichthis attribute applies, SHALLalways have this attribute setonce the object has beencreated or registered, upuntil the object has beendestroyed.Who is permitted to initiallyset the value of the attribute(if the attribute has neverbeen set, or if all the attributevalues have been deleted)?Is the server allowed tochange an existing value ofthe attribute withoutreceiving a request from aclient?Is the client able to changean existing value of theattribute value once it hasbeen set?Is the client able to delete aninstance of the attribute?Are multiple instances of theattribute permitted?Which operations MAYcause this attribute to be seteven if the attribute is notspecified in the operationrequest itself?Which Managed ObjectsMAY have this attribute set?523524525526527528529530Table 36: Attribute Rules3.1 Unique IdentifierThe Unique Identifier is generated by the key management system to uniquely identify a Managed Object.It is only REQUIRED to be unique within the identifier space managed by a single key managementsystem, however it is RECOMMENDED that this identifier be globally unique in order to allow for a keymanagement domain export of such objects. This attribute SHALL be assigned by the key managementsystem at creation or registration time, and then SHALL NOT be changed or deleted before the object isdestroyed.ObjectUnique IdentifierText StringEncoding531Table 37: Unique Identifier Attributekmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 32 of 164