kmip message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Custom Attribute to Vendor Attribute -- Re: [kmip] Groups - Introduction to KMIP v2.0 WD01 uploaded
- From: Mark Joseph <mark@p6r.com>
- To: Tony Cox <tony.cox@cryptsoft.com>, kmip@lists.oasis-open.org
- Date: Thu, 14 Dec 2017 13:28:15 -0800
I did not see anything like this in the KMIP 2.0 spec:
For managed objects that already have one or more pre KMIP 2.0 Custom Attributes (e.g., "x-", and "y-" values) I suggest thatthese show up as KMIP 2.0 Vendor Attributes where the Vendor Name field is either not present in the structure or something like "KMIP-PRE2.0" appears (which will not clash with a real vendor's name). The point is so that KMIP 2.0 applications can access previously created Custom Attributes which have been removed from the 2.0 spec.
We have customers that have used Custom Attributes and for them to transition to KMIP 2.0 will require something like this.
Best,
Mark Joseph
P6R, Inc
From:
Tony Cox <tony.cox@cryptsoft.com>
To:
<kmip@lists.oasis-open.org>
Sent:
12/7/2017 5:18 AM
Subject:
[kmip] Groups - Introduction to KMIP v2.0 WD01 uploaded
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]