kmip-interop-tech — archive

[David Featherstone]

Hi John By the logic of Option-2, given three appearances of the x-ID attribute -- two in a referenced Template, and a third made explicit in the Create -- then the explicit third appearance would take highest precedence and would have the lowest AttributeIndex value [of zero]. Suppose, however, that instead of a single {Create w/Template&x-ID } we were given two batched operations: {Create w/Template plus Add w/x-ID}. The semantic intents of the two requests are so similar as to be indistinguishable, but by the logic of Option-2, the Add w/x-ID instance would receive the highest AttributeIndex value of 2, and the second of the two x-ID appearances in the Template reference would get the AttributeIndex of zero. Option-1 provides a more consistent outcome in that the third x-ID instance -- no matter that it appears coincident with the Create operation, or separate in the Add operation -- always receives an AttributeIndex of 2. The fact that Option-2 does not have this consistency lends preference to Option-1. I do not think that the KMIP Specification can allow both options/interpretations. Cheers, ... Dave