OASIS Open Mailing List Archives  ·  All Lists  ·  kmip-interop-tech  ·  2016-01

kmip-interop-tech — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

TC-312-12 (was RE: [kmip-interop-tech] Testing extension)


Gemalto's KeySecure KMIP server processes attributes as follows: 1. Process attributes in the order in which they appear within a request, regardless that the attribute appears in a referenced Template Managed Object within a TA Structure, as a stand-alone attribute within a TA Structure, or as a stand-alone attribute within a Key Block 2. In the case of a Template-Attribute (TA) Structure, in sequence: 2.1. Process any named Template references [i.e. retrieve all attributes contained by the named Template Managed Object] 2.2. Process any stand-alone attributes 3. In the case of single-instance attributes, the (N+1)th occurrence of the attribute overrides [i.e. replaces/displaces] the Nth occurrence of that same attribute. Single-instance attributes always have a zero-valued Attribute Index. 4. In the case of multi-instance attributes, the server assigns a zero-valued Attribute Index to the 1st occurrence of the attribute. For each subsequent occurrence N of the attribute, the server assigns an Attribute Index of (N-1). i.e. Monotonically increasing Attribute Index values, starting from zero. 5. In the case of attribute deletion, all remaining instances of that attribute preserve their Attribute Index values. 5.1. In the case that a client deletes the most recently added instance N of a multi-instance attribute, that attribute's next available Attribute Index remains N+1. i.e. All Attribute Index values remain unique for the life of that attribute. See 5.2 for "life". 5.2. In the case that all instances of a multi-instance attribute have been deleted, the server resets that attribute's next available Attribute Index to zero, and monotonically increasing Attribute Index assignment resumes. i.e. The life of an attribute ends on deletion of its last remaining instance. Note: This behaviour of multi-instance attributes is consistent with the behaviour of single-instance attributes. i.e. After deletion and subsequent re-creation (Add) of a single-instance attribute, that attribute's Attribute Index is (still) zero. Cheers, ... Dave

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]