[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [kmip] Import operation suggestion
On Jan 5, 2017, at 3:57 PM, Bruce Rich <firstname.lastname@example.org> wrote:Hmm, like maybe a Profile that specifies the required Attributes? Which would allow you to Query the server to see what profiles it supports, which would net the required Attributes without actually having to enhance Query to deal directly with Attributes, if that makes any sense. It did when I thought it, but now that I've typed it out it looks odder than most things I type.BruceOn Thu, Jan 5, 2017 at 5:51 PM, Mark Joseph <email@example.com> wrote:AnthonyOn the Import operation why not define a minimum set of attributes that must be supported on both ends for the operation to succeed? Maybe this is a way to ensure interoperability. I think one use for this feature could be by a customer to export from one server vendor and move the object to a different vendors product.
Best,Mark JosephP6R, Inc
On Jan 5, 2017, at 1:28 AM, Anthony Berglas <firstname.lastname@example.org
> wrote:Um, that should be PKCS#11, not POX intended!AnthonyOn Thu, Jan 5, 2017 at 7:25 PM, Anthony Berglas <email@example.com >wrote:Submitter's message
Below is the link to a proposal to add Extractable and Sensitive flags to KMIP. They are modeled after POCS#11 in order to restrict the retrieval of key material.
I will present this on tomorrow's call.
-- Anthony Berglas
Document Name: Non Exportable and Sensitive Attributes proposal
No description provided.
Download Latest Revision
Public Download Link
Submitter: Anthony Berglas
Group: OASIS Key Management Interoperability Protocol (KMIP) TC
Date submitted: 2017-01-05 01:25:10