For a multivalued attribute, given we don't have an attribute index any more, how would the server know which one to delete?
Given we've pitched the index, we now need to know which value.
Unless we're talking about adopting the "don't argue with me, young man, you know what I meant" approach whereby the server just randomly shoots a value. That might prove difficult to write a conformance test for.
It just looks strange at first. Then it was clear to me that today with KMIP 1.4 a client would have to determine the value of an attribute anyway and then just use its index. So I am fine with it the way it is.
Thanks,
Mark
Bruce
On Wed, Dec 13, 2017 at 10:58 AM, Mark Joseph <> wrote:
Looking at the definition of "Delete Attribute" operation in the current KMIP 2.0 spec and comparing that to KMIP 1.4 there is a difference I am not sure we want.
In KMIP 1.4 the value of the attribute to delete is not required (only the attribute's Name and index)
In KMIP 2.0 the "Current Attribute" structure is required which includes the attribute's value. There is no text in the KMIP 2.0 spec that I have found that clearly contradicts that. So the KMIP client would have to know the current value of the attribute to delete it. That would be a new requirement and one I don't see the need for.
Best,
Mark Joseph
P6R, Inc
From:
Tony Cox <>
To:
<>
Sent:
12/7/2017 5:18 AM
Subject:
[kmip] Groups - Introduction to KMIP v2.0 WD01 uploaded
Document Name: Introduction to KMIP v2.0 WD01
No description provided.
Download Latest Revision
Public Download Link
Submitter: Mr. Tony Cox
Group: OASIS Key Management Interoperability Protocol (KMIP) TC
Folder: Proposals
Date submitted: 2017-12-07 05:17:29
